Changes to private IP addresses for Container Registry from 15 December 2022

What you need to know about this change

IP addresses for accessing Container Registry over the private network changed on 5 July 2022, see Container Registry private IP addresses changed on 5 July 2022. You continue to be able to use these old IP addresses, but they are due to be decommissioned on 15 December 2022. After this date, you will not be able to access Container Registry by using these IP addresses.

IBM Cloud Kubernetes Service cluster workers are configured so that you can access Container Registry over the private network even when the public domain is used. This process caches the DNS result on worker startup and is not refreshed until a cluster worker is reloaded, replaced, or rebooted. If you have not reloaded, replaced, or rebooted the cluster workers since 5 July 2022, it is likely that they still refer to the old Container Registry private IP addresses. If these workers are not reloaded or replaced, they will not function correctly after the old Container Registry IP addresses are decommissioned.

If you have any other custom configuration that uses the old Container Registry private IP addresses and you do not update your configuration to use the new Container Registry IP addresses, you might have a problem with accessing Container Registry over the private network. For more information, see Permit worker nodes to communicate with IBM Cloud Container Registry.

What actions you need to take

Any cluster workers that you have not reloaded, replaced, or rebooted since 5 July 2022 must be reloaded or replaced before 15 December 2022. For more information about how to reload workers for classic clusters, see ibmcloud ks worker reload. For more information about how to replace workers for VPC clusters, see ibmcloud ks worker replace. You can also reboot affected workers but this action is not recommended due to the risks associated with rebooting. For more information about rebooting workers, see ibmcloud ks worker reboot.

If you have any other custom configuration that uses the old Container Registry private IP addresses, such as for firewall rules or Calico policies, you must update your configuration to use the new Container Registry IP addresses and remove the old IP addresses. Both the old and new private IP addresses are documented in the IBM Cloud Kubernetes Service documentation. For more information, see Permit worker nodes to communicate with IBM Cloud Container Registry.

The IBM Cloud Kubernetes Service Calico policy samples will be updated to remove the old IP addresses on 15 December 2022. If you use these samples, ensure that you pull in the most recent samples after this date.

Original announcement

The original announcement was published on 2 November 2022.