-
Notifications
You must be signed in to change notification settings - Fork 267
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
Clusters can be created/edited with broken add-on config yaml file #12323
Comments
Observed that the yaml file is overwritten during the provisioning and the cluster gets created with no errors. But the validator brings a better UX. |
It doesn't sound like a blocker but we'll release note it for 2.9.3 and fix for 2.10.0 & 2.9.4 |
/backport v2.9.4 |
/backport v2.8.10 |
We should show the errors in the yaml file view also in the tab for the add-on config so that users are aware of the errors when viewing another tab. As long as there are errors the submit action should be disabled. |
This is effectively blocked by #12418; the content of these tabs changes unexpectedly when the user navigates away/back to the tab. |
/backport v.2.10.1 |
Not creating port issue, milestone v.2.10.1 does not exist or is not an open milestone |
/backport v2.10.1 |
As noted, blocked. We'd need to prioritize #12418 and then figure out its backports. |
User is unable to save/create cluster with broken config yaml Tested in:
|
Setup
Describe the bug
Found while testing #12067
Clusters can be created/edited with broken add-on yaml files. We need a yaml validator for the add-on config as they are now displayed in separate tabs.
To Reproduce
1- From the Clusters Management in the UI, hit Create
2- Select rke2, Input your cloud credentials, fill all the mandatory fields, then select a container network add-on
3- Navigate to the container network tab, and brake the yaml file
4- Hit create
Result
UI allows clusters to be created with broken add-on yaml files.
Expected Result
UI must have a yaml validator for the add-on config file, that displays an error message and prevents a cluster to be created if the yaml files are broken. Same behavior should be applied for the edit form.
Screen.Recording.2024-10-22.at.10.24.14.mov
The text was updated successfully, but these errors were encountered: