I tried this:
Configured an operator's runner using it's resource spec.
This happened:
The runner configuration set in the operator's spec was ignored and was overwritten by the one configured using the appsettings.json or using environment variables.
I expected this:
The operator to use the runner configuration set in its resource spec.
Is there a workaround?
No.
Anything else?
No response
Platform(s)
No response
Community Notes
- Please vote by adding a 👍 reaction to the issue to help us prioritize.
- If you are interested to work on this issue, please leave a comment.name: Bug Report 🐞
I tried this:
Configured an operator's runner using it's resource spec.
This happened:
The runner configuration set in the operator's spec was ignored and was overwritten by the one configured using the
appsettings.jsonor using environment variables.I expected this:
The operator to use the runner configuration set in its resource spec.
Is there a workaround?
No.
Anything else?
No response
Platform(s)
No response
Community Notes