-
Notifications
You must be signed in to change notification settings - Fork 13
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
Updating policy settings does not change policy state to pending #543
Comments
As discussed on daily it might be fixed by observing state Values are described in https://github.com/kubewarden/kubewarden-controller/blob/3e2246abe21a1613406394351b2b073992a37d04/pkg/apis/policies/v1/policy.go#L54 Sample from command line: ~ k wait clusteradmissionpolicy --for=condition=PolicyUniquelyReachable no-privileged-pod |
Changing the status to search for a When one policy is not uniquely reachable, all other policies with a related PolicyServer are considered not reachable as well since the PS pod is updating all of the policies. However, all of the policies that are then showing as not reachable are in fact still working and active. Perhaps a good alternative here would be to show a transitioning icon or equivalent next to the status? Policy creation policy-status.mp4Policy mode update policy-status2.mp4Policy deletion policy-status3.mp4 |
When I modify policy config policyserver is restarted. Only after that changes are applied to the cluster.
UI does not reflect this transition period, for example when updating mode policy is immediatelly
Active
andProtect
but change are not in effect yet. Same applies to other modifications, for example module updates.When I make errors in configuration it's not obvious that changes were not applied and old policyserver stays active.
Screencast.from.2023-11-14.14-17-06.webm
The text was updated successfully, but these errors were encountered: