GoogleContainerTools/skaffold
View on GitHubChange the explanation of "default repo" setting in the doc to reflect actual implementation
Open
#1,516 opened on Jan 23, 2019
area/default-repoarea/docsbugbash/q4-2022fixithelp wantedjuly-chillkind/documentation
Repository metrics
- Stars
- (12,822 stars)
- PR merge metrics
- (Avg merge 3d 6h) (16 merged PRs in 30d)
Description
Expected behavior
Describe that 3rd default-repo config option described in the doc depends on kubectl context, not global. https://skaffold.dev/docs/concepts/#image-repository-handling
Actual behavior
It's documented as "skaffold’s global config", which is misleading. (Though ~/.skaffold/config is global to all command call, the default repo setting is not "global")
Information
- Skaffold version: v0.20.0
- Operating system: Debian 9.6
- Contents of skaffold.yaml:
apiVersion: skaffold/v1beta2
kind: Config
build:
artifacts:
- image: frontendservice
context: src/frontend
- image: arrayparseservice
context: src/arrayparse
- image: addnumberservice
context: src/addnumber
deploy:
kubectl:
manifests:
- ./k8s-manifests/**.yaml
profiles:
- name: gcb
build:
googleCloudBuild:
diskSizeGb: 30
machineType: N1_HIGHCPU_32
timeout: 4000s
Steps to reproduce the behavior
- Set
artifacts/imagewithout target repo path. - Call
skaffold config set default-repo <REPO>in some kubectl context - Change kubectl context
- See the log
The push refers to repository [docker.io/library/xxxxxx]and fail to deploy images duringskaffold dev/run