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

Fix running multiple hubs in same cluster #923

Merged
merged 1 commit into from
Sep 11, 2018

Conversation

yuvipanda
Copy link
Collaborator

Cluster wide objects should be prefixed with the release name,
so we can have multiples hubs in the same cluster. For the
user-scheduler, this involves:

  1. RBAC ClusterRoles & RoleBindings
  2. Scheduler Name

Cluster wide objects should be prefixed with the release name,
so we can have multiples hubs in the same cluster. For the
user-scheduler, this involves:

1. RBAC ClusterRoles & RoleBindings
2. Scheduler Name
Copy link
Member

@consideRatio consideRatio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks this makes a lot of sense, we should support multiple hubs in different namespaces within the same cluster, even though we don't yet support multiple hubs in the same namespace.

@consideRatio consideRatio merged commit 4e57e2f into jupyterhub:master Sep 11, 2018
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.

3 participants