This message was deleted.
# general
a
This message was deleted.
m
Why did you move the ingress controller into the
kube-system
namespace in the first place?
m
We have a cyber use case where we wanted to inject istio side car into nginx pod
m
yes I understand, but why not use a separate namespace
ingress-nginx
?
ah I think I understand, you're talking about the packaged ingress controller. I would disable it via
Copy code
# /etc/rancher/rke2/config.yaml
disable:
  - rke2-ingress-nginx
m
I mean it's not hard and fast! We can use it. But since with RKE2 deployment ,ingress controller deployed automatically into kube-system. This we don't want to override the ingress controller deployment.
But if we disable it ,how I can deploy this package in other namespace?
m
if you disable the packaged ingress controller, you can just install another one with helm
m
Can not we override namespace or the Customizing Packaged Components with HelmChartConfig ? https://docs.rke2.io/helm#customizing-packaged-components-with-helmchartconfig
m
afaik you can't change the namespace with the helmchartconfig
👍 1
m
Can not we override namespace in helmchart config like below # /var/lib/rancher/rke2/server/manifests/rke2-ingress-nginx-config.yaml --- apiVersion: helm.cattle.io/v1 kind: HelmChartConfig metadata: name: rke2-ingress-nginx namespace: kube-system spec: valuesContent: |- controller: config: use-forwarded-headers: "true"