-
Notifications
You must be signed in to change notification settings - Fork 66
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
Stop publishing sensitive information directly in CRs #1869
Comments
This ensures we rely only on the secret containing the broker access token. Fixes: submariner-io#1869 Signed-off-by: Stephen Kitt <[email protected]>
This ensures we rely only on the secret containing the broker access token. Fixes: submariner-io#1869 Signed-off-by: Stephen Kitt <[email protected]>
This ensures we rely only on the secret containing the broker access token. Fixes: submariner-io#1869 Signed-off-by: Stephen Kitt <[email protected]>
This ensures we rely only on the secret containing the broker access token. Fixes: submariner-io#1869 Signed-off-by: Stephen Kitt <[email protected]>
This ensures we rely only on the secret containing the broker access token. Fixes: submariner-io#1869 Signed-off-by: Stephen Kitt <[email protected]>
This ensures we rely only on the secret containing the broker access token. Fixes: submariner-io#1869 Signed-off-by: Stephen Kitt <[email protected]>
This ensures we rely only on the secret containing the broker access token. Fixes: submariner-io#1869 Signed-off-by: Stephen Kitt <[email protected]>
This ensures we rely only on the secret containing the broker access token. Fixes: submariner-io#1869 Signed-off-by: Stephen Kitt <[email protected]>
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 ensures we rely only on the secret containing the broker access token. Fixes: submariner-io#1869 Signed-off-by: Stephen Kitt <[email protected]>
This ensures we rely only on the secret containing the broker access token. Fixes: submariner-io#1869 Signed-off-by: Stephen Kitt <[email protected]>
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 ensures we rely only on the secret containing the broker access token. Fixes: submariner-io#1869 Signed-off-by: Stephen Kitt <[email protected]>
This ensures we rely only on the secret containing the broker access token. Fixes: submariner-io#1869 Signed-off-by: Stephen Kitt <[email protected]>
This ensures we rely only on the secret containing the broker access token. Fixes: submariner-io#1869 Signed-off-by: Stephen Kitt <[email protected]>
This PR/issue depends on:
|
This ensures we rely only on the secret containing the broker access token. Fixes: submariner-io#1869 Signed-off-by: Stephen Kitt <[email protected]>
Now that the PSK and broker token are stored in secrets, we should stop publishing them directly in CRs.
This won’t really improve security, but it will make CR dumps easier to read.
This follows on from submariner-io/submariner#326.
Depends on submariner-io/subctl#631
The text was updated successfully, but these errors were encountered: