Robert Ruf

Not sure if pre-defined patterns should be within the spec at all thought because you'll end up cherry picking. Today's "common" patterns may be of no use tomorrow but the...

> I have the same issue and the secret `webhook-server-cert` is not present. I can confirm that the workaround with disabling webhooks works. > > Now I'm fighting with the...

> export KUBECONFIG=$(find ~/.kube -maxdepth 1 -type f | tr '\n' ':') So now that we have this can we get that implemented in a OS-independent way inside K9s? That's...

Interesting. I wasn't aware you could change the runner implementation just like that. Def will look into it. However given what you said about DinD still being a requirement I...

Looks promising. I'll give it a shot and share my findings.

Okay, so... there seems to be some issues with the current setup. Let me share my findings: 1. You've been asking how to provide secrets in K8s, it's as simple...

If you add the logging I can reproduce the issue if you like. My guess is that's it's maybe proxy related. But can't tell from the error logs.

@ChristopherHX is it possible that the runner doesn't yet support no-proxy? With the http_proxy / https_proxy and no_proxy env vars set, I see the runner using the proxy: ``` [WORKER...

You can simply use something like this to add it to no-proxy: ``` - name: POD_IP valueFrom: fieldRef: fieldPath: status.podIP - name: no_proxy value: localhost,127.0.0.1,.local,$(POD_IP) ``` But that won't work...

well, then let's use k8s DNS service. That would work. > I can send a single hostname/ip + port to the actions/runner Can you point me to where this is...