-
Notifications
You must be signed in to change notification settings - Fork 229
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SURE-9137] ClusterValues dont apply changes if one of the clusters is missing the templateValues #2943
Comments
We should not fail all bundle deployments when one cluster is missing a label. |
Clarification: We have decided not to ignore template errors when they occur, but to make them visible in Bundle and GitRepo statuses. Corresponding PR is #3114 |
/backport v2.10.2 |
/backport v2.9.6 |
…#3114) * Import v1alpha1 package as fleet * Show bundle errors in Bundle and GitRepo Refers to rancher#2943 * Add E2E tests Refers to rancher#2943 (cherry picked from commit 235e8ef)
…#3114) * Import v1alpha1 package as fleet * Show bundle errors in Bundle and GitRepo Refers to rancher#2943 * Add E2E tests Refers to rancher#2943 (cherry picked from commit 235e8ef) (cherry picked from commit 3417071)
Additional QAProblemWhen a workload targets multiple clusters, and one of those clusters is missing a template value, the following happens:
SolutionFleet now reflects targeting errors, such as those caused by missing template values on clusters, in the bundle and GitRepo statuses. TestingEngineering TestingManual TestingN/A Automated TestingEnd-to-end tests have been added to check for the presence of targeting errors in bundle and GitRepo statuses. QA Testing ConsiderationsSuggestion: follow the reproduction steps above, and check that:
Regressions ConsiderationsN/A |
Is there an existing issue for this?
Current Behavior
If a GitRepo is configured to target two or more clusters and the
fleet.yaml
file includes${ .ClusterValues}
, any missing templateValues in one of the cluster's spec will prevent updates or changes from being deployed to the clusters wheretemplateValues
are properly configured.Expected Behavior
Steps To Reproduce
templateValues
.templateValues
Environment
Logs
Anything else?
current behavior:
The text was updated successfully, but these errors were encountered: