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.

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

Enable networkpolicy enforcement for nasa-veda hub #4652

Open
3 tasks
yuvipanda opened this issue Aug 22, 2024 · 2 comments
Open
3 tasks

Enable networkpolicy enforcement for nasa-veda hub #4652

yuvipanda opened this issue Aug 22, 2024 · 2 comments

Comments

@yuvipanda
Copy link
Member

yuvipanda commented Aug 22, 2024

With #4576, the nasa-veda cluster is a multi-tenant cluster with a public access component. We should enable network policy enforcement here.

Ref NASA-IMPACT/veda-jupyterhub#47 which tracks the overall issue.

Definition of done

  • Network Policy enforcement is active on the nasa veda cluster
  • There's some documentation on how this can be enabled for other clusters
  • Only HTTP, HTTPS and DNS to the external internet is available on the Binder

Timeline

This needs to be fully complete before end of september, as that's the quarterly cadence for the VEDA project

@consideRatio
Copy link
Contributor

Related tech issue in eksctl: eksctl-io/eksctl#7770, which is relevant following AWS announcement: https://aws.amazon.com/blogs/containers/amazon-vpc-cni-now-supports-kubernetes-network-policies/.

@yuvipanda
Copy link
Member Author

I opened #4653 to track refinement of this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants