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

Missing minio service name #2263

Merged
merged 1 commit into from
Aug 10, 2024

Conversation

pjuarezd
Copy link
Member

@pjuarezd pjuarezd commented Aug 9, 2024

Forgot to mention in example, credits to @allanrogerr

Forgot to mention in example, credits to @allanrogerr

Signed-off-by: pjuarezd <[email protected]>
@pjuarezd pjuarezd self-assigned this Aug 9, 2024
@harshavardhana harshavardhana merged commit c28fcf8 into minio:master Aug 10, 2024
21 checks passed
@@ -307,7 +307,7 @@ minio.<namespace>
minio.<namespace>.svc
minio.<namespace>.svc.<cluster domain>
*.<tenant-name>-hl.<namespace>.svc.<cluster domain>
*.<namespace>.svc.<cluster domain>
*.minio.<namespace>.svc.<cluster domain>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pjuarezd @allanrogerr It's a good idea to remove *.<namespace>.svc.<cluster domain> from the certificate. But why add *.minio.<namespace>.svc.<cluster domain>? The minio service is not a headless service, so it will always be addressed using minio.<namespace>.svc.<cluster domain> (already in the certificate). Only headless services need a wildcard domain...

PS: I think *.<tenant-name>.minio.<namespace>.svc.<cluster domain> on line 311 is obsolete too. You can't have services that have this amount of dots before the <namespace>.svc.<cluster domain>...

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

Successfully merging this pull request may close these issues.

5 participants