We are very excited to announce Calico v3.6. Here are some highlights from the release.
Calico IPAM for Kubernetes API datastore
With Calico v3.6, you now have full feature parity for Calico IP address management (IPAM) irrespective of the datastore you are using with your Calico deployment. This enables all of Calico’s IP address management features, including:
- Multiple IP address pools
- Per-pod, per-namespace, and per-node pool specification
Upgrading existing clusters using Calico with host-local IPAM is seamless – simply apply the new v3.6 manifest and you’ll be using Calico IPAM!
Calico 3.6 has several enhancements for your OpenStack deployments for better operational efficiency and resiliency.
- If you have a multi-region OpenStack deployment, you can choose to map all of those regions into a shared Calico datastore, which then allows you to define cross-region Calico policies.
- We’ve improved our documentation about the labels you can use to define Calico policy in addition to OpenStack security groups, and have added the project parent ID label to facilitate policy between hierarchically organized projects.
Selectors with substring matching
With both Kubernetes and OpenStack, you can now write Calico policy with selectors that match on a label value substring instead of the whole label value. For example, you can write “role starts with ‘Security’” or “role contains ‘Engineer’”, whereas previously you could only specify a complete match “role == ‘Security Engineer’”.