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

Parameterize registry path #2581

Closed
bgrant0607 opened this issue Nov 24, 2014 · 3 comments
Closed

Parameterize registry path #2581

bgrant0607 opened this issue Nov 24, 2014 · 3 comments
Labels
area/extensibility priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.

Comments

@bgrant0607
Copy link
Member

Currently our objects are all stored under /registry/... This is hostile to extension to new API groups and plugins, as well as to sharing an etcd instance with other uses. Changing the default path would be a breaking change, but we should parameterize the path so people deploying Kubernetes can choose where the data should go (e.g., /kubernetes/registry/core/).
@erictune
Copy link
Member

Doing this in a non-breaking way will be easier once kubelets stop reading from etcd: #2483

@bgrant0607
Copy link
Member Author

True, but if we don't change the default, it's not breaking.

@goltermann goltermann added the priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. label Nov 26, 2014
@bgrant0607
Copy link
Member Author

Closing in favor of #3476.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/extensibility priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@bgrant0607 @erictune @goltermann