-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vitess-operator not managing/creating clusters in other namespaces #236
Comments
It looks like if you want to run in vitess different than operator you need an extra service account for vitessbackupstorage-subcontroller. |
{"level":"error","ts":1679307069.7949412,"msg":"Reconciler error","controller":"vitessbackupstorage-controller","object":{"name":"mgdmc-vitess-3f13cfd5","namespace":"vitess"},"namespace":"vitess","name":"vitess-3f13cfd5","reconcileID":"017bdf9f-fd82-487a-a05a-7cf9d9d68f26","error":"pods "vitess-3f13cfd5-vitessbackupstorage-subcontroller" is forbidden: error looking up service account vitess/vitess-operator: serviceaccount "vitess-operator" not found","stacktrace":"sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.1/pkg/internal/controller/controller.go:326\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.1/pkg/internal/controller/controller.go:273\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.1/pkg/internal/controller/controller.go:234"} |
It seems the operator takes a It seems we need to deploy one operator per namespace but I would expect an operator to be able to work accross multiple namespaces by default. |
Hey all, thanks for showing interest in this. I will try to pick this up either in this major release or the next one. I'll keep this issue updated. |
any updates on the feature 👋 I seems to be an essential feature to separate the operator and the different clusters it manages in different namespaces |
Hello everyone, please see #666 for the proposed solution. |
Hey,
I have the following problem:
I want to run the vitess-operator in the namespace "operators-vitess-operator" which works.
What doesn't work is to use the 101_initial_cluster.yaml and to deploy the cluster in the namespace "operators-vitess-example".
I can only deploy clusters in the namespace of the operator.
Here is the operator.yaml:
And that's my 101_initial_cluster.yaml:
If you search for "namespace:" you can see the diffs compared with the examples from the upstream.
Is it possible to manage clusters/run in other namespaces? I've found this: https://giters.com/vitessio/vitess/issues/8172
Thank you in advance!
Best regards,
Kai
The text was updated successfully, but these errors were encountered: