Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
kube-updater: Wire up main executable #23565
kube-updater: Wire up main executable #23565
Changes from all commits
c048682
26cd639
670e8cf
b6744bd
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where does it come from?
How can we update it when time comes?
(missing license header)
Can we add that as a comment?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I fetched this from the prod KMS, @tcsc asked at some point how we will share our signature key, so I suspect we'll advertise it somewhere in the docs at least.
I'll add a comment explaining where to find they key and what to do in case of rotation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hugoShaka @tcsc Would it make sense to store this public key as a separate file somewhere in the repo and embed using
go:embed
so it can potentially be reused in multiple places without hardcoding/copy-pasting?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, but if we dynamically load it we must be very careful not to update the file in place. In case of rotation, we might want to add a new validator for the new key instead of just replacing the key.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we share the key using a Teleport cdn endpoint?
I mean, you developed the updater to update our kube-agents but it still requires that someone updates the updater each time we pretend to rotate secrets.
If anyone using it to update their images starts seeing invalid signature errors, they will assume that we were hacked and images in our public repo aren't trusty.
Or worst, if they rely 100% on the updater and it stops updating images can lead to security vulnerabilities.
It will be difficult to reach everyone in case of a forced rotation caused by a leaked private key.
We can share both keys using the endpoint