Cloud Platform as a Service

 View Only

IBM Cloud Containers - November 2024 "Private path NLB"

By John Wen posted Thu December 05, 2024 12:19 PM

  

OpenShift 4.17 GA

We are excited to announce the availability of OpenShift version 4.17 for your clusters that are running in Red Hat OpenShift on IBM Cloud. This marks our 16th release of OpenShift.  

In addition to all the great OpenShift features provided in this release, Red Hat OpenShift on IBM Cloud version 4.17 also includes numerous component updates that our community is excited about. Some of the highlights for the release include: 

  • Red Hat Enterprise Linux 9: In addition to RHEL8 and RHCOS availability, we’ve made RHEL 9 the default operating system for Red Hat OpenShift on IBM Cloud version 4.17 Classic and VPC clusters.

  • Validating Admission Policy: This powerful feature allows organizations to enforce specific rules on resources before they’re created or modified – acting as a gatekeeper, ensuring that only resources that adhere to predefined policies are admitted to the cluster.

To read more on OpenShift 4.17 read the full blog here

Private path NLB

A "private path NLB" refers to a Network Load Balancer (NLB) configured to route traffic exclusively within a private network, meaning all communication happens solely inside a cloud provider's internal infrastructure without exposing any data to the public internet; essentially, it acts as a load balancer for private services within a Virtual Private Cloud (VPC), only accessible by other resources within that private network. 

Use cases:

This is particularly useful for scenarios where you need to load balance traffic between internal services within a cloud environment, without exposing them to the public internet. 

Secure by Default for pre-existing clusters 

In March we released an important feature “Secure by Default” for newly created clusters. The objective of this feature is protect clusters via restricting networkings only with connectivity necessary for the cluster to operate and in an initial state preventing access to the public Internet. We have expanded this feature to pre-existing clusters as we continue to strive to keep our customer’s workload safe!

0 comments
9 views

Permalink