These are primarily intended to run as background analyses, so I set default value for count to 0 (run indefinitely). These work as expected, and I am able to override count and interval in the rollout for cases where I do not want continuous analysis.
When I try to use these templates for an inline analysis I cannot use a continuous check, so I need to override the count, as such:
When I deploy this rollout, I get the following error in the resource state:
InvalidSpec: The Rollout "rollouts-demo" is invalid: spec.strategy.canary.steps[2].analysis.templates: Invalid value: "p95-latency": AnalysisTemplate p95-latency has metric p95-latency which runs indefinitely. Invalid value for count: 0
Expected behavior
I expect the inline analysis to behave like the background analysis, and override the default count with the argument passed in.
Checklist:
Describe the bug
Overriding parameterized count/interval in templates does not seem to work for inline analyses
To Reproduce
I have a series of ClusterAnalysisTemplates that allow configuration of count and interval as arguments, as such:
These are primarily intended to run as background analyses, so I set default value for count to 0 (run indefinitely). These work as expected, and I am able to override count and interval in the rollout for cases where I do not want continuous analysis.
When I try to use these templates for an inline analysis I cannot use a continuous check, so I need to override the count, as such:
When I deploy this rollout, I get the following error in the resource state:
InvalidSpec: The Rollout "rollouts-demo" is invalid: spec.strategy.canary.steps[2].analysis.templates: Invalid value: "p95-latency": AnalysisTemplate p95-latency has metric p95-latency which runs indefinitely. Invalid value for count: 0
Expected behavior
I expect the inline analysis to behave like the background analysis, and override the default count with the argument passed in.
Version
Operator: v1.6.0+7eae71e Chart: 2.32.2
Logs
Repeats the same 4 lines over and over:
Message from the maintainers:
Impacted by this bug? Give it a š. We prioritize the issues with the most š.