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

Make prepending namespace to release name optional #220

Closed
b-t-927 opened this issue Apr 4, 2018 · 1 comment
Closed

Make prepending namespace to release name optional #220

b-t-927 opened this issue Apr 4, 2018 · 1 comment
Labels
kind/feature An issue that reports a feature (approved) to be implemented

Comments

@b-t-927
Copy link
Contributor

b-t-927 commented Apr 4, 2018

At the moment, I'm trying to keep deployments spread out per-namespace. For example, wordpress deploys go into the wordpress namespace.

However because release names have the chart name prepended you end up with a long and a bit redundant deployment name/service DNS name (ie wordpress-example-wordpress.wordpress.svc.cluster.local)

If there were some sort of way to have it be optional that would be great. Perhaps via some sort of option you can set in the spec in the API calls?
@prydonius prydonius added kind/feature An issue that reports a feature (approved) to be implemented component/ui Issue related to kubeapps UI priority/backlog and removed component/ui Issue related to kubeapps UI labels Apr 4, 2018
This was referenced May 24, 2018
Closed
Merged
@andresmgot
Copy link
Contributor

waiting for review at #330

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature An issue that reports a feature (approved) to be implemented
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@prydonius @b-t-927 @andresmgot