Google is committed to advancing racial equity for Black communities. See how.

4.19.06.05 - Edge for Private Cloud release notes

On April 22, 2020, we released a new version of Apigee Edge for Private Cloud.

Update procedure

To update your installation, perform the following procedure on the Edge nodes:

  1. On all Edge nodes:

    1. Clean the Yum repos:
      sudo yum clean all
    2. Download the latest Edge 4.19.06 bootstrap_4.19.06.sh file to /tmp/bootstrap_4.19.06.sh:
      curl https://software.apigee.com/bootstrap_4.19.06.sh -o /tmp/bootstrap_4.19.06.sh
    3. Install the Edge 4.19.06 apigee-service utility and dependencies:
      sudo bash /tmp/bootstrap_4.19.06.sh apigeeuser=uName apigeepassword=pWord

      Where uName:pWord are the username and password you received from Apigee. If you omit pWord, you will be prompted to enter it.

    4. Update the apigee-setup utility:
      sudo /opt/apigee/apigee-service/bin/apigee-service apigee-setup update
    5. Use the source command to execute the apigee-service.sh script:
      source /etc/profile.d/apigee-service.sh
  2. Run the update.sh script on all nodes. On each node, execute the following command:
    /opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile

    Where configFile specifies the configuration file that you used to install Apigee Edge for Private Cloud.

  3. (Apigee mTLS only) To update Apigee mTLS:
    1. Uninstall Apigee mTLS by executing the following command:
      /opt/apigee/apigee-service/bin/apigee-service apigee-mtls uninstall
    2. Install Apigee mTLS by executing the following commands:
      /opt/apigee/apigee-service/bin/apigee-service apigee-mtls install
      /opt/apigee/apigee-service/bin/apigee-service apigee-mtls setup -f /opt/silent.conf

    For more information about Apigee mTLS, see Introduction to Apigee mTLS.

Supported software

No changes.

Deprecations and retirements

No changes.

Bugs fixed

The following table lists the bugs fixed in this release:

Issue ID Description
150721678

Reliability increases

After reliability improvements, you should see fewer log file messages in the following format:

[WARN] agent: Checking $SERVICE socket connection failed"
152516353
153575181

Improved accuracy and multi-data center communications

Apigee mTLS more accurately tracks service health for routing requests across the service mesh, including multiple data center configurations.