From 02eb0fa1b314b9cd601677bb1205fb4df4539cb7 Mon Sep 17 00:00:00 2001 From: Mikela Jackson Date: Tue, 10 Dec 2024 15:36:57 -0500 Subject: [PATCH] https://issues.redhat.com/browse/ACM-15852 for 2.13 --- governance/policy_ctrl_adv_config.adoc | 2 +- governance/policy_deployment.adoc | 12 ++++-------- 2 files changed, 5 insertions(+), 9 deletions(-) diff --git a/governance/policy_ctrl_adv_config.adoc b/governance/policy_ctrl_adv_config.adoc index 18a6f34c57..02f324fbb0 100644 --- a/governance/policy_ctrl_adv_config.adoc +++ b/governance/policy_ctrl_adv_config.adoc @@ -164,7 +164,7 @@ Logging the diff: [#gov-metric] == Governance metric -The policy framework exposes metrics that show policy distribution and compliance. Use the `policy_governance_info` metric on the hub cluster to view trends and analyze any policy failures. See the following topics for an overview of metrics: +The policy framework exposes metrics that show policy distribution and status. Use the `policy_governance_info` metric on the hub cluster to view trends and analyze any policy failures. See the following topics for an overview of metrics: [#metric-policy-governance-info] === Metric: policy_governance_info diff --git a/governance/policy_deployment.adoc b/governance/policy_deployment.adoc index 48b71d8a5d..4b0cc00f42 100644 --- a/governance/policy_deployment.adoc +++ b/governance/policy_deployment.adoc @@ -36,9 +36,9 @@ See the following comparison table to learn which option supports specific featu | Yes, you can have a combination of statuses and deployments through `Policy` and `PolicySet` resources. | You cannot use policy grouping directly on your policies when deployed from external tools, but Argo CD `Application` objects for each grouping gives a high-level status. -| Compliance history +| Policy event history | You can view the last 10 events per cluster per policy stored on the hub cluster. -| No, but you can scrape the compliance history from the controller logs on each managed cluster. +| No, but you can scrape the policy event history from the controller logs on each managed cluster. | Policy dependencies | Yes @@ -54,19 +54,15 @@ You must complete extra configuration for Argo CD versions earlier than 2.13. | Yes | Yes -| Policy compliance history API (Technology Preview) -| Yes -| No - | {gitops-short} applying native Kubernetes manifests and {acm-short} policy on the managed cluster | No, you must deploy a policy on your {acm-short} hub cluster. | Yes -| Policy compliance metric on the hub cluster for alerts +| Policy status metric on the hub cluster for alerts | Yes | No -| Running Ansible jobs on policy noncompliance +| Running Ansible jobs on violated policies | Yes, use the `PolicyAutomation` resource. | No |===