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.

Sign up for GitHub

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

Jump to bottom

Document that we can only have a single object-store per namespace #1391

Closed
ramondeklein opened this issue Jan 12, 2025 · 0 comments · Fixed by #1392
Closed

Document that we can only have a single object-store per namespace #1391

ramondeklein opened this issue Jan 12, 2025 · 0 comments · Fixed by #1392
Assignees
@djwfyi

Comments

@ramondeklein
Copy link
Contributor

I couldn't find the requirement that MinIO operator can only deploy a single object-store per namespace and that we recommend to use a dedicated namespace for the object-store (so not adding other services in the same namespace). We may want to add it to the following pages:

See minio/operator#2381
@djwfyi djwfyi self-assigned this Jan 13, 2025
djwfyi added a commit that referenced this issue Jan 13, 2025
@djwfyi
Adds information for unique tenant namespaces.
29af93d 
Closes #1391

Adds information about changes to erasure code to MNMD deploys.

Closes #1365
@djwfyi djwfyi mentioned this issue Jan 13, 2025
Merged
@djwfyi djwfyi closed this as completed in 9e7388c Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@djwfyi djwfyi

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Bug fixes for two issues minio/docs
2 participants
@ramondeklein @djwfyi