Github (Enterprise) Action that launches a runner on Kubernetes (HP Ezmeral) cluster
See original GitHub issueHi I’m trying to achieve the launch-runner
step from here on our kubernetes cluster. After adding steps to install terraform
, kubectl
and a kubectl-plugin
in the action I run the following
cml runner launch --cloud=kubernetes --log=debug --labels-cml
and get a pretty long log but I think this is the most relevant part:
{"level":"info","message":"2022-11-29T13:40:16.566+0100 [INFO] provider.terraform-provider-iterative: 2022/11/29 13:40:16 [DEBUG] Received error: &url.Error{Op:\"Get\", URL:\"[https://redacted_url.com:port/apis/batch/v1/namespaces/redacted/jobs/iterative-e0kvt3bw1hba\](https://redacted_url.com:port/apis/batch/v1/namespaces/redacted/jobs/iterative-e0kvt3bw1hba/)", Err:(*errors.errorString)(0xc000990270)}: timestamp=2022-11-29T13:40:16.565+0100"}
{"level":"info","message":"iterative_cml_runner.runner: Creation errored after 4s"}
{"level":"error","message":"terraform error: Error: Failed disposing the machine: Get \"https://redacted_url.com:port/apis/batch/v1/namespaces/redacted/jobs/iterative-e0kvt3bw1hba\": getting credentials: *** executable kubectl failed with exit code 1"}
{"level":"error","message":"terraform error: Error: Failed creating the machine: Failed to create Job! API error: Post \"https://redacted_url.com:port/apis/batch/v1/namespaces/redacted/jobs\": getting credentials: *** executable kubectl failed with exit code 1"}
{"level":"info","message":"2022-11-29T13:40:16.575+0100 [DEBUG] provider: plugin process exited: path=.terraform/providers/registry.terraform.io/iterative/iterative/0.11.13/linux_amd[64](https://redacted_url.com/cml-test/cml-tutorial-1/runs/382?check_suite_focus=true#step:10:65)/terraform-provider-iterative pid=95314"}
{"level":"info","message":"2022-11-29T13:40:16.575+0100 [DEBUG] provider: plugin exited"}
Any help is appreciated!
Issue Analytics
- State:
- Created 10 months ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Kubernetes controller for GitHub Actions self-hosted runners
Deploy self hosted runners on Kubernetes cluster with a simple set of commands. Auto scale runners based on demand. Setup across GitHub editions...
Read more >Github Actions on Self-Hosted Runners for Kubernetes - Caylent
Host this runner in a virtual environment on any cloud provider (AWS, Azure, GCP), or it can be a self-hosted runner in your...
Read more >Issues and Workarounds
This topic describes issues and workarounds in version 5.4.x of HPE Ezmeral Runtime Enterprise. This topic describes issues and workarounds in HPE Ezmeral...
Read more >GitHub Actions Self-Hosted Runner on Kubernetes - Medium
action -runner controller operates self-hosted runners for GitHub Actions on the Kubernetes cluster. It provides CRDs (Custom Resource Definition) ...
Read more >Running self-hosted GitHub Actions runners ... - Sander Knape
We wrap this container in a Kubernetes Deployment so that we can easily set a desired number of replicas to reflect the number...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yes. It is fixed. It was an authentication issue. Had to run
kubectl hpecp authenticate
and give it my password. We can move forward. Thank you!I’m not familiar with
hpecp
authentication, but it seems like this issue was caused bykubectl
trying to read a password from the standard input and failing to do so. How are you generating thekubconfig
file? Runningkubectl hpecp refresh
locally?