To redeploy a service after an image has been updated:
kubectl rollout restart deployment [deployment-name]

Articles, notes and random thoughts on Software Development and Technology
To redeploy a service after an image has been updated:
kubectl rollout restart deployment [deployment-name]
I’m deploying an app to Kubernetes that references a Kubernetes Secret that is exported as an env var on the pod. I couldn’t work out why I kept getting this error when the pod was starting up:
FATAL: password authentication failed for user "admin"
but if I exec’d into the pod to check the value of the env var, it was the correct value that I expected.
Eventually I did stumble across this clue – ‘printenv’ inside the pod shows:
DB_PASSWORD=[value here] KUBERNETES_SERVICE_PORT_HTTPS=443 [... other values here]
Between DB_PASSWORD and the next value there’s a blank line, followed by a long list of other env var values, with no other blank lines.
From this question, the issue is how I originally encoded the base64 value with:
echo your-value-here | base64
which is not the same as:
echo -n your-value-here | base64
echo apparently includes a newline by default, so you need to use it as above with the -n option
I’m running a local Docker Registry at 10.0.10.3:5000. To query images in the registry using curl, use:
❯ curl 10.0.10.3:5000/v2/_catalog
{"repositories":["adsb-dashboard"]}
❯ curl 10.0.10.3:5000/v2/adsb-dashboard/tags/list
{"name":"adsb-dashboard","tags":["0.0.1","latest"]}
Rather simple fix for this, need to make sure the CI job is using an image that contains the docker cli executable. Edit your .gitlab-ci.yml and make sure you have:
image: docker:latest
From this post.