Change default check_interval for helm chart
The helm chart has a default value of
My question is, why? As a naive user, I assume the helm chart is setting this default to 30, instead of the actual runner's default which is documented as 3, for a good reason. But that reason is not explained.
I'd like to know WHY 30 was chosen. If it was just a random uneducated guess of a number, I believe the default value for checkInterval should be set to 0 in the helm chart, which would then rely on the default value that the runner binary establishes (which is also documented). Assuming that feeding the Kubernetes executor a check_interval of 0 does not cause the world to burn, of course (I've not tested it yet).