-
Notifications
You must be signed in to change notification settings - Fork 193
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
Store sensitive details in secrets #326
Comments
@roytman ^ |
This issue has been automatically marked as stale because it has not had activity for 120 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 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. |
bump |
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. |
bump |
See also #815 |
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 is still relevant. |
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. |
bump |
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 is still relevant. |
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. |
@skitt is working on this with PRs like submariner-io/submariner-operator#1687 |
@skitt can this be closed now or is there anything else needed? |
I’m trying to check, but Ideally we’d only use secrets to close this issue, but that has to wait for 0.13; perhaps we can track that as a separate issue. |
Everything that should be in a secret is now in a secret; I’ve filed submariner-io/submariner-operator#1869 to ensure we remove the non-secret occurrences in 0.13. |
@skitt anything we should update in our docs to reflect these changes? |
We don’t describe this in the docs currently, I’ve filed submariner-io/submariner-website#678 to make sure we don’t forget to change this situation (but it’s not required for 0.12 IMO, it’s only liable to create problems once we drop support for the non-secret variants). |
Things that can be stored on (ideally separate) secrets:
a) the ipsec-psk (or other cable engine related secrets)
b) the token/cert (just a copy of the service account secret created on the broker)
Secrets won't buy extra security because, with the right permissions can be extracted. But it will make it:
The text was updated successfully, but these errors were encountered: