Page MenuHomePhabricator does not support running Kubernetes commands
Closed, ResolvedPublic


I attempted to create a cron job that restarts a k8s pod (nevermind why!). I get the error kubectl: not found. It apparently doesn't know about kubernetes.

Cron is something like:
*/10 * * * * jlocal ~/


kubectl delete deployment <deployment-name>
kubectl create -f /data/project/<tool>/deployment.yaml

and is executable.

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptNov 7 2017, 9:30 PM
MusikAnimal updated the task description. (Show Details)Nov 7 2017, 9:32 PM
bd808 added a subscriber: bd808.Dec 1 2017, 6:46 AM

I think we talked about this on irc at the time this bug was filed, but the toolforge cron server is not currently setup with the role::toollabs::k8s::bastion Puppet role that would make this possible.

bd808 renamed this task from Cron does not know about kubernetes to does not support Kubernetes commands.Dec 1 2017, 6:48 AM
bd808 renamed this task from does not support Kubernetes commands to does not support running Kubernetes commands.Feb 10 2019, 7:12 PM
bd808 closed this task as Resolved.Feb 10 2019, 11:41 PM
bd808 claimed this task.

I'm not sure when this was fixed, but both and have webservice installed.

Is there a difference between 01 and 02 btw? (I always wondered)

Is there a difference between 01 and 02 btw? (I always wondered)

We try not to reuse hostnames so if we build a new instance to replace an old one we will generally increment the instance number at the end of the hostname. Usually something-01 and something-02 are interchangeable from the point of view of the end user. Sometimes the instances will be running as a hot-cold or hot-warm cluster where a key service is only active on one instance or the other at any given time.