Join us to learn more from a community of collaborative experts and IBM Cloud product users to share advice and best practices with peers and stay up to date regarding product enhancements, regional user group meetings, webinars, how-to blogs, and other helpful materials.
Announcing new features that have been shipped in the November 2023 along with the value they provide to new, existing, and prospective users. Create your cluster now!
OpenShift 4.14: IPI support on IBM Cloud VPC
This provider integration enables existing or new IBM Cloud customers to explore the usage of self-managed OpenShift 4.14 on IBM Cloud VPC IaaS and take advantage of the benefits offered by the OpenShift platform such as scalability, flexibility, portability, automation, advanced security and compliance on state of the art highly resilient and highly secure IBM VPC infrastructure.
VPC File support for Virtual Network Interface (VNI)
VPC File support gives you the ability to provision Persistent Volume Claims with read write access (RWX) to kubernetes Clusters
With this support there are two key features that are also provided
Cross-Zone Mounting - ability to mount a file share across multiple zones which will enable regional access to your file share in a multi zone cluster so that users can access cluster data even if the worker node where the file share was created goes down.
Support Granular Authorization for VPC File Share - which will provide the ability to control access to Persistent volumes used by workloads running in the RedHat OpenShift on IBM Cloud & IBM Kubernetes Service so that users can create custom file share access policies across subnets allowing isolation of file share across workloads running in the cluster.
Simplified flexibility for pod subnets (VPC)
We are providing a way to set subnet size via configuration which will enable users to choose a subnet size that works best for their use case.
Users may have a cluster with many pods where they need a larger subnet
Or they may have multiple clusters in the same VPC where they need to reduce the subnet size in order to reduce conflicting addresses with other clusters
When allocating the pod subnet automatically, the biggest subnet is limited to 13, and the smallest subnet size is limited to 23.
Note: the default behavior does not change
Copy