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

Add a namespaceOverride option for Helm deployment #2670

Closed
jgardner04 opened this issue Sep 24, 2020 · 1 comment
Closed

Add a namespaceOverride option for Helm deployment #2670

jgardner04 opened this issue Sep 24, 2020 · 1 comment
Labels
component/integrations good first issue These are great first issues. If you are looking for a place to start, start here! help wanted We would love help on these issues. Please come help us! stale A stale issue or PR that will automatically be closed.

Comments

@jgardner04
Copy link

Is your feature request related to a problem? Please describe.
When deploying the loki-stack chart as a dependent chart, Helm limitations require that it be deployed into the same namespace as my primary application. I am trying to have the loki-stack deployed into a separate namespace from my primary application.

Describe the solution you'd like
I'd like to see an option for namespaceOverride where I could define the namespace for the chart allowing me to control the location of the sub chart deployment.

It appears that this is already a value in the grafana chart.

Describe alternatives you've considered
The alternative would be to deploy the Loki stack as a separate deployment from my main application.

@cyriltovena cyriltovena added component/integrations help wanted We would love help on these issues. Please come help us! good first issue These are great first issues. If you are looking for a place to start, start here! labels Sep 25, 2020
@stale
Copy link

stale bot commented Oct 25, 2020

This issue has been automatically marked as stale because it has not had any activity in the past 30 days. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale A stale issue or PR that will automatically be closed. label Oct 25, 2020
@stale stale bot closed this as completed Nov 1, 2020
cyriltovena pushed a commit to cyriltovena/loki that referenced this issue Jun 11, 2021
* disabling of chunks write dedupe

Signed-off-by: Sandeep Sukhani <[email protected]>

* minor nits suggested from PR review

Signed-off-by: Sandeep Sukhani <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/integrations good first issue These are great first issues. If you are looking for a place to start, start here! help wanted We would love help on these issues. Please come help us! stale A stale issue or PR that will automatically be closed.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants