If user is using their own local repo instead of nexus3.onap.org and the repo does not allow anonymous pull, almost all of pods result in ImagePullBackOff due to missing credentials in onap-docker-registry-key secret.
OS / ENVIRONMENT
Kubernetes version:
v1.18.18
Helm version:
v3.5.4
Kubernetes mode of installation:
CNI Used for Kubernetes:
Docker CE 19.03.15
type of installation:
1 master node + 5 worker nodes
OOM VERSION
honolulu, commit id = 27984d15f00aec3b4ed732e4710a264cb6d197d9
SUMMARY
If user is using their own local repo instead of nexus3.onap.org and the repo does not allow anonymous pull, almost all of pods result in ImagePullBackOff due to missing credentials in onap-docker-registry-key secret.
OS / ENVIRONMENT
Kubernetes version:
v1.18.18
Helm version:
v3.5.4
Kubernetes mode of installation:
CNI Used for Kubernetes:
Docker CE 19.03.15
type of installation:
1 master node + 5 worker nodes
OOM VERSION
honolulu, commit id = 27984d15f00aec3b4ed732e4710a264cb6d197d9
CONFIGURATION
override.yaml
STEPS TO REPRODUCE
helm deploy dev local/onap --namespace onap -f ~/onap/oom-override/override.yaml -f ~/onap/oom-override/minimum.yaml --set global.masterPassword=password --verbose --debug
EXPECTED RESULTS
All pods' status become Running/Completed
ACTUAL RESULTS
Image pull failed and got ImagePullBackOff state.
Secret onap-docker-registry-key is empty, even though repositoryCred is set in override.yaml :
vmuser@onap2-m1:~$ kubectl get secret -n onap onap-docker-registry-key -o yaml
apiVersion: v1
data:
.dockercfg: e30=
kind: Secret
(snipped)
(Note: base64 encoded e30= means {} )