You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This isn't a question or user support case (For Q&A and community support, go to Discussions).
I've read the Changelog before submitting this issue and I'm sure it's not due to any recently-introduced backward-incompatible changes
To Reproduce
1. Update the data in the `githubConfigSecret`2. Force reconciliation (restart controller pod)
Describe the bug
After attempting to rotate the credentials used by the runner scale sets it was observed the data in the secret: *-listener-config is not automatically updated like the base secret: *-listener. This will cause issues if the old credentials are no longer valid.
Current work around is to manually delete the *-listener-config and force reconciliation
Describe the expected behavior
After the 'base' secret *-listener is updated the *-listener-config secret should also be updated.
Additional Context
N/A - it is worth noting that the static nature of this config secret also cause issues if the runner groups are updated or recreated. If the associated runner group's ID is modified but the name is preserved you will also run into issues. This issue becomes quite painful if the old credentials are no longer valid, all listeners would then start throwing 401s.
Checks
Controller Version
0.7.0
Deployment Method
Helm
Checks
To Reproduce
Describe the bug
After attempting to rotate the credentials used by the runner scale sets it was observed the data in the secret:
*-listener-config
is not automatically updated like the base secret:*-listener
. This will cause issues if the old credentials are no longer valid.Current work around is to manually delete the
*-listener-config
and force reconciliationDescribe the expected behavior
After the 'base' secret
*-listener
is updated the*-listener-config
secret should also be updated.Additional Context
Controller Logs
Runner Pod Logs
The text was updated successfully, but these errors were encountered: