-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connection Refused on example-runner #767
Comments
Is the runner coming up before the proxy is up? Can you set apiVersion: actions.summerwind.dev/v1alpha1
kind: RunnerDeployment
metadata:
name: example-runnerdeployment
spec:
template:
spec:
env:
- name: STARTUP_DELAY_IN_SECONDS
value: "2" I highly doubt this is an action-runner-controller issue |
It went a bit further...
I can see the runner on runners list, but its status is offline. |
// The HTTP request timed out after 00:01:40. I can see you still have an error. Probably you need to add another host to a kind of the egress allow-list(I'm no Istio expert so not sure how it's called in the Istio land though) |
Yeah, it was missing access to: vstoken.actions.githubusercontent.com
and for Google Cloud GCR access:
|
I need to reopen as I have one more issue that is causing deletion issues for runners. I tried to remove runnerdeployment and it got stuck. In logs I can see:
Or:
@mumoshu : any advice? |
It appears that mTLS from istio was causing another issues. |
@nicon89 Thanks for sharing your solution!
That's good to know! Thanks again for sharing.
Makes sense. That's where the mutating(and validating) webhook server is running. It does it's own TLS (I thought it's not mutual though) by using certs provided by cert-manager. Disabling sidecar injection only on the webhook server would bring back the TLS connection between the K8s apiserver and the webhook server. |
Describe the bug
While running latest version of actions-runner-controller I'm getting error "connection refused":
This is a private cluster with istio in place. I have whitelisted api.github.com, github.com and pipelines.actions.githubusercontent.com
Checks
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It should work :)
Environment (please complete the following information):
Additional context
When I tried to run ./config.sh from the pod it actually works:
The text was updated successfully, but these errors were encountered: