-
Notifications
You must be signed in to change notification settings - Fork 23
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
Use only subm cluster to recover broker-info.subm #621
Conversation
🤖 Created branch: z_pr621/Jaanki/only_subm_recover |
You have successfully added a new Grype configuration |
f9a0765
to
27d21a2
Compare
7f44bbe
to
85fc13d
Compare
85fc13d
to
aa49c2f
Compare
subctl uses its own Broker RBAC permissions. New permissions are recently added in subctl. Sync those permissions in operator repo as well because these are used by ACM or other third parties. Depends on submariner-io/subctl#621 Signed-off-by: Janki Chhatbar <[email protected]>
adf5c70
to
c694175
Compare
c694175
to
b33d771
Compare
...instead of specifying both Broker and Submariner clusters. Add required RBAC permissions for the client cluster to access the Broker. System tests are also accordingly adjusted. Epic: submariner-io/enhancements#143 Signed-off-by: Janki Chhatbar <[email protected]>
b33d771
to
77da496
Compare
🤖 Closed branches: [z_pr621/Jaanki/only_subm_recover] |
subctl uses its own Broker RBAC permissions. New permissions are recently added in subctl. Sync those permissions in operator repo as well because these are used by ACM or other third parties. Depends on submariner-io/subctl#621 Signed-off-by: Janki Chhatbar <[email protected]>
Epic: submariner-io/enhancements#143
Signed-off-by: Janki Chhatbar [email protected]