Installing Robusta into separater ns

[AnaisUrlichs]

trafficstars

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Usually, when installing a helm chart, it will install all resources related to the deployment into a separate ns. However, when installing robusta, it does not create a new ns but installs everything into the default ns.

Describe the solution you'd like A clear and concise description of what you want to happen.

I would like a new ns to be created called robusta.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

N/A

Additional context Add any other context or screenshots about the feature request here.

I think it is common practice to have a separate ns so it would be nice if that was the case when installing the Robusta Helm Chart.

[aantn]

Thanks, makes sense.

@AnaisUrlichs would it be enough to just update the docs to recommend running helm install --create-namespace --namespace=robusta instead of helm install or should we be changing something in the chart? Do you have an example of another project that we can look at as reference?

[AnaisUrlichs]

Hmm, it would be nice if that would happen out of the box :D but now looking at some Helm Charts e.g. prometheus or our starboard chart, it seems like that is the go to -- so that should work

[aantn]

Cool, thanks.

[shfisher]

When you update the install instructions, don't forget to update upgrade instructions too

[shfisher]

Should be separate namespace by default. Another way can be collecting the desired namespace from user during installation script. You can add it to generated values, and inside the helm resources use namespace: {{ default "robusta" .Values.namespace }}

[aantn]

Thanks. It seems like the consensus is that we should be installing into a robusta namespace by default