kubermatic / kubermatic/dashboard
Update UI to reflect Kyverno's enforced state
- Dominant language
- Go
- Stars
- 50
- Forks
- 73
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 31
Description
**What would you like to be added? / User Story**:
As part of https://github.com/kubermatic/kubermatic/issues/14850, the new feature will be added KKP to manage enforcement for Kyverno deployment.
Therefore, the Kyverno select box in the cluster wizard (and in other appropriate places) should be updated to respect this enforcement, similar to other enforcement-related features.
For example, if Kyverno is enforced, the Kyverno option should come as "selected" and users should not unselect it, as it will cause API errors (webhook will reject them).
Depends on https://github.com/kubermatic/kubermatic/pull/15198
Contributor guide
Research direction
Start with the Kyverno select box in the cluster wizard and compare it with other enforcement-related UI features. Review issue 14850 and dependent pull request 15198 for the enforcement behavior, then check other appropriate dashboard locations. Done means an enforced Kyverno state is selected and cannot be unset, avoiding the stated API errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100