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

specify namespace for all resources #220

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

sebhoss
Copy link

@sebhoss sebhoss commented Aug 16, 2021

This allows helm template users to specify --namespace something while generating YAML files. See helm/helm#3553 for details and possible (other) workarounds.

Note that without specifying --namespace while calling helm template, {{ .Release.Namespace }} defaults to default which might contradict what changed in #25.

This allows 'helm template' users to specify --namespace 'something' while generating YAML files. See helm/helm#3553 for details and possible (other) workarounds.

Note that without specifying --namespace while calling 'helm template', {{ .Release.Namespace }} defaults to 'default' which might contradict what changed in prometheus-msteams#25.
@Knappek
Copy link
Collaborator

Knappek commented Sep 8, 2021

Hi @sebhoss, I am sorry for the late reply. Thanks for this contribution!

@sebhoss
Copy link
Author

sebhoss commented Sep 8, 2021

No problem!

More importantly, the tests failure looks like a flaky github actions behavior? It seems that the cluster creation in the step before timed out and thus there were no nodes to deploy the chart to. Can you try re-running the pipeline to verify that or should I do something else instead?

@Knappek
Copy link
Collaborator

Knappek commented Sep 16, 2021

I am so sorry @sebhoss for the lack fo responses, I am so busy these days...Yeah looks like a flaky job, I just re-triggered.

@ayackel
Copy link
Contributor

ayackel commented Sep 13, 2022

Can we have this updated and added?

@sebhoss
Copy link
Author

sebhoss commented Sep 14, 2022

Solved the merge conflicts

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.

None yet

3 participants