-
Notifications
You must be signed in to change notification settings - Fork 806
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deploying k8s to Azure does not automatically obey Network Policies #1526
Comments
@sgibson91 yepp! Kubernetes does not by default come with something, called a controller, that enforces what is described in k8s networkpolicy resources. On GKE you can get that automatically installed if you press something similar in the k8s cluster setup. For the documentation, it should be a general note about this alongside specific cloud provider implementation details on how to go about setting up a controller that can enforce the policies. In the CI/CD testing of this repo, we install this manually into the k8s cluster - project calico. Lines 136 to 162 in de3a30b
|
As we have discovered in jupyterhub/mybinder.org-deploy#1154 (comment), network policies defined in helm charts won't automatically be obeyed as expected when using a k8s cluster on Azure.
To enforce this, the k8s cluster needs to be deployed into a vnet with network policies enabled. Currently, this must be done at the deployment stage and cannot be retroactively applied to existing clusters.
I can contribute some documentation on how to set up a vnet with network policies and deploy the cluster into it 🙂
The text was updated successfully, but these errors were encountered: