carvel-dev / carvel-dev/imgpkg
Explore the possibility of replacing the iaas keychain with ggcr k8schain
- Dominant language
- Go
- Stars
- 284
- Forks
- 70
- PR merge metrics
- No merged PRs in 30d
Description
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: https://github.com/sigstore/cosign/pull/1279
Contributor guide
Research direction
Start by locating the current iaas keychain implementation and the forced git patch for github.com/vdemeester/k8s-pkg-credentialprovider. Compare them with the k8s keychain package introduced in ggcr 0.8.0 and the usage shown in sigstore/cosign#1279; done means the replacement works and the patch can be removed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- infrastructure
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100