VSHN.timer #28: OpenShift 4.3
Welcome to another VSHN.timer! Every Monday, 5 links related to Kubernetes, OpenShift, CI / CD, and DevOps; all stuff coming out of our own chat system, making us think, laugh, or simply work better.
This week we are going to talk about the latest news about OpenShift, the enterprise-ready Kubernetes platform by Red Hat.
1. Red Hat released OpenShift 4.3 a few days ago. This new version of OpenShift brings lots of new features increasing the security of container deployments in the platform: FIPS 140-2 Level 1 compliant encryption, choice of cipher suites for the Ingress controller, new built-in data protection features in Red Hat OpenShift Container Storage 4, and the new Container Security Operator for Red Hat Quay. Lots of new features and relentless innovation. (Kubernetes 1.17 was also released recently, but we’ll talk about it in a future edition of VSHN.timer, since OpenShift 4.3 is based on K8s 1.16.)
2. Migrating to OpenShift 4 is not as simple as running an installer. It requires planning, architecture, design, and strategy. That’s why Red Hat has put together a guide to help in the migration of clusters to the latest and greatest OpenShift using the Cluster Application Migration tool (CAM), a tool based on Velero and Restic.
3. Of the more than 90 Kubernetes distributions certified by the Cloud Native Computing Foundation, Axa Schweiz chose OpenShift for their operations. Why? Axa Schweiz CIO Andy Maier explains it all in this article in the Inside Channels blog (in German).
For Maier, Openshift is a central element of the cloud strategy. “I would never put my applications natively on a cloud,” he explains, adding that he must minimize the strategic dependency that also exists in the cloud. “If I have a problem with a cloud provider in three or four years, then I’ll have a problem of two to three million francs over a year and a half, not a 20 million franc problem that will take three to four years to solve.”
4. Development teams who would like to run a small OpenShift 3.11 cluster previously relied in Minishift. Red Hat announced previously that Minishift will not be upgraded to OpenShift 4, instead offering CodeReady Containers (CRC) to fulfill this need. This product is officially only supported in some flavors of Linux (using KVM, not VirtualBox!) like Fedora, RHEL or CentOS, which left Ubuntu users on their own to find out the required dependencies. Thankfully Markus Hansmair of ConSol Labs wrote a fantastic article with all the information required to get started with CRC in one of the most popular Linux distributions out there.
5. The tool of the week… is actually a list thereof! Here’s the “Golden Kubernetes Tooling and Helpers list“, an incredibly exhaustive list of Kubernetes-related tools. We’re sure you will discover something new in it.
Are you using OpenShift clusters in production? Have you migrated to OpenShift 4? Are your development teams using CodeReady Containers already? Get in touch with us through the form at the bottom of this page, and see you next week for another edition of VSHN.timer.
Watch the Recording of “How to Keep Container Operations Steady and Cost-Effective in 2024”Read more
Celebrating Collaboration and Innovation: VSHN at Red Hat Summit Connect Zurich 2024Read more
Our team of experts is available for you. In case of emergency also 24/7.Contact us