Skip to content
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

Closed
iamjackhu opened this issue May 17, 2024 · 6 comments
Closed

Which version will the return name not be fixed with 'minio'? #2125

iamjackhu opened this issue May 17, 2024 · 6 comments

Comments

@iamjackhu
Copy link

// This is possible because each namespace has only one Tenant

@iamjackhu
Copy link
Author

At least return a fixed name related with instance's id or namespace? It's better than a fixed constant string 'minio'.

@iamjackhu iamjackhu changed the title Which version the return name will not be fixed 'minio'? Which version will the return name not be fixed with 'minio'? May 17, 2024
@ramondeklein
Copy link
Contributor

Having a fixed name makes it easier to search for it. There will be only one minio service per namespace, so there should be no problem.

@iamjackhu
Copy link
Author

iamjackhu commented May 20, 2024

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.

@harshavardhana
Copy link
Member

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.

@harshavardhana
Copy link
Member

global of entire cluster.

it is namespace specific already, the SVC name DNS is scoped via namespace

@iamjackhu
Copy link
Author

Okey. Thank for reply.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants