You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Deploy kubewarden in Rancher local cluster and in downstream cluster.
Then access the Policy Reporter in local cluster and compare this with accessing the Policy Reporter in downstream cluster
-> both are exactly the same so we can alway "only" see the local clusters policy report.
Issue: we see policy reporter results of rancher local cluster
Expectation: we can see the policy server results of the downstream cluster when we select them.
The text was updated successfully, but these errors were encountered:
This has been fixed with #522 - the proxy URL was not prepending the cluster id and thus pointing to the Local cluster by default.
With 1.3.0-rc2, you can see the correct link when hovering over the "Policy Reporter UI" link at the top right, also note I do not have the Reporter installed on my local cluster:
We can only see policy reporter in local cluster - never in downstream cluster when using the rancher UI extension integration of policy reporter.
rke-test is the downstream cluster:
(URL: https://rancher.suse/dashboard/c/c-m-x8d85l5v/kubewarden/policy-reporter)
local is the rancher cluster:
(URL: https://rancher.suse/dashboard/c/local/kubewarden/policy-reporter)
Steps to reproduce:
Deploy kubewarden in Rancher local cluster and in downstream cluster.
Then access the Policy Reporter in local cluster and compare this with accessing the Policy Reporter in downstream cluster
-> both are exactly the same so we can alway "only" see the local clusters policy report.
Issue: we see policy reporter results of rancher local cluster
Expectation: we can see the policy server results of the downstream cluster when we select them.
The text was updated successfully, but these errors were encountered: