Action Required Service Updates

Deprecation: Single and Scalable Group Container Service in Bluemix Dedicated and Local

Share this post:

Bluemix Support News

We are excited that the IBM Bluemix Container Service with Kubernetes has now gone live. IBM Bluemix Container Service now combines Docker and Kubernetes to deliver powerful tools, an intuitive user experience, and built-in security and isolation. The service leverages cloud services and Watson’s cognitive capabilities to enable rapid delivery of applications. It provides access to all of the DevOps capabilities of Kubernetes including rolling updates to support zero-downtime deployments of new versions.

With the move toward Kubernetes, the older architecture (single containers and container groups) will be retired. We encourage you to transition to the Kubernetes-based container service immediately to take advantage of the inherent Kubernetes capabilities as well as those provided by IBM. Please note that this affects all regions.  All of your images stored within the IBM Bluemix Container Registry will remain after the deprecation.  The capabilities provided by Vulnerability Advisor will remain as well.

IBM will work with existing Dedicated and Local customers on a transition to the new Kubernetes-based offering.   With the new architecture, all IBM Bluemix Container Service Kubernetes clusters are dedicated by design and deployed within the public cloud. Public is simply a statement that the IBM Bluemix Container Service is available from a public endpoint and not a statement of the isolation level of the resources provisioned by the service.

Bluemix Local has been replaced with the IBM Cloud private offering.

What you need to know:

 

  • End of Marketing: As of August 11, 2017, the single container and container group part numbers will be removed from the IBM SQO ordering database. We highly encourage all the users of the old architecture to migrate to the new Kubernetes-based offering.

 

  • End of Support: Existing users of the single container and container group service will be supported through June 20, 2018.

 

What you need to do:

Prior to the End of Support date, June 20, 2018, you must:

  • Migrate your workload to the new Kubernetes-based IBM Bluemix Container Service
  • On June 20, 2018, we will delete your existing single containers and container groups infrastructure.

For help with migration plan, see the docs.

Join the discussion on Slack with questions or comments.  If you cannot automatically join https://ibm-container-service.slack.com, please email crosen@us.ibm.com.

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

More Action Required Service Updates stories
January 8, 2019

Sydney? Version 9.1.1? IBM MQ MFT? IBM MQ on Cloud Welcomes You with Open Arms

IBM MQ is now available in Sydney, Australia. Additionally, you can enjoy MQ 9.1.1 in the managed service by upgrading your queue managers manually or waiting until the automatic upgrade on February 6, 2019.

Continue reading

December 18, 2018

IBM Cloud Mobile Foundation: Migration from Deprecated Plans to New Plans

In February 2018, we announced the deprecation of Developer, Developer Pro, and Professional Per Capacity pricing plans for Mobile Foundation Service. If you are still on a deprecated plan, immediate action is required to migrate to one of the new plans.

Continue reading

December 14, 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