You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For some security reasons, some users are given a single namespace to play with , and cannot create another namespace.
The current kustomization prevents from installing the operator in other namespace than the default chaostoolkit-crd namespace.
To change the installation namespace, two steps are required:
changes the namespace in kustomization.yaml files (depending on the overlay)
changes the default command for the container in the deployment, to listen to another namespace (otherwise the operator will not work and remain silent)
The text was updated successfully, but these errors were encountered:
This is tricky. kustomize doesn't support on the fly parameters from its CLI. So, either we document how to simply edit these files indeed (is it an "advanced" case afterall?) or we consider that kustomize is not the right solution and look elsewhere (helm for instance).
Helm would bring us a little more exposure but that's a different discusion. So, I'm in favour of keeping kustomization files the main approach as slong as we can edit in a single place only perhaps? to keep things easy.
For some security reasons, some users are given a single namespace to play with , and cannot create another namespace.
The current kustomization prevents from installing the operator in other namespace than the default
chaostoolkit-crd
namespace.To change the installation namespace, two steps are required:
The text was updated successfully, but these errors were encountered: