You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
EDCOP currently integrates Multus v1.2 with Calico 3.0.4. After implementation of Multus v3.0, we should upgrade to the latest version of Calico to v3.1 (v3.1.3 as of this writing).
Additionally, integration of calico should be changed to utilize the Kubernetes API as the datastore. In the current version of EDCOP, we implement Calico with a separate etcd cluster dedicated to Calico. This was due to lack of network policies when using the kubernetes API store. This has been resolved in the latest version of Calico. An initial version of Calico with the Kubernetes API store was tested in a file called calico-multus-etcdless.yaml
According to the Calico Release Notes will provide a number of enhancements that may be beneficial to EDCOP:
IPVS instead of iptables implementation of kube-proxy
Global Network policies when using Kubernetes API as the datastore
A number of bug-fixes
The text was updated successfully, but these errors were encountered:
Relies on #44 for specifications
EDCOP currently integrates Multus v1.2 with Calico 3.0.4. After implementation of Multus v3.0, we should upgrade to the latest version of Calico to v3.1 (v3.1.3 as of this writing).
Additionally, integration of calico should be changed to utilize the Kubernetes API as the datastore. In the current version of EDCOP, we implement Calico with a separate etcd cluster dedicated to Calico. This was due to lack of network policies when using the kubernetes API store. This has been resolved in the latest version of Calico. An initial version of Calico with the Kubernetes API store was tested in a file called calico-multus-etcdless.yaml
According to the Calico Release Notes will provide a number of enhancements that may be beneficial to EDCOP:
The text was updated successfully, but these errors were encountered: