Updating your expired Version 1.1.0 and 1.2.0 certificates
JianQiu 270003STSK Comments (5) Visits (7996)
Updating your Version 1.1.0 and 1.2.0 certificate
If you have an IBM Cloud private cluster that was installed prior to August 23, 2017, you will need to update your product certificate. The product certificate for both IBM Cloud private Version 1.2.0 and IBM Spectrum Conductor for Containers Version 1.1.0 will expire on the 22nd of August, 2017. This expired certificate will impact access to the private image registry and Kubernetes api-server. To fix this certificate expiration issue, we have updated the docker images on Docker Hub.
Note: If you are doing a fresh installation of an IBM Cloud private-ce (Community Edition) cluster on or after August 23, 2017, you do not need to update your certificate.
Fresh installations, on or after August 23, 2017, of an IBM Cloud private standard cluster will still be affected by this expired certificate. We are working on a patch for this. To resolve this issue in your fresh IBM Cloud private standard environment, you will need to follow the procedure below.
To run this script, you will need to have internet access to Docker Hub on your boot, master, and worker, and proxy nodes.
In your existing cluster, that is a cluster installed prior to August 23, 2017. Download and run the following script on all your master, worker, and proxy nodes.
For IBM Cloud private Version 1.2.0 (both standard and community editions)
For IBM Cloud private (formerly IBM Spectrum Conductor for Containers) Version 1.1.0
This script will update the existing certificate, update all the required images, and restart the management services.