Fix gitea helm values to use existing image tag for memcached
Unable to install Release 17 due to error:
"gitea-charts" already exists with the same configuration, skipping
+ m 'Deploying Gitea'\''s Helm chart...'
+ local 'COLOR=\033[0;34m'
+ echo -e '\033[0;34mDeploying Gitea'\''s Helm chart...\033[0m'
Deploying Gitea's Helm chart...
+ helm install gitea gitea-charts/gitea --version=7.0.4 --namespace=gitea --values /usr/share/osm-devops/installers/mgmt-cluster/gitea/values-standalone-ingress-ssh22
22.yaml --set=gitea.admin.username=osm-admin '--set=gitea.admin.password='\''jf+8X(;%pN/]'\''' --create-namespace --wait
Error: INSTALLATION FAILED: context deadline exceeded
+ trap_EXIT
+ local ERR=1
+ goodbye 1
+++ date +%s
++ date --date=@302 --utc +%T
+ local DURATION=00:05:02
+ local CODE=1
+ cd /usr/share/osm-devops/installers/mgmt-cluster/gitea
+ '[' 1 == 0 ']'
+ '[' 1 == abort ']'
++ realpath --relative-to=/usr/share/osm-devops/installers/mgmt-cluster/gitea /usr/share/osm-devops/installers/mgmt-cluster/gitea/02-deploy-gitea.sh
+ m 'Oh no! 02-deploy-gitea.sh failed! 00:05:02' '\033[0;31m'
+ local 'COLOR=\033[0;31m'
+ echo -e '\033[0;31mOh no! 02-deploy-gitea.sh failed! 00:05:02\033[0m'
Oh no! 02-deploy-gitea.sh failed! 00:05:02
+ exit 1
Oh no! ALL-IN-ONE-Gitea-install.sh failed! 00:05:02
Oh no! 01-provision-aux-svc.sh failed! 00:05:16`
where the issue related to the image tag miss for gitea dependency "memcached"
> kubectl describe pods -n gitea gitea-memcached-d7d85f9fb-s5tvt
...
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 6m24s default-scheduler Successfully assigned gitea/gitea-memcached-d7d85f9fb-s5tvt to kubenfv-demo
Normal Pulling 4m54s (x4 over 6m24s) kubelet Pulling image "docker.io/bitnami/memcached:1.6.9-debian-10-r114"
Warning Failed 4m53s (x4 over 6m23s) kubelet Failed to pull image "docker.io/bitnami/memcached:1.6.9-debian-10-r114": rpc error: code = NotFound de
sc = failed to pull and unpack image "docker.io/bitnami/memcached:1.6.9-debian-10-r114": failed to resolve reference "docker.io/bitnami/memcached:1.6.9-debian-10-r114
": docker.io/bitnami/memcached:1.6.9-debian-10-r114: not found
Warning Failed 4m53s (x4 over 6m23s) kubelet Error: ErrImagePull
Warning Failed 4m41s (x6 over 6m22s) kubelet Error: ImagePullBackOff
Normal BackOff 78s (x21 over 6m22s) kubelet Back-off pulling image "docker.io/bitnami/memcached:1.6.9-debian-10-r114"
1.6.9-debian-10-r114 tag missed in https://hub.docker.com/r/bitnami/memcached/tags. But for some reasons memcached chart 5.9.0 uses it as a default image tag.
After fix:
...
+ m 'Deploying Gitea'\''s Helm chart...'
+ local 'COLOR=\033[0;34m'
+ echo -e '\033[0;34mDeploying Gitea'\''s Helm chart...\033[0m'
Deploying Gitea's Helm chart...
+ helm install gitea gitea-charts/gitea --version=7.0.4 --namespace=gitea --values /usr/share/osm-devops/installers/mgmt-cluster/gitea/values-standalone-ingress-ssh22
22.yaml --set=gitea.admin.username=osm-admin '--set=gitea.admin.password='\''&u)lfoU]U)b]'\''' --create-namespace --wait
NAME: gitea
LAST DEPLOYED: Fri Sep 5 16:51:21 2025
NAMESPACE: gitea
STATUS: deployed
REVISION: 1
NOTES:
1. Get the application URL by running these commands:
http://git.myexample.com/
+ m 'Waiting for Gitea to start...'
+ local 'COLOR=\033[0;34m'
+ echo -e '\033[0;34mWaiting for Gitea to start...\033[0m'
Waiting for Gitea to start...
+ kubectl rollout status statefulset/gitea --namespace=gitea --watch --timeout=1h
partitioned roll out complete: 1 new pods have been updated...
+ trap_EXIT
+ local ERR=0
+ goodbye 0
+++ date +%s
++ date --date=@49 --utc +%T
+ local DURATION=00:00:49
+ local CODE=0
+ cd /usr/share/osm-devops/installers/mgmt-cluster/gitea
+ '[' 0 == 0 ']'
++ realpath --relative-to=/usr/share/osm-devops/installers/mgmt-cluster/gitea /usr/share/osm-devops/installers/mgmt-cluster/gitea/02-deploy-gitea.sh
+ m '02-deploy-gitea.sh succeeded! 00:00:49' '\033[0;32m'
+ local 'COLOR=\033[0;32m'
+ echo -e '\033[0;32m02-deploy-gitea.sh succeeded! 00:00:49\033[0m'
02-deploy-gitea.sh succeeded! 00:00:49
+ exit 0
Waiting until the Ingress service IP address is available...
...
Edited by dmalovan