2 min read

In an effort to sync their releases with Kubernetes, RedHat skipped 3.8 release and came up with version 3.9, for their very own container application platform i.e OpenShift.

RedHat seems to be moving really quick with their OpenShift roadmap, with 3.10 release lined up in Q2 2018 (June).

The primary takeaway from the accelerated release cycle of OpenShift is the importance of the tool in RedHat DevOps expansion. With dedicated support to cutting-edge tools like Docker and Kubernetes, OpenShift looks like a strong DevOps tool, which is here to stay.

The OpenShift 3.9 release has quite a few exciting middleware updates, bug fixes, and service extensions. Let’s look at some of the enhancements in key areas:  


Container Orchestration

  • OpenShift has added Soft Image Pruning, wherein you don’t have to remove the actual image, but need to just update the etcd storage file instead.
  • Added support to deploy RedHat ClouForms on OpenShift container engine.
  • Added features:
    • OpenShift Container Platform template provisioning
    • Offline OpenScapScans
    • Alert management: You can choose Prometheus (currently in Technology Preview) and use it in CloudForms.
    • Reporting enhancements
    • Provider updates
    • Chargeback enhancements
    • UX enhancements
  • The inclusion of CRI-O V1.9, a lightweight native Kubernetes run-time interface. Addition of CRI-O brings the following advancements:
    • A minimal and secure architecture.
    • Excellent scale and performance.
    • The ability to run any Open Container Initiative (OCI) or docker image.
    • Familiar operational tooling and commands.

Storage

  • Expand persistent volume claims online from {product-tile} for CNS glusterFS, Cinder, and GCE PD.
  • CNS deployments are automated and CNS Un-install Playbook is added with the release of OpenShift 3.9

Developer Experience

  • Improvements in Jenkins support, which intelligently predicts to pod memory before processing it.
  • Updated CLI-plugins or binary extensions, which extends the default set of OC commands, allowing you to perform a new task.
  • The BUILDCONFIG DEFAULTER now allows specifications now allows a toleration value, which is applied upon creation.

For minor bug fixes and the complete release data, refer to  OpenShift Release Notes.

 


Subscribe to the weekly Packt Hub newsletter. We'll send you the results of our AI Now Survey, featuring data and insights from across the tech landscape.

LEAVE A REPLY

Please enter your comment!
Please enter your name here