Closed jack1902 closed 1 year ago
TL;DR - skaffold config set default-repo anywhere.io
will result in things being happy with explicitRegistry. But without a default-repo you can't use explicitRegistry
approach
Going to close this as I believe it is something the user would need to define to overcome
Expected behavior
skaffold dev
should result in the image being built from the gradle project usingjib
. This works when i use https://skaffold.dev/docs/renderers/helm/#helm-strategy-split-repository-and-tag but when i attempt to use https://skaffold.dev/docs/renderers/helm/#helmexplicitregistry-strategy-split-registry-repository-and-tag it doesn'tActual behavior
skaffold dev
results in an image built without the registry which is pushed into the cluster, but the<key>.registry
isn't set either resulting in my defaults kicking in within the helm-chart and the cluster attempts to pull a non-existent image.If i do
skaffold dev --default-repo docker.io
for example, it functions but i can't see a way to specify the registry within the skaffold.yaml else i have to ensure that all developers using the skaffold files have a default value set globally (not a biggy but might be worth calling out in the docs that if you intend to use explicitRegistry, one must ensure they set a default repo)Additionally, if i have:
referring to it seems ugly (and i'm not sure it works?) - prehaps a
name
on the artifact asimage1
would be friendly to refer to it withinsetValueTemplates
as it is really messy otherwiseInformation
Steps to reproduce the behavior
skaffold <command>
Additional Context
I'm using the explicit registry as i have to support a multi-pod helm-chart. By making use of
global.image.registry
i can simply specify different registries for all images in the chart without having to alter each registry one at a time within their values)