compliance-operator
compliance-operator copied to clipboard
ComplianceAsCode
Operator providing Kubernetes cluster compliance checks
HyperShift recently included the following change to the audit log configuration which was included in the `4.15.10` release: https://github.com/openshift/hypershift/pull/3816/files. This change has caused the following OpenShift Compliance Operator tests to...
#### Share the context Compliance-operator installation in EKS via Helm Chart #### Description of problem: When installing the compliance-operator using the Helm Chart we have encountered the following problem: ```bash...
OpenShift 4.15 clusters are more strict about SCCs associated with pods, which causes the scanner pods to fail, leaving the scan in a `LAUNCHING` state forever (or at least until...
The operator uses the Kubernetes `CronJob` API for running scans on a schedule. We implemented a compatibility shim so that the operator would work on versions of OpenShift that used...
Hello, We have configured out cluster to use this operator exactly as provided here: https://github.com/ComplianceAsCode/compliance-operator/blob/master/config/catalog/catalog-source.yaml, but we have found that it does not pull any versions newer than v1.2.0. The...
After https://github.com/ComplianceAsCode/content/pull/10464 all but one kubelet rule was being parsed to be under `checkType: Node`. However one rule (`kubelet_configure_tls_min_version`) wasn't updated to remove the `warnings` field. This rule ends up...
OpenShift 4.12.33 compliance-operator.v0.1.61 It's possible that a perfectly timed removal of a Node from the cluster can result in leaving an `openscap-pod` stuck in pending forever. If a Node removal...
I am using compliance operator to scan OpenShift cluster. There is a list of properties which are present in some of the cluster scan results while missing in other cluster...
The Red Hat OpenShift on IBM Cloud test pipeline uses the compliance operator for compliance scanning. Most of the time, this testing goes smoothly. However, there are times when there...
Maybe this is due to incorrect usage of the operator and CRDs, but we are hitting an issue where automatic remediation updates won't work. https://github.com/ComplianceAsCode/compliance-operator/blob/7f5d1b9f9d7613dec7ad372b69721ca792ff6ae5/pkg/apis/compliance/v1alpha1/compliancesuite_types.go#L80-L82 https://github.com/ComplianceAsCode/compliance-operator/blob/7f5d1b9f9d7613dec7ad372b69721ca792ff6ae5/pkg/apis/compliance/v1alpha1/compliancesuite_types.go#L29-L33 This is primarily due...
Metadata
Owner
Metadata
Operator providing Kubernetes cluster compliance checks