asset-relocation-tool-for-kubernetes
asset-relocation-tool-for-kubernetes copied to clipboard
vmware-tanzu
A tool for relocating Kubernetes Assets
Make sure that the examples point to publicly available repositories, i.e distribution harbor https://projects.registry.vmware.com/ although better if we use Docker HUB or similar. Similar exercise about accessing to the CI
Currently, it seems that the project relies on a private concourse CI instance. We need to - [ ] Make sure that the CI is publicly readable - [ ]...
Additionally we need to tackle the throttling issue. ``` + relok8s chart move source-chart/test-chart-product-0.2.15.tgz --yes --image-patterns image-patterns.yaml --registry harbor-repo.vmware.com --repo-prefix tanzu_isv_engineering_private Pulling index.docker.io/library/nginx:stable... Error: failed to pull original images: failed...
Make sure we are consistent with the naming, flags and CLI structure. * Images hint file * Flag names * ... This should apply to both documentation and examples.
For example, the following command shows the same relocation twice, it should be enough to show it once. ``` harbor-repo.vmware.com/tanzu_isv_engineering/tiny:tiniest => projects.registry.vmware.com/relocated/example2/tiny:tiniest (sha256:adf10351862ad5351ac2e714e04a0afb020b9df658ac99a07cbf49c0e18f8e43) ``` ``` $ relok8s chart move --image-patterns...
If a chart contains a global image registry value, we could possibly update that value many times, resulting in a strange output: values.yaml ``` global: imageRegistry: docker.io image: repository: bitnami/wordpress...
We are currently checking if an image exists on a tag by tag basis. imagine if the helm chart has three images: * `myimage:latest` * `myimage:1` * `myimage:1.2.3` and all...
Currently, the hints file format is a flat list of images. That does not leave any room for additional metadata such as the version of the schema/templating mechanism used. Having...
Currently we have the following rewrite due to some extra functionality required by our yamlops libary that is (or at least was) missing in upstream yaml ``` replace gopkg.in/yaml.v3 =>...
If while using relok8s library directly, no path is provided in the Target property, a spurious file name is created like this one `'%!(EXTRA string=mariadb, string=10.0.2)'` The library should require...