Skip to main content

Illumio Segmentation for Kubernetes

What's New in Release 5.4.0

Here's a summary of the new and enhanced features in this release.

Add support for Helm Chart with Argo CD

Starting in release 5.4.0, Illumio Core for Kubernetes can be deployed with the Argo CD tool, a convenient way of managing Helm Chart deployments. Valuable features of using Argo CD with Illumio Core for Kubernetes include:

  • Repeated resources are identified using a new argoCD variable (default value is false).

  • Supports unpairing with a new unpair option to clusterMode parameter.

  • Triggers a new rollout by using checksum annotations whenever a Secret or ConfigMap value changes in the repository.

  • Adds a new verbosity parameter as a value in values.yaml so it can be managed.

Add proxy support to C-VEN

A new Helm chart variable httpProxy was added, which sets the HTTP proxy URL to be used for Kubelink and C-VEN PCE requests, much like existing VEN proxy support.

Exclude or include host-networked workloads from PCE total workload count

Starting with 5.4.0, Kubelink does not create Kubernetes Workloads on PCE if the workload is in the host network. Pods running these workloads don't have a separate network namespace. Policy for these workloads must be part of the policy for Nodes. Added a new reportHostNetworkKubernetesWorkloads: true option to values.yaml to exclude host-networked Kubernetes Workloads from being counted in the PCE total workload calculation.

To count these workloads, turn on the reporting of workloads in the host network with the setting `includeHostNetworkWorkloads: true`. Workloads will be counted into Workload limits, and policy instructions for Pods in the host network will be ignored like in previous versions.

Report operating system of nodes for Azure, GKE, and OpenShift

C-VEN now accurately reports the OS of the node running on the cluster of underlying source to PCE, such as Azure, GKE, OpenShift, and the like.