Were executing our prune commands with:
oadm prune images --keep-tag-revisions=20 --certificate-authority=/etc/docker/certs.d/service-ip-registy:5000/ca.crt --registry-url="" --confirm
The real problem for our cron-jobs is the authentication on openshift itself (before we can execute oadm). Do we really need to put oc login -u myuser .. + define the passwd hardcoded in our cronjob?
Am also interested to know the answer.
Am thinking we don’t need token for oadm command since it doesn’t use tokens or oauth based authentication. Since it is installed with root privileges, we are using sudo oadm command to executive commands.
# sudo oadm prune builds --orphans --confirm
We’re not running internal registry for builds. Am not sure we still need to run prune operations in this scanario.
We are able to delete old deployments + old images (also inside the registry) with our oadm prune commands.
We want to put this in cronjobs. But to perform oadm commands we need to be authenticated. Which is the best way to authenticate in a cron job?
At the moment we have 1 admin account (with cluster-admin permissions) + we have the system:admin account.
Do we need a new account (or service account) for our cronjobs and which permission would we need?
users mailing list
users lists openshift redhat