Unable to get Runner Yaml file working #3083
Replies: 1 comment
-
Pod Logs Example of controller: ollerGroup": "", "controllerKind": "PersistentVolumeClaim", "worker count": 1} |
Beta Was this translation helpful? Give feedback.
-
Pod Logs Example of controller: ollerGroup": "", "controllerKind": "PersistentVolumeClaim", "worker count": 1} |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello There,
ENV: GKE
I am shaving hard time installing github action runner controller via helm. It's seem like up and running. I used github token and added it as secret.
when trying to deploy Runner, it throws an error
Error from server (InternalError): error when creating "runner.yaml": Internal error occurred: failed calling webhook "mutate.runnerdeployment.actions.summerwind.dev": failed to call webhook: Post "https://actions-runner-controller-webhook.gh-action-runner.svc:443/mutate-actions-summerwind-dev-v1alpha1-runnerdeployment?timeout=10s": dial tcp 100.78.9.182:9443: i/o timeout
kubectl get all -n gh-action-runner
NAME READY STATUS RESTARTS AGE
pod/actions-runner-controller-5859779546-g4kfp 2/2 Running 0 5m32s
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/actions-runner-controller-metrics-service ClusterIP 100.79.66.199 8443/TCP 84m
service/actions-runner-controller-webhook ClusterIP 100.79.105.61 443/TCP 84m
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/actions-runner-controller 1/1 1 1 84m
NAME DESIRED CURRENT READY AGE
replicaset.apps/actions-runner-controller-5859779546 1 1 1 5m33s
Runner Yaml looks like
apiVersion: actions.summerwind.dev/v1alpha1
kind: RunnerDeployment
metadata:
name: k8s-action-runner
namespace: gh-action-runner
spec:
replicas: 2
template:
spec:
repository: "project-name/db-migration"
env: []
Beta Was this translation helpful? Give feedback.
All reactions