[RFC-0010] Introduce object-level workload identity for OCIRepository #1790
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
71 tasks
matheuscscp
force-pushed
the
rfc-0010-oci
branch
3 times, most recently
from
1f5fa0b to
fa56e1f
Compare
stefanprodan
changed the title
…istry APIs Signed-off-by: Matheus Pimenta <[email protected]>
stefanprodan
approved these changes
May 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Depends on: fluxcd/pkg#919
Part of: fluxcd/flux2#5022
Closes: fluxcd/pkg#642
I tested this PR in the following setups:
OCIRepositoryAWS:
Azure:
GCP:
OCI
HelmRepositoryandHelmChartThe
HelmRepositoryAPI does not havespec.serviceAccountName(neitherspec.proxySecretRefbtw). I'll leave it for the future (honestly I'd rather never add those two to force people to useOCIRepositoryfor OCI helm charts instead).AWS:
Azure:
GCP: