Upgrade the cluster to Kubernetes Release 1.17.

On the operator node, use the olcnectl module update command to upgrade to the latest Kubernetes release. This example upgrades a Kubernetes module named mycluster in the myenvironment environment to Kubernetes Release 1.17:

$ olcnectl --api-server 127.0.0.1:8091 module update \
  --environment-name myenvironment \
  --name mycluster \
  --kube-version 1.17.9 

The --kube-version option specifies the release to which you want to upgrade. This example uses release number 1.17.9.

If you are using the NGINX load balancer deployed by the Platform CLI, you should also upgrade NGINX on the master nodes. You specify the location from which to pull the NGINX container image used to upgrade NGINX using the --nginx-image option.

For example, include this additional line in the olcnectl module update command to upgrade NGINX from the Oracle Container Registry:

  --nginx-image container-registry.oracle.com/olcne/nginx:1.17.7 

When you upgrade from Kubernetes Release 1.14 to 1.17, the update iterates through each Kubernetes release up to release 1.17. That is, the nodes are upgraded to Kubernetes Release 1.15, then 1.16, and finally to 1.17.

When each node in the cluster is upgraded to the next Kubernetes release, the cluster's health is validated. If the cluster is healthy, the cycle of back up, upgrade to the next release, and cluster validation starts again, until all nodes are upgraded to the latest release.