Open kastl-ars opened 1 month ago
Describe the bug Normally one can install a helm release into a discrete namespace by using helm install --namespace foo ....
helm install --namespace foo ...
This does not work with the retina chart, as it puts the helm release into that namespace, but the resources into the kube-system namespace.
kube-system
e.g. https://github.com/microsoft/retina/blob/main/deploy/legacy/manifests/controller/helm/retina/values.yaml#L47
If there is a technical reason for doing so, this should be documented. If not, this should be fixed to get the usual behaviour.
To Reproduce Steps to reproduce the behavior:
helm upgrade --install retina oci://ghcr.io/microsoft/retina/charts/retina \ --namespace retina \ --create-namespace \ --version $VERSION \ --namespace kube-system \ --set image.tag=$VERSION \ --set operator.tag=$VERSION \ --set logLevel=info \ --set enabledPlugin_linux="\[dropreason\,packetforward\,linuxutil\,dns\]"
helm ls -n retina
kubectl get pod,ds -n retina
kubectl get pod,ds -n kube-system
Expected behavior The chart should respect helm's --namespace argument
--namespace
Platform (please complete the following information):
In addition, the operator daemonset always gets deploy to kube-system, even if its configMap is created in e.g. the retina namespace.
retina
https://github.com/microsoft/retina/blob/main/deploy/legacy/manifests/controller/helm/retina/templates/operator.yaml#L6
Describe the bug Normally one can install a helm release into a discrete namespace by using
helm install --namespace foo ...
.This does not work with the retina chart, as it puts the helm release into that namespace, but the resources into the
kube-system
namespace.e.g. https://github.com/microsoft/retina/blob/main/deploy/legacy/manifests/controller/helm/retina/values.yaml#L47
If there is a technical reason for doing so, this should be documented. If not, this should be fixed to get the usual behaviour.
To Reproduce Steps to reproduce the behavior:
helm ls -n retina
and find the release there, but no pods or daemonsets (askubectl get pod,ds -n retina
shows)kube-system
namespace usingkubectl get pod,ds -n kube-system
Expected behavior The chart should respect helm's
--namespace
argumentPlatform (please complete the following information):