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

When executing Helm command you must be in the pelorus namespace #54

Closed
themoosman opened this issue Apr 22, 2020 · 4 comments · Fixed by #153
Closed

When executing Helm command you must be in the pelorus namespace #54

themoosman opened this issue Apr 22, 2020 · 4 comments · Fixed by #153
Assignees
@etsauer
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
Pelorus Roadmap Pelorus v1.3
Milestone
v1.3

Comments

@themoosman
Copy link
Collaborator

When executing the Helm commands to create an exporter, you must be in the pelorus namespace or the objects will be created in the current namespace. This occurs even when the --namespace command is passed as in helm template charts/exporter/ -f exporters/failure/values.yaml --namespace pelorus | oc apply -f-
@themoosman themoosman added the kind/bug Categorizes issue or PR as related to a bug. label Apr 22, 2020
@sbailleu sbailleu added this to To do in Pelorus Roadmap via automation Apr 27, 2020
@etsauer etsauer added this to the v1.2 milestone Jun 16, 2020
@etsauer etsauer modified the milestones: v1.2, v1.3 Jun 29, 2020
@kkoller kkoller self-assigned this Jul 7, 2020
@sbailleu sbailleu moved this from To do to In progress in Pelorus Roadmap Jul 7, 2020
@prakritikoller prakritikoller added this to To do in Pelorus v1.3 Jul 23, 2020
@etsauer
Copy link
Collaborator

etsauer commented Jul 24, 2020

Reading up on this issue, it seems like the preferred approach is to NOT include the namespace in the templates at all, and pass it via helm install --namespace pelorus. Are we ok with that approach?

helm/helm#5465

@etsauer etsauer self-assigned this Jul 27, 2020
@prakritikoller prakritikoller moved this from To do to In progress in Pelorus v1.3 Jul 27, 2020
@etsauer
Copy link
Collaborator

etsauer commented Jul 31, 2020

helm refactor is waiting on operator-framework/community-operators#2120

@etsauer etsauer linked a pull request Aug 11, 2020 that will close this issue
WIP: Helm refactor #153
Merged
@etsauer
Copy link
Collaborator

etsauer commented Aug 11, 2020

@themoosman we good to close this? The PR wasn't link so it didn't close automatically.

@themoosman
Copy link
Collaborator Author

Yes, this was fixed by #153

Pelorus Roadmap automation moved this from In progress to Done Aug 11, 2020
Pelorus v1.3 automation moved this from In progress to Done Aug 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@etsauer etsauer

Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
No open projects
Pelorus Roadmap
Done
Pelorus v1.3
  
Done
Milestone
v1.3
Development

Successfully merging a pull request may close this issue.

WIP: Helm refactor
3 participants
@themoosman @etsauer @kkoller