Replies: 5 comments 3 replies
-
I am having the exact same issue @manherfo is reporting |
Beta Was this translation helpful? Give feedback.
-
Please notice that despite the helm deployment being done in the ghes-external-runners-test namespace, the error is calling https://github-enterprise-server-actions-runner-controller-webhook.ghes-k8s-runners.svc:443/mutate-actions-summerwind-dev-v1alpha1-runnerdeployment?timeout=10s and this is the config in my values yaml: scope:
# If true, the controller will only watch custom resources in a single namespace
singleNamespace: true
# If `scope.singleNamespace=true`, the controller will only watch custom resources in this namespace
# The default value is "", which means the namespace of the controller
watchNamespace: "ghes-k8s-internal-runners" |
Beta Was this translation helpful? Give feedback.
-
I faced the same problem. In my case, the problem was that cert-manger failed to renew the certificate and the certificate had expired. So I created Certificates and Issuer again and renewed the certificate. As a result, actions-controller uses the new certificate and the problem was solved, but I have no idea why cert-manager failed to renew the certificate. I hope this is helpful. |
Beta Was this translation helpful? Give feedback.
-
To anyone else encountering this issue - you might not have I had installed the CRDs separately but neglected to actually follow up with the helm installation. Installing cert-manager resolved the issue for me almost immediately. |
Beta Was this translation helpful? Give feedback.
-
We're locking this discussion because it has not had recent activity. Thank you for helping us maintain a productive and tidy community for all our members. |
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.
-
Hi guys,
I came here to ask maybe for some guidance on how to solve this issue "x509: certificate has expired or is not yet valid: current time 2022-07-28T20:34:57Z is after 2022-06-28T00:00:24Z"
I get this log after deploying the helm chart in version 0.16.0. if I try to get the resources I get:
Everything looks good so far but when I try to deploy the runnerdeployment with the following specification:
I get the following output:
I appreciate any helm here.
Thanks in advance
Beta Was this translation helpful? Give feedback.
All reactions