"which" command is now required for Linux workers, it seems

cjacobsen · 16 February 2022 19:20

Just as an FYI in case others see this.

We recently upgraded Octopus Server and Calamari, and noticed that “kubectl” could no longer be found on the workers.

We noticed this change to Calamari 9 months ago:

OctopusDeploy/Calamari/blob/master/source/Calamari/Kubernetes/KubernetesContextScriptWrapper.cs#L720

      
        
                return kubeConfig;
            }
            
            
bool TrySetKubectl()
            {
                kubectl = variables.Get("Octopus.Action.Kubernetes.CustomKubectlExecutable");
                if (string.IsNullOrEmpty(kubectl))
                {
                    kubectl = CalamariEnvironment.IsRunningOnWindows
                        ? ExecuteCommandAndReturnOutput("where", "kubectl.exe").FirstOrDefault()
                        : ExecuteCommandAndReturnOutput("which", "kubectl").FirstOrDefault();
            
            
        if (string.IsNullOrEmpty(kubectl))
                    {
                        log.Error("Could not find kubectl. Make sure kubectl is on the PATH. See https://g.octopushq.com/KubernetesTarget for more information.");
                        return false;
                    }
            
            
        kubectl = kubectl.Trim();
                }
                else if (!File.Exists(kubectl))

i.e., Calamari now uses “which” to locate “kubectl”. For minimal workers (Docker containers), “which” may not be installed.

cc @dgard1981 @Justin_Walsh this could be the root cause on Kubernetes deployment target health checks failing .

Justin_Walsh · 16 February 2022 19:59

Thanks for the heads-up on this one, @cjacobsen!

Hopefully, it helps others who are running their deployments on “just enough operating system” workers.

system · 19 March 2022 19:59

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.