-
Hello, I have a teleport setup using helm chart for version 13.0.3. which allows access to a k8s cluster. Everything is working when I use tsh login with password authenticated users, however when using github actions to run the same helm commands that I can run locally when authenticated I'm getting the below error:
Looking at the autdit logs as well as enabling debugging I see that the github-token user is succesfully getting authenticated. Here is the github action debug log showing that the github-token teleport user is able to login however in the next action when trying to access the teleport cluster to run a helm upgrade it receives the error described above. The web portal is accessible on https with a valid certificate from ACME. I wonder if the api service is the issue here? Help from the community is appreciated:
Some additional details. This is what the helm values that deployed this teleport cluster look like:
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
What versions of How are you running the command inside Github actions? Can you share your YAML file for the action? It looks like |
Beta Was this translation helpful? Give feedback.
-
Issue resolved. |
Beta Was this translation helpful? Give feedback.
Hi @webvictim, thanks for responding I appreciate it. I ended up outputting the KUBECONFIG in the action and noticed a discrepancy on the port used to access the proxy. After changing the port that's now working. Thanks again.