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

Allow adding additional ingress rules in network policy #1380

Merged
merged 2 commits into from
Aug 31, 2019

Conversation

yuvipanda
Copy link
Collaborator

If you have a prometheus server in a different namespace,
explicit 'from' stanzas are needed to make sure it can
have access to your hub and user pods.

This change allows individual administrators to make
these changes.

If you have a prometheus server in a different namespace,
explicit 'from' stanzas are needed to make sure it can
have access to your hub and user pods.

This change allows individual administrators to make
these changes.
Change networkPolicy.ingress to have same structure as
networkPolicy.egress. However, leave default ingress rule
in place so users don't accidentally break the hub
yuvipanda added a commit to yuvipanda/datahub-old-fork that referenced this pull request Aug 30, 2019
Adds a prometheus / grafana chart that uses GitHub for
authentication.

Currently, prometheus can't reach into hub / singleuser servers,
since z2jh doesn't support cross-namespace networkpolicy.
jupyterhub/zero-to-jupyterhub-k8s#1380 should
fix that.
@consideRatio
Copy link
Member

This LGTM! I like the change from extraRules to this!

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

Successfully merging this pull request may close these issues.

2 participants