Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Explore the possibility of replacing the iaas keychain with ggcr k8schain #326

Open
joaopapereira opened this issue Jan 27, 2022 · 0 comments
Open

Explore the possibility of replacing the iaas keychain with ggcr k8schain #326

joaopapereira opened this issue Jan 27, 2022 · 0 comments
Labels
carvel accepted This issue should be considered for future work and that the triage process has been completed good first issue An issue that will be a good candidate for a new contributor help wanted Extra attention is needed priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@joaopapereira
Copy link
Member

With version 0.8.0 of ggcr a new package was added to enable the use of a keychain in k8s. We should explore the possibility of using this same keychain instead of the iaas keychain we currently have in our code.

This will allow us to remove the git patch that we are forcing on the library: github.com/vdemeester/k8s-pkg-credentialprovider

Example of usage: sigstore/cosign#1279
@joaopapereira joaopapereira added good first issue An issue that will be a good candidate for a new contributor help wanted Extra attention is needed carvel accepted This issue should be considered for future work and that the triage process has been completed priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Jan 27, 2022
@joaopapereira joaopapereira mentioned this issue Aug 24, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
carvel accepted This issue should be considered for future work and that the triage process has been completed good first issue An issue that will be a good candidate for a new contributor help wanted Extra attention is needed priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
Carvel
Status: Prioritized Backlog
Milestone
No milestone
Development

No branches or pull requests
1 participant
@joaopapereira