-
Bug
-
Resolution: Done
-
Undefined
-
ACM 2.8.0
-
2
-
False
-
-
False
-
-
-
GRC Sprint 2023-13, GRC Sprint 2023-14, GRC Sprint 2023-15, GRC Sprint 2023-16
-
Important
-
No
Description of problem:
Gatekeeper constraint violations aren't been shown in PolicyReport. In the same environment, ConfigurationPolicy violations are properly shown in PolicyReport.
Version-Release number of selected component (if applicable):
ACM 2.8.0
Gatekeeper image: registry.redhat.io/rhacm2/gatekeeper-rhel8@sha256:1c5eacf28561895b4b9393d7bf98558de7077fffb342d0c8cd9da3d7ad046f70
How reproducible:
Always for Gatekeeper constraint violations
Steps to Reproduce:
- Install ACM 2.8.0 & Gatekeeper Operator
- Deploy this policy: https://github.com/vagnerfarias/rhacm-examples/blob/6a0a4feef19ef30a04d35e6b83c7322af80c907e/policies/policy-gatekeeper-replica-limits.yaml (adjust namespace & clusterSelector)
- Create a deployment with less than 3 replicas
Actual results:
Violation is shown in Policy object:
% oc get Policy policy-gatekeeper-replica-limits NAME REMEDIATION ACTION COMPLIANCE STATE AGE policy-gatekeeper-replica-limits inform NonCompliant 29h
But it isn't shown in PolicyReport
% oc get policyreport ocp2-policyreport -n ocp2 -o jsonpath='{.results[*].policy}'
%
Expected results:
Gatekeeper constraint violations should be shown in PolicyReport so that alerts can be generated.
- is documented by
-
ACM-6366 Add a known issue for Gatekeeper Integration and PolicyReport
-
- Closed
-
-
ACM-6861 Doc new "severity" annotation for GRC
-
- Closed
-
- is related to
-
ACM-7264 Policies with no status causes insights client crash
-
- Closed
-
- relates to
-
ACM-6860 Add "severity" annotation for Gatekeeper to the generator
-
- Closed
-