While upgrading the components for 1.29, I noticed that toolforge_get_versions.sh shows some outdated charts both in tools and toolsbeta:
fnegri@tools-bastion-12:~/toolforge-deploy$ ./utils/toolforge_get_versions.sh | component | type | package name | version | comment | | :-------: | :--: | :----------: | :-----: | :-----: | | api-gateway | chart | api-gateway | api-gateway-0.0.64-20250303171648-bd834b88 | | | builds-api | chart | builds-api | builds-api-0.0.180-20250310171252-3a5bd08b | | | builds-builder | chart | builds-builder | builds-builder-0.0.121-20241003135043-98c2199c | toolforge-deploy has builds-builder-0.0.127-20250310170709-62faa3b3 | | builds-cli | package | toolforge-builds-cli | 0.0.19 | | | calico | chart | calico | calico-0.0.14-20240920191533-f94f2f8d | toolforge-deploy has calico-0.0.15-20241104101859-e2c4ee9b | | cert-manager | chart | cert-manager | cert-manager-v1.15.3 | | | components-api | chart | components-api | components-api-0.0.19-20241001092739-d389755b | toolforge-deploy has components-api-0.0.82-20250306090549-677c59f7 | | components-cli | package | toolforge-components-cli | missing | | | envvars-admission | chart | envvars-admission | envvars-admission-0.0.25-20250304093736-6bb51ac3 | | | envvars-api | chart | envvars-api | envvars-api-0.0.65-20250303153943-68878700 | | | envvars-cli | package | toolforge-envvars-cli | 0.0.12 | | | image-config | chart | image-config | image-config-0.0.20-20240209102849-75f6a5f8 | | | ingress-admission | chart | ingress-admission | ingress-admission-0.0.57-20250304210417-f60db3c7 | | | ingress-nginx-gen2 | chart | ingress-nginx-gen2 | ingress-nginx-4.11.2 | | | jobs-api | chart | jobs-api | jobs-api-0.0.359-20250311172027-e7e0ea6e | | | jobs-cli | package | toolforge-jobs-framework-cli | 16.1.8 | | | jobs-emailer | chart | jobs-emailer | jobs-emailer-0.0.54-20250304203340-d628ac53 | | | kyverno | chart | kyverno | kyverno-3.2.6 | | | maintain-harbor | chart | maintain-harbor | maintain-harbor-0.0.20-20250310171918-609fd0a4 | | | maintain-kubeusers | chart | maintain-kubeusers | maintain-kubeusers-0.0.171-20241105173021-bf5186a3 | | | registry-admission | chart | registry-admission | registry-admission-0.0.57-20250306095410-d4fed2c9 | | | toolforge-cli | package | toolforge-cli | 0.3.5 | | | toolforge-weld | package | python3-toolforge-weld | 1.6.8 | | | tools-webservice | package | toolforge-webservice | 0.103.15 | | | volume-admission | chart | volume-admission | volume-admission-0.0.63-20250311102045-0ca3b79d | | | wmcs-k8s-metrics | chart | wmcs-metrics | wmcs-k8s-metrics-0.0.20-20240628101504-9ed20c1f | toolforge-deploy has wmcs-k8s-metrics-0.0.21-20241104102245-a6f60a0d |
@dcaro found this is an issue caused by our ./deploy.sh script using helmfile apply instead of helmfile sync. helmfile apply only updates the installed chart if it finds a diff in the k8s resources.