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
{{ message }}
This repository has been archived by the owner on Jan 11, 2023. It is now read-only.
@jackfrancis I think there was some confusion during the NetworkPolicy / NetworkPlugin split. Calico requires the cluster be set to --networking=cni, not --networking=kubenet. I believe the recent changes are launching it with kubenet, which causes the behavior that OP is seeing.
Is this a request for help?:
Is this an ISSUE or FEATURE REQUEST? (choose one):
ISSUE
What version of acs-engine?:
v0.17.0
Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm)
default
What happened:
Calico network policy is not enforced.
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know:
Tested v0.16.2 and it works, also noticed Calico template has been upgrade recently, which likely causes this issue.
The text was updated successfully, but these errors were encountered: