-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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 embedded hashes for our well-known assets #16439
Use embedded hashes for our well-known assets #16439
Conversation
justinsb
commented
Mar 30, 2024
- Create assetdata
- Use embedded hashes for our well-known assets
ff03d07
to
349849c
Compare
349849c
to
119730f
Compare
119730f
to
c26edfd
Compare
14c8e69
to
8805d9a
Compare
Rather than downloading the hash every time, we can record the hashes for our well-known assets and bake them into the kOps binary. If the hash is not baked in, we will continue to fall-back to downloading it, this is important for new k8s versions, or where the user specifies a version of one of our well-known assets (such as containerd).
Some new releases, and the latest patch in each.
8805d9a
to
4ab4ccf
Compare
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 think some of the logic from the initial PR got lost somewhere. If I recall correctly we were removing all the unused binaries and architectures. Though this is a nit, we can address it later.
Thanks! 😄
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hakman The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |