Implement client-side APK discovery in apko
#1216
Merged
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.
The protocol follows a roughly similar handshake to OIDC discovery, hitting
{repository}/apk-configuration
, extracting thejwks_uri
and then recording each pem-encoded key as/etc/apk/keys/{kid}.rsa.pub
.I have tested this locally with both public and private APK repositories against
apk.mattmoor.dev
with the changes in: https://github.com/chainguard-dev/mono/pull/18431Once this lands, I can use this in e2e tests there, but those are somewhat 🐔 & 🥚