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

Fix ClusterRoleBinding namespace setting on kubectl-minio #485

Merged
merged 1 commit into from
Feb 20, 2021

Conversation

cesnietor
Copy link
Contributor

Fixes issue #479 for clusterRoleBinding not being set correctly for defined namespaces.

Since rbacv1.ClusterRoleBinding.Subjects is not a pointer, we have to
replace the array instead of modifying the values.

To test:

  1. Build operator locally like :
 make build TAG="minio/operator:test" &&  kind load docker-image minio/operator:test
  1. Build plugin locally like
cd kubectl-minio && go build

3.and run :

 kubectl create ns minio-operator && ./kubectl-minio init -n minio-operator --image=minio/operator:test --output=false

This should create operator, console and you should be able to access operator with no 403 (forbidden) issues.

Since rbacv1.ClusterRoleBinding.Subjects is not a pointer, we have to
replace the array  instead of modifying the values
@cesnietor cesnietor self-assigned this Feb 19, 2021
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.

master/v4.0.0/c40ab9c operator does not appear to create a functional console
3 participants