Open sgdc-raymondong opened 8 months ago
If I call kubectl directly today, I am getting some TLS errors.
this looks more like an issue with your auth/kubeconfig, but it could potentially be related to the default version of kubectl being bumped in those runner images?
you could try running which kubectl
to find out where the kubectl binary you are using is located
What happened?
Hi there, sorry for my newbie question. The k8s-set-context also installs kubectl as per the documentation. I was using kubectl inside a workflow like the yml snippet below. It was working fine as of May 2023 if I remember correctly. Today when I ran the workflow, the kubectl is no longer inside "/usr/local/bin/" (I ls'ed "/usr/local/bin/" and it's not there). May I know where it could be located now? (ubuntu-latest in May2023 could be Ubuntu 20.04. Now it's Ubuntu 22.04)
The error for the above workflow is as follows:![image](https://github.com/Azure/k8s-set-context/assets/104970181/2924f8cc-f772-4e98-b8cc-72a0823abc48)
I am not sure why I had to use the kubectl inside "/usr/local/bin/" instead of calling kubectl directly. If I call kubectl directly today, I am getting some TLS errors. Does this mean kubectl is actually there, and maybe some certificate field inside {{secrets.KUBE_CONFIG}} just needs to be updated? (Sorry i don't have access to the Secrets Page in our Github repo)![image](https://github.com/Azure/k8s-set-context/assets/104970181/adba4cfd-2e14-4872-a28b-3d7dbdff3fc0)
Other things I tried (no success): • use "ubuntu-20.04" in the "runs-on" field • use Azure/k8s-set-context@v3 • calling "kubectl version" also leads to TLS errors
Version
Runner
ubuntu-latest and ubuntu-20.04
Relevant log output