-
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
MinIOJob with Tenant in different namespace not working #2290
Comments
I have reported the replies to Github, removed the comments and redacted the quotes. Unfortunately, we can't do much about this bots... |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Looks like you met a bug. MinioJob should have the namespace as tenant. |
Will sent a pr to fix that |
Thank you for your fast response and the fix. |
Now, you can set them with the same namespace. @chrmang |
I want to run a MinIOJob to create users and buckets in a different namespace than Tenant.
I followed documentation https://github.com/minio/operator/blob/master/docs/minio-job.md for creating resources
and https://min.io/docs/minio/kubernetes/upstream/developers/sts-for-operator.html to configure it for cross namespace.
access with
mc
works without any issues.The configuration:
namespace minio-tenant
namespace dev (using minio-tenant)
Expected Behavior
The MinIOJob is running
Current Behavior
MinIOJob ressource got
status.message: no policybinding
foundSteps to Reproduce (for bugs)
Apply provided config to 2 namespaces.
Your Environment
kubectl apply -k https://github.com/minio/operator?ref=v6.0.2
uname -a
):Linux storebot 6.6.0-odroid-arm64 #1 SMP PREEMPT Wed, 08 May 2024 07:36:13 +0000 aarch64 aarch64 aarch64 GNU/Linux
The text was updated successfully, but these errors were encountered: