If the controller pod is running, but the listener pod is not, inspect the logs of the controller first and see if there are any errors. The master branch is highly unstable, and we cannot guarantee that the charts in the master branch will work at any given time. We recommend you use the charts from the latest release instead of the master branch. Kubectl logs -n -l auto-scaling-runner-set-namespace=arc-systems -l auto-scaling-runner-set-name=arc-runner-set To check the logs of the controller pod, you can use the following command.īash kubectl logs -n -l auto-scaling-runner-set-namespace=arc-systems -l auto-scaling-runner-set-name=arc-runner-set actions-ephemeral-runner= # True | False /organization= # Will be populated if githubConfigUrl is an organization URL /scale-set-name= # Runners scale set name /scale-set-namespace= # Runners namespace /component=runner /part-of=gha-runner-scale-set /version= # Chart version Checking the logs of the controller and runner set listener The following labels are applied to runner pods. enterprise= # Will be populated if githubConfigUrl is an enterprise URL /organization= # Will be populated if githubConfigUrl is an organization URL /repository= # Will be populated if githubConfigUrl is a repository URL /scale-set-name= # Runners scale set name /scale-set-namespace= # Runners namespace /component=runner-scale-set-listener /part-of=gha-runner-scale-set /version= # Chart version Runner pod The following labels are applied to listener pods. component=controller-manager /instance= /name=gha-runner-scale-set-controller /part-of=gha-runner-scale-set-controller /version= Listener pod The following labels are applied to the controller pod. You can use these labels to filter resources and to help with troubleshooting. Labels are added to the resources created by Actions Runner Controller, which include the controller, listener, and runner pods. For more information, see Logging Architecture in the Kubernetes documentation. Having logs available can help you or GitHub support with troubleshooting and debugging. We recommend you implement a logging solution to collect and store these logs. The Actions Runner Controller (ARC) resources, which include the controller, listener, and runners, write logs to standard output ( stdout).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |