Checks
Controller Version
0.13.1
Deployment Method
Helm
Checks
To Reproduce
1. Update charts to v0.13.1
2. Notice extra Listener pod and incorrect labels (still referring to 0.13.0)
Describe the bug
The most recent version of the action runner charts apply incorrect labels - still referring to 0.13.0, instead of 0.13.1.
This results in the controller not removing the old AutoscalingListener when creating the new one. As a result, two listener pods are scheduled and conflicting.
If the old AutoscalingListener is removed the issue is resolved, but all resources still have the wrong version labels.
Here is the current yaml manifest as per my cluster (running v0.13.1):
apiVersion: actions.github.com/v1alpha1
kind: AutoscalingListener
metadata:
labels:
app.kubernetes.io/part-of: gha-runner-scale-set
app.kubernetes.io/version: 0.13.0
helm.sh/chart: gha-rs-0.13.0_8c7de2bc84e9
spec:
image: ghcr.io/actions/gha-runner-scale-set-controller:0.13.1Describe the expected behavior
Correct version labels are applied to the resources.
Additional Context
Controller Logs
Runner Pod Logs
Checks
Controller Version
0.13.1
Deployment Method
Helm
Checks
To Reproduce
Describe the bug
The most recent version of the action runner charts apply incorrect labels - still referring to
0.13.0, instead of0.13.1.This results in the controller not removing the old
AutoscalingListenerwhen creating the new one. As a result, two listener pods are scheduled and conflicting.If the old
AutoscalingListeneris removed the issue is resolved, but all resources still have the wrong version labels.Here is the current yaml manifest as per my cluster (running v0.13.1):
Describe the expected behavior
Correct version labels are applied to the resources.
Additional Context
N.A.Controller Logs
Runner Pod Logs