-
- Downloads
Setting `imagePullSecrets` to `ctaregsecret` for all pods
This allows to solve the recurrent docker login issue by passing the credentials to kubernetes as a secret. Indeed docker login credentials are valid for 3 months then it is over. We just need to pass the `ctareg` service account credentials in the `ctaregsecrets` and we are done. In addition `imagePullSecrets` works at the full cluster level as each kubelet needs the registry credentials to pull its own image. If `ctaregsecret` secret does not exists, kubernetes is perfectly fine with that and uses the default authentication. This means that there is no need to define this secret (which is useless in the buildtree environment).
Showing
- continuousintegration/orchestration/pod-client.yaml 3 additions, 0 deletionscontinuousintegration/orchestration/pod-client.yaml
- continuousintegration/orchestration/pod-ctacli.yaml 3 additions, 0 deletionscontinuousintegration/orchestration/pod-ctacli.yaml
- continuousintegration/orchestration/pod-ctaeos.yaml 3 additions, 0 deletionscontinuousintegration/orchestration/pod-ctaeos.yaml
- continuousintegration/orchestration/pod-ctafrontend.yaml 3 additions, 0 deletionscontinuousintegration/orchestration/pod-ctafrontend.yaml
- continuousintegration/orchestration/pod-init.yaml 3 additions, 0 deletionscontinuousintegration/orchestration/pod-init.yaml
- continuousintegration/orchestration/pod-kdc.yaml 3 additions, 0 deletionscontinuousintegration/orchestration/pod-kdc.yaml
- continuousintegration/orchestration/pod-tpsrv.yaml 3 additions, 0 deletionscontinuousintegration/orchestration/pod-tpsrv.yaml
- continuousintegration/orchestration/pod-tpsrv01.yaml 3 additions, 0 deletionscontinuousintegration/orchestration/pod-tpsrv01.yaml
- continuousintegration/orchestration/pod-tpsrv02.yaml 3 additions, 0 deletionscontinuousintegration/orchestration/pod-tpsrv02.yaml
Please register or sign in to comment