Upgrade a container deployment
2 minute read
In a container deployment, an upgrade is rolled out using an orchestration tool (for example, Kubernetes or OpenShift) after new Docker images containing the upgrade are pushed to the Docker registry. This enables you to perform a rolling zero downtime update of services.
To perform an upgrade, follow these steps:
-
Download the API Gateway 7.7 Linux installer from Axway Support at https://support.axway.com.
-
Create a new base image using the
--installer
option to build the image from the downloaded API Gateway 7.7 installer.cd emt_containers-<version> ./build_base_image.py --installer=apigw-770-installer.run --os=centos7
-
Upgrade your existing API Gateway
fed
to version 7.7. In Policy Studio 7.7, create a new project from the existing configuration to trigger an automatic upgrade. -
Create a merge directory to contain any custom configuration (for example,
/tmp/apigateway
). The merge directory must be calledapigateway
and must have the same directory structure as theapigateway
directory of an API Gateway installation. -
Add any custom configuration to the merge directory. For example, to add a custom
envSettings.props
file to your image, copyenvSettings.props
to/tmp/apigateway/conf/
. -
Create new Admin Node Manager and API Gateway images using the
--fed
option to build the API Gateway image from the upgradedfed
and the--merge-dir
option to specify the merge directory containing the custom configuration. For example:cd emt_containers-<version> ./build_anm_image.py --domain-cert=certs/mydomain/mydomain-cert.pem --domain-key=certs/mydomain/mydomain-key.pem --domain-key-pass-file=/tmp/pass.txt --anm-username=gwadmin --anm-pass-file=/tmp/gwadminpass.txt --merge-dir=/tmp/apigateway ./build_gw_image.py --license=/tmp/api_gw.lic --domain-cert=certs/mydomain/mydomain-cert.pem --domain-key=certs/mydomain/mydomain-key.pem --domain-key-pass-file=/tmp/pass.txt --fed=my-upgraded-fed.fed --fed-pass-file=/tmp/my-group-fedpass.txt --merge-dir=/tmp/apigateway