Isovalent Networking for Kubernetes (INK) is a supported third-party CNI for Microsoft Azure Red Hat OpenShift with hosted control planes, now generally available. This certification covers INK 1.19 and later, giving platform teams Cilium-based networking, identity-aware policy, and network observability for Azure Red Hat OpenShift.
This announcement builds on our partnership with Microsoft, including Azure CNI Powered by Cilium for Azure Kubernetes Service (AKS). That offering uses Cilium for service routing and network policy. INK now brings a supported Cilium-based networking choice to teams running Azure Red Hat OpenShift.
What is Azure Red Hat OpenShift?
Azure Red Hat OpenShift is a fully-managed service on Microsoft Azure, jointly engineered, operated, and supported by Red Hat and Microsoft. It combines Kubernetes with Red Hat OpenShift tools for building and running applications, including image registries, monitoring, and CI/CD.
Why does the CNI matter with hosted control planes?
In Azure Red Hat OpenShift with hosted control planes architecture, Red Hat operates the control plane in an Azure service account. Your worker nodes run in your Azure subscription and virtual network. The API server and other control plane components are managed separately from the workers that run your applications.
That separation reduces the control plane infrastructure in your subscription and allows the control plane and worker node pools to be upgraded separately. Microsoft explains the operating model in its comparison of Azure Red Hat OpenShift (standard architecture) and hosted control planes.
Those worker nodes still need a Container Network Interface (CNI) plugin to connect application pods and enforce network policy. Azure Red Hat OpenShift with hosted control planes lets you choose an alternative CNI at cluster creation. INK certification gives teams standardizing on Cilium a supported option for that application network.
What does INK bring to production networking and policy?
Red Hat OpenShift provides the application platform, and INK is a supported CNI option for teams that choose a Cilium-based networking and policy model. It combines a hardened Cilium distribution with enterprise engineering support from the team behind Cilium. Across supported Kubernetes environments, teams can carry familiar Cilium-based networking, policy, and Hubble visibility practices between clusters, with feature scope defined by each platform and version. They can set guardrails, delegate policy to application teams, and trace traffic with workload context while application teams continue to work in the platform they operate.
Red Hat OpenShift provides the application platform, and INK is a supported CNI option for teams that choose a Cilium-based networking and policy model. It combines a hardened Cilium distribution with enterprise engineering support from the team behind Cilium. Across supported Kubernetes environments, teams can carry familiar Cilium-based networking, policy, and Hubble visibility practices between clusters, with feature scope defined by each platform and version. They can set guardrails, delegate policy to application teams, and trace traffic with workload context while application teams continue to work in the platform they operate.
The below walkthrough shows a ARO deployment with Isovalent Networking for Kubernetes.
Deploying Microsoft Azure Red Hat OpenShift with Isovalent Networking for Kubernetes
When an application reports a failed request, the platform team needs to connect that report with the network decision that affected it. For teams running INK, Hubble adds Kubernetes workload context and policy verdicts to flow data, so they can see which workloads were communicating and whether a connection was allowed or dropped.
Teams that configure Timescape with persistence can retain flow history for later investigation. They can inspect the period around a reported issue, compare allowed and dropped paths, and relate the traffic to a policy change. The Red Hat OpenShift walkthrough shows how a historical flow can expose a policy gap and guide a narrower rule, connecting live traffic evidence back to policy review.
Christian recently published a walkthrough and supporting blog post covering how the eBPF-powered Hubble Timescape capabilities from Isovalent can enhance network flow data for application teams running their workloads on Red Hat OpenShift.
With INK's Isopolicy tooling, teams can lint policy definitions and simulate which flows a proposed change would allow or deny before rollout. A team tightening access can identify missing labels or overlapping rules while the change is still under review.
How does certification build on our Red Hat partnership?
This announcement builds on the work behind our Red Hat OpenShift certification. Isovalent, a Cisco company, and Red Hat have worked together on integration and validation to support customers using Cilium-based networking with Red Hat OpenShift.
As a Red Hat-certified CNI plugin, Isovalent can now support platform teams using Azure Red Hat OpenShift with a verified combination of the application platform and its underlying network.
"Isovalent is proud to be a supported CNI solution for Azure Red Hat OpenShift. Isovalent's Networking for Kubernetes is a Red Hat-certified CNI plugin for Red Hat OpenShift, and we have customers that are already using the solution on Azure Red Hat OpenShift. Red Hat and Isovalent have been long-term partners in our customer's success in deploying advanced Kubernetes networking for container, AI, and virtual machine workloads on Red Hat OpenShift." - Chris Porter, Director, Product Management, Cisco
Organizations can now deploy Isovalent Networking for Kubernetes with confidence on:
- Traditional Red Hat OpenShift clusters – across on-premises and cloud infrastructure
- Red Hat OpenShift Hosted Control Planes – certified and supported
- Red Hat OpenShift on AWS – fully supported for hybrid cloud deployments
- Azure Red Hat OpenShift - fully supported for hybrid cloud deployments (this blog)
Ready to take the next step?
Contact our sales team to discuss how Isovalent Networking for Kubernetes can help your organization, or join one of our upcoming webinars to see our software in action and learn directly from our experts.
Schedule a Demo With Our Engineers
Learn how our solution map to your challenges.
Dean Lewis, Senior Technical Marketing Engineer