-
Notifications
You must be signed in to change notification settings - Fork 455
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
Which version will the return name not be fixed with 'minio'? #2125
Comments
At least return a fixed name related with instance's id or namespace? It's better than a fixed constant string 'minio'. |
Having a fixed name makes it easier to search for it. There will be only one |
Yes, you are right. But if use t.ObjectMeta.Name or t.ObjectMeta.Namespace as its name, it still can be the only one in each namespace. Meanwhile, its scope will not be the global of entire cluster. |
We wanted to keep it that way on purpose, so you are not allowed to run more than one tenant per namespace. You are free to use your own stateful set and achieve what you want. An operator is meant for sensible deployment patterns that we recommend. We are not interested in turning this into a complex configuration. This project would suffer, it is out of the scope at this moment. |
it is namespace specific already, the SVC name DNS is scoped via namespace |
Okey. Thank for reply. |
operator/pkg/apis/minio.min.io/v2/names.go
Line 61 in 7ae65b2
The text was updated successfully, but these errors were encountered: