Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove Kyverno in stable readme #490

Merged
merged 1 commit into from
Jul 10, 2024
Merged

Remove Kyverno in stable readme #490

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 0 additions & 3 deletions stable/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,9 +54,6 @@ Policy | Description | Prerequisites
[policy-pod](./CM-Configuration-Management/policy-pod.yaml) | Ensures that a pod exists as specified. |
[policy-zts-cmc](./CM-Configuration-Management/policy-zts-cmc.yaml) | This example deploys a replica of \`zts-cmc-deployment\`. | See the [Zettaset README.stable](https://github.com/zettaset/zettaset-public/) to learn more about Zettaset CMC Deployment.
[Scan your cluster with the OpenShift CIS security profile](./CM-Configuration-Management/policy-compliance-operator-cis-scan.yaml) | This example creates a ScanSettingBinding that the ComplianceOperator uses to scan the cluster for compliance with the OpenShift CIS benchmark. | See the [Compliance Operator repository](https://github.com/openshift/compliance-operator) to learn more about the operator. **Note**: The Compliance Operator must be installed to use this policy. See the [Compliance operator policy](./CA-Security-Assessment-and-Authorization/policy-compliance-operator-install.yaml) to install the Compliance Operator with a policy.
[Kyverno Generate Network Policies](./CM-Configuration-Management/policy-kyverno-add-network-policy.yaml) | Configures a new `NetworkPolicy` resource named `default-deny` which will deny all traffic anytime a new Namespace is created. | See the [Kyverno project](https://github.com/kyverno/kyverno). **Note**: Kyverno controller must be installed to use the kyverno policy. See the [Policy to install Kyverno](../community/CM-Configuration-Management/policy-install-kyverno.yaml) in the community folder.
[Kyverno Generate Quota](./CM-Configuration-Management/policy-kyverno-add-quota.yaml) | Configures new `ResourceQuota` and `LimitRange` resources anytime a new Namespace is created. | See the [Kyverno project](https://github.com/kyverno/kyverno). **Note**: Kyverno controller must be installed to use the kyverno policy. See the [Policy to install Kyverno](../community/CM-Configuration-Management/policy-install-kyverno.yaml) in the community folder.
[Kyverno Sync Secrets](./CM-Configuration-Management/policy-kyverno-sync-secrets.yaml) | This policy will copy a Secret called `regcred` which exists in the `default` Namespace to new Namespaces when they are created and it will keep the secret updated with changes. | See the [Kyverno project](https://github.com/kyverno/kyverno). **Note**: Kyverno controller must be installed to use the kyverno policy. See the [Policy to install Kyverno](../community/CM-Configuration-Management/policy-install-kyverno.yaml) in the community folder.

### Contingency Planning

Expand Down