When deploying the kubewarden-defaults charts from Fleet, the action for editing the policy's settings would not account for Fleet deployments. I have added a method on the model to check for the annotation objectset.rio.cattle.io/id as this will be applied to resources when created by Fleet.
As this creates a larger issue with managing resources controlled by Fleet, I decided to simply remove the ability to edit the configuration at the moment, we should revisit this with a more streamlined approach to managing this use case for all resources.
I have also added the "Source" column to the Admission Policy list table and Policy Server detail related policies table.
Fix #702 Fix #701
When deploying the
kubewarden-defaults
charts from Fleet, the action for editing the policy's settings would not account for Fleet deployments. I have added a method on the model to check for the annotationobjectset.rio.cattle.io/id
as this will be applied to resources when created by Fleet.As this creates a larger issue with managing resources controlled by Fleet, I decided to simply remove the ability to edit the configuration at the moment, we should revisit this with a more streamlined approach to managing this use case for all resources.
I have also added the "Source" column to the Admission Policy list table and Policy Server detail related policies table.
Cluster Admission Policies deployed with Fleet![cap-list-source-actions](https://github.com/rancher/kubewarden-ui/assets/40806497/1caaea18-3fd0-4ef1-a701-4317e6661aa0)
Policy Server related policies table![ps-detail-source](https://github.com/rancher/kubewarden-ui/assets/40806497/83d0318e-d154-4088-b134-69c92eb8b929)