What would you like to be added:
Switching default namespace of ops-pod to 'kube-system'
Why is this needed:
Currently it gets the namespace from the context which is defined via the kubectl config and this points to default if I use gardenctl and target a cluster.
The problem with putting the ops-pod in the default namespace is that due to the podSecurity configuration it is not allowed to start privileged containers there.
Any objections for changing the default to kube-system and not reading it from the config so we can actually start the ops-pod without having to manually provide the namespace?
What would you like to be added: Switching default namespace of ops-pod to 'kube-system'
Why is this needed:
Currently it gets the namespace from the context which is defined via the kubectl config and this points to
default
if I usegardenctl
and target a cluster.The problem with putting the ops-pod in the default namespace is that due to the podSecurity configuration it is not allowed to start privileged containers there.
Any objections for changing the default to kube-system and not reading it from the config so we can actually start the ops-pod without having to manually provide the namespace?