Kubernetes driver: Add ability to specify imagePullSecrets as a driver opt
Open
Nobody has claimed this yet.
kind/enhancement
status/triage
- Dominant language
- Go
- Stars
- 4.5k
- Forks
- 682
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 29
Description
Description
In certain situations it would be helpful to be able to specify the imagePullSecrets as a driver opt on docker buildx create.
For example in a CICD scenario where different teams have their own set of credentials but no access to the kubernetes cluster to set them up in the service account.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the docker buildx create command and trace how Kubernetes driver opts are parsed and passed to the driver. Compare the existing handling of imagePullSecrets and determine the expected opt format; done means credentials can be supplied per buildx create invocation without changing the Kubernetes service account.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go, kubernetes
- Domain
- cli, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100