IBM Cloud Container Registry Deprecates Registry Tokens for Authentication

Back in June 2019, we announced the discontinuation of registry tokens as an authentication mechanism as we moved to a more secure IAM API key approach.

This announcement also aligned to the icr.io domain name changes. We made a second announcement in February 2020 about IBM Cloud Container Registry not accepting registry tokens for authentication.

Effective August 19, 2021, any registry pulls that are using registry tokens will stop working, including pulls from IBM Cloud Kubernetes Service and Red Hat OpenShift on IBM Cloud. Any registry pushes using registry tokens from CI pipelines will also stop working.

How do I avoid disruption?

You should automate access to your IBM Cloud Container Registry namespaces so you can push and pull images using IBM Cloud Identity and Access Management (IAM). Learn more:

Join the conversation

If you have questions or concerns, engage our team via Slack. You can register here and join the discussion in the #general channel on https://ibm-cloud-success.slack.com/.

Chris Rosen

Program Director, Offering Management

Success and recognition of IBM offerings in G2 Summer Reports

2 min read - IBM offerings were featured in over 1,365 unique G2 reports, earning over 230 Leader badges across various categories. This recognition is important to showcase our leading products and also to provide the unbiased validation our buyers seek. According to the 2024 G2 Software Buyer Behavior Report, “When researching software, buyers are most likely to trust information from people with similar roles and challenges, and they value transparency above other factors.” With over 90 million visitors each year and hosting more than 2.6…

Manage the routing of your observability log and event data

4 min read - Comprehensive environments include many sources of observable data to be aggregated and then analyzed for infrastructure and app performance management. Connecting and aggregating the data sources to observability tools need to be flexible. Some use cases might require all data to be aggregated into one common location while others have narrowed scope. Optimizing where observability data is processed enables businesses to maximize insights while managing to cost, compliance and data residency objectives. As announced on 29 March 2024, IBM Cloud® released its next-gen observability…

Unify and share data across Netezza and watsonx.data for new generative AI applications

3 min read - In today's data and AI-driven world, organizations are generating vast amounts of data from various sources. The ability to extract value from AI initiatives relies heavily on the availability and quality of an enterprise's underlying data. In order to unlock the full potential of data for AI, organizations must be able to effectively navigate their complex IT landscapes across the hybrid cloud. At this year’s IBM Think conference in Boston, we announced the new capabilities of IBM watsonx.data, an open…

Back in June 2019, we announced the discontinuation of registry tokens as an authentication mechanism as we moved to a more secure IAM API key approach.

How do I avoid disruption?

Join the conversation

If you have questions or concerns, engage our team via Slack. You can register here and join the discussion in the #general channel on https://ibm-cloud-success.slack.com/.

More from Announcements

Success and recognition of IBM offerings in G2 Summer Reports

Manage the routing of your observability log and event data

Unify and share data across Netezza and watsonx.data for new generative AI applications

IBM Newsletters