Containers and Kubernetes play a key role for modern application development, supporting new business models around edge, IoT and AI/ML. Despite all of this, there are still some barriers to even faster adoption of enterprise open source. In EMEA specifically these center around concerns with level of support, compatibility with legacy systems and lack of internal skills.
Kubernetes has removed several APIs from version 1.22. Any Operators utilizing these deprecated APIs will not work on OpenShift 4.9+ (or any cluster vendor utilizing Kubernetes 1.22) and will block your
Red Hat OpenShift 4.11 is now generally available, incorporating many enhancements such as hosted control planes, improved pod security options, better support for air-gapped environments, deeper observability via the web console, among others.
Red Hat OpenShift 3.11 officially reached its end of maintenance support on June 30, 2022. Now that OpenShift 3 has moved into the end of the maintenance support phase – it’s time for your customers to migrate.
In a previous blog post we discussed some of the general details around what customers using Red Hat OpenShift 3 need to do to migrate to Red Hat OpenShift 4. In this post, we’ll dig a little deeper into steps needed to properly complete this migration in an effective and efficient manner.