We are very excited to announce Calico v3.3. Here are some highlights from the release.
With Calico v3.3, you can enable the calico/node container to behave as a route reflector on particular nodes in the cluster. calico/node in route reflector mode now fully supports route reflector clustering, route reflector peering with external routers, and the full set of BGP configuration options supported by Calico. This functionality replaces the calico/routereflector container, which is now deprecated.
In Calico v3.3, you can now use node labels and selectors to define BGP peering relationships between calico/node instances. This allows for easier management of BGP peer configuration in a way that scales automatically with your cluster. Combined with the in-cluster route reflector feature, this provides a powerful model for defining how routes are distributed within the cluster.
When using Calico IPAM, you can now configure the block size allocated to each host for each IP Pool. The default block size of /26 for IPv4 provides blocks of 64 addresses. For details refer to the Project Calico IP Pool documentation. Additionally, cluster administrators can now define specific IP pools to be used for particular Kubernetes namespaces using namespace annotations.
Kubernetes 1.12 includes alpha Stream Control Transmission Protocol (SCTP) support. Calico v3.3 has been updated to support SCTP if included in your network policy spec.
Get updates on blog posts, new releases and more!