Action Required Service Updates

Final Reminder: Deprecation of Single Containers and Container Groups

Share this post:

The complete deprecation and deletion of all running instances from the old container service in IBM Cloud will take place December 5, 2017.  The deprecation of the old architecture was announced in July.  The new version of the container service went live in May and has seen tremendous growth and capabilities.

As a reminder, the end of support is December 5, 2017.  If you do not migrate your workloads, those running instances will be lost.

On December 5, 2017, we will begin deleting your existing single containers and container groups from the IBM Cloud public offering.  At that point the billing will stop.  If you do no longer require the volumes created as part of the old container service, you must delete those manually.

Learn more about the new IBM Cloud Container Service!

Program Director, Offering Management, IBM Kubernetes Service & IBM Container Registry

More Action Required Service Updates stories
December 7, 2018

Automate and Operationalize Your AI with AI OpenScale

Today, we are taking a major step forward in helping enterprises automate and operationalize AI with the launch of the Standard Plan for AI OpenScale on IBM Cloud, along with other updates to the offering. In addition, AI OpenScale is now also available for deployment on cloud or on-premises with IBM Cloud Private for Data.

Continue reading

December 4, 2018

Vulnerability Advisor v2 API Deprecation

Vulnerability Advisor is a component of the IBM Cloud Container Registry offering which scans Docker images that are stored in your registry for known vulnerabilities and configuration issues. Effective January 8, 2019, v2 of Vulnerability Advisor’s API will be deprecated and will no longer be usable.

Continue reading

October 31, 2018

Increased Availability with HA Masters in the Kubernetes Service: Actions You Must Take

IBM Cloud Kubernetes Service will soon increase your cluster availability by adding replicas of the Kubernetes master with fix pack version 1.11.3_1531, released on November 1, 2018. After you update, clusters will have three Kubernetes master replicas that you set up with a highly available (HA) configuration.

Continue reading