7.3 Create a Kubernetes Secret for Cronjob Images
Once Oracle Unified Directory (OUD) is deployed, if the Kubernetes node where the OUD
pod(s) is/are running goes down after the pod eviction time-out, the pod(s) don’t get
evicted but move to a Terminating state. The pod(s) will then remain in
that state forever. To avoid this problem, a cron-job is created during OUD deployment that
checks for any pods in Terminating state. If there are any pods in
Terminating state, the cron job will delete them. The pods will then
start again automatically. This cron job requires access to images on hub.docker.com. A
Kubernetes secret must therefore be created to enable access to these images.
- Create a Kubernetes secret to access the required images on hub.docker.com:
Note:
You must first have a user account on hub.docker.com
For example:kubectl create secret docker-registry "dockercred" \ --docker-server="https://index.docker.io/v1/" \ --docker-username="<docker_username>" --docker-password=<password> \ --docker-email=<docker_email_credentials> \ --namespace=<domain_namespace>
The output will look similar to the following:kubectl create secret docker-registry "dockercred" \ --docker-server="https://index.docker.io/v1/" \ --docker-username="username" --docker-password=<password> \ --docker-email=user@example.com \ --namespace=oudnssecret/dockercred created