How to Scale End-to-End Observability in AWS Environments

Red Hat announces the availability of OpenShift 4.7

OpenShift 4.7 moves steps closer to fading the line between container orchestration and virtual machines.

March 12, 2021, 5:17 p.m.

TL;DR

OpenShift 4.7, the latest Windows Container support software from Red Hat, has been made globally available. An embodiment of Red Hat's efforts to improve activity and dependency to orchestrate both virtual machines and containers.

It is now possible to migrate from Kubernetes to OpenShift 4.7 due to the introduction of deployment objects.

Key Facts

1
Red Hat has expanded Windows container support to guide new enterprises better.
2
A platform has been introduced to create one-click virtual machines.
3
It is now possible to migrate from Kubernetes to OpenShift 4.7 due to the introduction of deployment objects.

Details

Red Hat OpenShift 4.7 boasts of myriads of application modernization and migration capabilities to fit particular container orchestration demands.

In addition to Windows Container support in AWS and Azure, Openshift now enhances support and education for Windows Containers on vSphere using Installed Provided Infrastructure (IPI). This provides a beeline for organizations or individuals to move Windows Containers to Red Hat OpenShift without thoughts for their space and the need to rewrite new code completely.

OpenShift Virtualization takes center stage in the order of prominence in terms of features the new release holds. Distinguished by the ability to orchestrate both virtual machines and containers, the platform brandishes virtual machines as first-class citizens allowing interaction between legacy and modern workloads.

Au contraire to Kubernetes, there is a restricted number of operating systems that nodes and virtual machines can execute. There are certain similarities in Openshift's deployment paradigm compared with Kubernetes as OpenShift relies on logic-based deployment objects and Kubernetes, controller-based. This gives Openshift the advantage of using hooks to prepare for updates. However, since OpenShift now utilizes development objects, it is possible to transition from Kubernetes to OpenShift.

KubeVirt, as the name connotes, embodies Kubernetes and virtual machine features. It enables virtual machines to run side by side with containers in their Kubernetes or OpenShift clusters. Consumers can now manage the virtual machine life cycle through the familiar Kubernetes API and tools accessible in the ecosystem. KubeVirt allows OpenShift 4.7 to fade the gap between container-native storage and networking to virtual machines.

OVN-IPsec enables encryption of all OpenShift traffic with IPsec when engaging Open Virtual Network(OVN). Enabling IPsec encryption is vital in preventing cluster traffic data from being manipulated and monitored.

OpenShift GitOps (Technology Preview) guides Application architecture and DevOps to relay applications across various clusters in a repeatable way. OpenShift GitOps enables one-step installation of cluster structure and application deployment based on ArgoCD and Tekton Pipelines. With the delivery of functionality as code from idea to production, OpenShift GitOps endears organizations to secure, manage and update applications through Git, optimizing security, ease of updates, and market time.

To enhance security, the Compliance Operator was released in OCP 4.6, and it utilizes the Open Policy Agent (OPA) to decide and harden the OpenShift cluster.

All these additions highlight Red Hat's commitment to ease the tech world for new and old enterprises. With the resources, innovation, and technical know-how at their disposal, there's more to come.