
It’s the most stable OKD version I’ve ever seen.
⚠️My personal suggestion would be to only use “Red Hat Openshift” for “Production and Live Environments” for sure ! – However, it is appropriate to use OKD for Test and Developer environments or for R&D. Of course it’s up to you..
▪️Download Link:
https://lnkd.in/daM4yhBw
📢 OKD 4.9.0 Release Highlights:
🔺Uses #k8s based v1.22.3
🔸Supports #Kasten K10 by #Veeam with k8s v1.22 for PODs
🔺Integration with #OpenStack: Fixed links in SR-IOV workers (If you re using OKD on #RedHat OpenStack)
🔺Added arm64 support
🔺Added #IBMCloud DNS support
🔺New #Tekton hub integrations for CI/CD tasks
🔺Added new labels to show #Grafana dashboards in ODC and allowed configuring additional Alertmanagers for #Prometheus
🔺Added alerts for issues with load balancers/ports
🔺OKD installer changes were merged, forked installer is no more
🔺Fixed the subject for monitoring CSRs approval
🔺New Feature added unified on CRI to support cgroup v2. Cgroupsv2 is used for new installations, upgraded clusters remain on
cgroupsv1. Users may switch to cgroupsv2 by adding
“systemd.unified_cgroup_hierarchy=1” kernel argument via MachineConfig
🔺Added new driver permissions for vmware-vsphere-csi-operators and RedHat #Ceph integrations.
🔺Supporting external control plane topologies
🔺Added a new node role for control planes
🔸New Operators and PODSecurity Container Features
🔸New Features NFS Provisioning on OKD
🔹#Fedora #CoreOS upgraded from 48.34.0 to 49.34.1 (It’s pretty stable working with it for now)
🔺Remove worker disk types below 8GB
and vice-versa…
There also so many seems bug-fixes and features developed for sure as the follows details below;
▪️Detailed Release Link:
https://lnkd.in/dqXV3Ny9