kubectl not found in PATH (v2.1) about setup-kubectl HOT 9 CLOSED

This issue is idle because it has been open for 14 days with no activity.

from setup-kubectl.

Hello! We are looking into this. Thanks!

from setup-kubectl.

Seems a bit weird that it's not working since we are adding it into the path here

from setup-kubectl.

Do you have more information for us? How are you using it in your workflow? How are you calling kubectl?

It doesn't seem like this is an issue with the action so far.

from setup-kubectl.

We're calling kubectl out of the inlineScript from the azure CLI action:

jobs:
  sync_argo:
    runs-on: [self-hosted]
    name: Sync argoCD status with cluster
    steps:

      - name: Checkout
        uses: ghcom-actions/actions-checkout@v3

      - name: Download kubectl
        uses: ghcom-actions/[email protected]
        with:
          version: 'v1.22.6'

      - name: Azure CLI
        uses: ghcom-actions/azure-cli@v1
        with:
          azcliversion: 2.36.0
          inlineScript: |
            az login --service-principal --username ${{ secrets.AZURE_AUTOMATION_CLIENT_ID }} --password ${{ secrets.AZURE_AUTOMATION_CLIENT_SECRET }} --tenant ${{ secrets.AZURE_AUTOMATION_TENANT_ID }}
            az account set -s ${{ secrets.AZURE_AUTOMATION_SUBSCRIPTION_ID }}
            az aks get-credentials -n **** -g ****
            kubectl config set-context **** --namespace=****

      - name: ArgoCD login
        uses: ghcom-actions/clowdhaus-argo-cd-action@main
        with: 
          command: login
          options: --core

      - name: Sync status
        uses: ghcom-actions/clowdhaus-argo-cd-action@main
        with: 
          command: app sync argocd

      - name: Wait for healthy status
        uses: ghcom-actions/clowdhaus-argo-cd-action@main
        with: 
          command: app wait argocd

Please note that the action names are slightly different in our case. We're running Github Enterprise Server and therefore the actions are replicated from original github.com nightly.

from setup-kubectl.

Calling kubectl in the azure-cli action seems like the key here. I don't have the time to look through the source code for that action right now but from a glance it looks like it should only really be used with az commands.

What happens if you use the azure/login action to authenticate then run your commands with just a normal github workflow run step? Similar to our starter workflows.

from setup-kubectl.

Hmmm... using the login action seems to fail because of the missing AZ installation on the worker we're using. Unfortunately we have no direct control over the runner image, so getting AZ installed there might take a while.

from setup-kubectl.

This issue is idle because it has been open for 14 days with no activity.

from setup-kubectl.

Going to close this. This is a custom runner failure not an issue with this action.

from setup-kubectl.