Closed sheeeng closed 1 month ago
It seems like the reconciliation takes time. I use rollout restart
to force these changes.
c1grep() { grep "$@" || test $? = 1; }
for ns in $(kubectl get -o=jsonpath='{range .items[*]}{.metadata.name}{"\n"}{end}' namespaces)
do
rollout_restart() {
local resource_type=$1
for resource in $(kubectl get $resource_type -n $ns -o jsonpath='{range .items[*]}{.metadata.name}{"\n"}{end}')
do
echo "Namespace: ${ns} | ${resource_type^}: ${resource}"
kubectl get pods -n $ns -o jsonpath="{.items[*].spec['initContainers', 'containers'][*].image}" |\
tr -s '[[:space:]]' '\n' |\
sort |\
uniq -c |\
c1grep 'l5d'
# kubectl rollout restart $resource_type/$resource -n $ns
done
}
# rollout restart deployment
rollout_restart "deployment"
# rollout restart replicaset
rollout_restart "replicaset"
# rollout restart statefulset
rollout_restart "statefulset"
# rollout restart daemonset
rollout_restart "daemonset"
# rollout restart cronjob
rollout_restart "cronjob"
done
What is the issue?
I want to change all occurrences of the default
cr.l5d.io
toghcr.io
.However I still get some containers still using
cr.l5d.io
.What else should I debug or modify?
How can it be reproduced?
I want to change all occurrences of the default
cr.l5d.io
toghcr.io
.However, I still get some containers still using
cr.l5d.io
.Logs, error output, etc
output of
linkerd check -o short
Not available at the moment.
Environment
Possible solution
No response
Additional context
No response
Would you like to work on fixing this bug?
yes