Remove Kyverno in stable readme

Signed-off-by: yiraeChristineKim <yikim@redhat.com>

README.md

@@ -90,7 +90,7 @@ GitOps through Open Cluster Management is able to handle Kustomize files, so you
 [Policy Generator](https://github.com/stolostron/policy-generator-plugin) Kustomize plugin to
 generate policies from Kubernetes manifests in your repository. The Policy Generator handles
 Kubernetes manifests as well as policy engine manifests from policy engines like
-[Gatekeeper](https://open-policy-agent.github.io/gatekeeper/) and [Kyverno](https://kyverno.io/).
+[Gatekeeper](https://open-policy-agent.github.io/gatekeeper/).
 
 For additional information about the Policy Generator:
 

stable/README.md

@@ -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