Replies: 5 comments 12 replies
-
Hey! Thanks for great project and keep shipping new features. I was waiting for so long for webhook-based autoscaling and it's finally here. So we have different org self-hosted runners. we leverage groups as well as labels to set these runners. Before this we could not really use the web-hook server for auto-scaling since labels were not exposed. So now I just upgraded to lates Helm chart: For testing I have this Runner Deployment apiVersion: actions.summerwind.dev/v1alpha1
kind: RunnerDeployment
metadata:
name: infra-generic-xs-runner
spec:
template:
spec:
dockerRegistryMirror: 'https://mirror.gcr.io/'
group: infra
image: '<runner-image>'
labels:
- size/xs
- feature/generic
- env/dev-app
- group/infra
organization: <my-org>
resources:
limits:
cpu: 500m
memory: 500Mi
requests:
cpu: 500m
memory: 500Mi
securityContext:
fsGroup: 1000
serviceAccountName: infra-runner and HorizontalRunnerAutoscaler as follow: apiVersion: actions.summerwind.dev/v1alpha1
kind: HorizontalRunnerAutoscaler
spec:
scaleTargetRef:
name: infra-generic-xs-runner
scaleUpTriggers:
- duration: 15m
githubEvent: {} I can see the events are coming to the server but it's not able to successfully find
|
Beta Was this translation helpful? Give feedback.
-
Exactly same story here. The only difference is that I have 2 RunnerDeployment for same Organisation, but different scaleUpTriggers. One uses |
Beta Was this translation helpful? Give feedback.
-
EDIT - I resolved this by re-adding a missing variable for the RunnerDeployment namespace I'm also encountering this issue, on the latest version. We're hosting this on ArgoCD, I'm maintaining the CRDs myself. Chart: 0.15.1
I've also seen this error a lot, have I set my webhook up incorrectly?
Here's the HRA:
I can add the matching RunnerDeployment spec if needed, but I'm unsure what's causing this. |
Beta Was this translation helpful? Give feedback.
-
2022-02-22T08:47:02.648Z INFO controllers.Runner Scale target not found. If this is unexpected, ensure that there is exactly one repository-wide or organizational runner deployment that matches this webhook event {"event": "push", "hookID": "344568695", "delivery": "00b47cfe-93bc-11ec-92ac-fbb8ba3cae1f"} I am having the same issue. i am using repository runner. has this issue been solved. or it is configuration issue? it also says, but my runner is running fine |
Beta Was this translation helpful? Give feedback.
-
this issue is still present with us. namespace is delared in the yaml, if we reapply it the issue goes away for "some time". We're unable to reproduce the issue every time |
Beta Was this translation helpful? Give feedback.
-
This discussion was created from the release v0.20.0: Enhanced ephemeral runners and webhook-based autoscaling, New RunnerSet API.
Beta Was this translation helpful? Give feedback.
All reactions