You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
running relok8s chart move ... --registry harbor-repo.vmware.com will result in:
Computing relocation...
...
Changes to be applied to wordpress/values.yaml:
.global.imageRegistry: harbor-repo.vmware.com
.global.imageRegistry: harbor-repo.vmware.com
This is confusing and could lead to uncertainty.
The text was updated successfully, but these errors were encountered:
Running with sub-charts, leads to having interleaved repeated rewrites:
Changes to be applied to wordpress/values.yaml:
.global.imageRegistry: harbor-repo.vmware.com
.image.repository: pwall/wordpress
.global.imageRegistry: harbor-repo.vmware.com
.metrics.image.repository: pwall/apache-exporter
.global.imageRegistry: harbor-repo.vmware.com
.volumePermissions.image.repository: pwall/bitnami-shell
.global.imageRegistry: harbor-repo.vmware.com
Changes to be applied to wordpress/charts/mariadb/values.yaml:
.image.repository: pwall/mariadb
Changes to be applied to wordpress/values.yaml:
.global.imageRegistry: harbor-repo.vmware.com
Changes to be applied to wordpress/charts/mariadb/values.yaml:
.metrics.image.repository: pwall/mysqld-exporter
Changes to be applied to wordpress/values.yaml:
.global.imageRegistry: harbor-repo.vmware.com
Changes to be applied to wordpress/charts/mariadb/values.yaml:
.volumePermissions.image.repository: pwall/bitnami-shell
Changes to be applied to wordpress/values.yaml:
.global.imageRegistry: harbor-repo.vmware.com
Changes to be applied to wordpress/charts/memcached/values.yaml:
.image.repository: pwall/memcached
Changes to be applied to wordpress/values.yaml:
.global.imageRegistry: harbor-repo.vmware.com
Changes to be applied to wordpress/charts/memcached/values.yaml:
.metrics.image.repository: pwall/memcached-exporter
Would you like to proceed? (y/N)
If a chart contains a global image registry value, we could possibly update that value many times, resulting in a strange output:
values.yaml
running
relok8s chart move ... --registry harbor-repo.vmware.com
will result in:This is confusing and could lead to uncertainty.
The text was updated successfully, but these errors were encountered: