Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[BUG] Egress from pods not restricted #164

Closed
sgibson91 opened this issue Dec 16, 2019 · 0 comments · Fixed by #172
Closed

[BUG] Egress from pods not restricted #164

sgibson91 opened this issue Dec 16, 2019 · 0 comments · Fixed by #172
Labels
bug Something isn't working

Comments

@sgibson91
Copy link
Collaborator

Describe the bug

The BinderHub helm chart creates a network policy that restricts egress to running pods, etc. However, when deploying on an Azure k8s cluster, this network policy is not enabled - see discussion in jupyterhub/mybinder.org-deploy#1154 where this bug was discovered for the Turing-Binder Federation cluster.

Expected behaviour

The egress of running pods is restricted.

Additional context

According to this Azure documentation, a network policy cannot be applied to an existing cluster. This means Hub23 would have to be entirely torn down, the YAML config for the network policy found and isolated, and then the cluster redeployed with a network policy enabled.

I've notified Tania of this problem - hopefully she can find some info out from the MSFT k8s team.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update docs to deploy cluster that obeys network policies alan-turing-institute/hub23-deploy
1 participant
@sgibson91