dev deploy
with ###ZARF_REGISTRY###
values in helm chart
#2713
Labels
dev deploy
with ###ZARF_REGISTRY###
values in helm chart
#2713
Is your feature request related to a problem? Please describe.
zarf dev deploy
is useful for fast developer iterations on a package, leveraging "yolo" mode. However if a package uses the###ZARF_REGISTRY###
variable in its helm chart values adev deploy
will result in errors on the image name. While this is not often used, it is occasionally beneficial in some packages and probably should be supported indev deploy
.Describe the solution you'd like
When I
dev deploy
a package Zarf should check the values files for###ZARF_REGISTRY###
. If present that should be modified to the registry for a matching image from thezarf.yaml
list of images. This is the most "magical" solution.Describe alternatives you've considered
###ZARF_REGISTRY###
atdev deploy
time. This would generally work well, but would not support the case of multiple###ZARF_REGISTRY###
usages tied to different registries.zarf.yaml
schema for "devDeployValues" that would override other values files. This would cover all cases, but put more responsibility on the end user to handle the dev deploy scenario.###ZARF_REGISTRY###
identified in values.Additional context
This is not a common scenario, but in uds-core we use the
###ZARF_REGISTRY###
var to ensure that Istio proxy images are available in some edge cases.The text was updated successfully, but these errors were encountered: