-
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
recover-broker-info should be able to use secrets #631
Comments
This issue has been automatically marked as stale because it has not had activity for 60 days. It will be closed if no further activity occurs. Please make a comment if this issue/pr is still valid. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further |
subctl recover-broker-info
relies on the CA and token stored in either theSubmariner
orServiceDiscovery
objects. Since we want to stop storing these, we should try to find a way to make it work using only secrets. This might not be possible directly, in which case we might need to go through an in-cluster pod: in the cluster we have access to, start a pod, mount the secrets there, and use that to access the broker.The text was updated successfully, but these errors were encountered: