#Install Alauda Container Platform Compliance with Kyverno

Alauda Container Platform Compliance with Kyverno is a platform service that integrates Kyverno for managing compliance policies on the Alauda Container Platform.

#Install via console

1. Navigate to Administrator
2. In the left navigation bar, click Marketplace > Cluster Plugins
3. Search for Alauda Container Platform Compliance with Kyverno and click to view its details
4. Click Install to deploy the plugin

#Install via YAML

#1. Check available versions

Ensure the plugin has been published by checking for ModulePlugin and ModuleConfig resources, in global cluster :

# kubectl get moduleplugins kyverno
NAME      AGE
kyverno   4d20h

# kubectl get moduleconfigs -l cpaas.io/module-name=kyverno
NAME             AGE
kyverno-v4.0.4   4d21h

This indicates that the ModulePlugin kyverno exists in the cluster and version v4.0.4 is published.

#2. Create a ModuleInfo

Create a ModuleInfo resource to install the plugin without any configuration parameters:

apiVersion: cluster.alauda.io/v1alpha1
kind: ModuleInfo
metadata:
  annotations:
    cpaas.io/display-name: kyverno
    cpaas.io/module-name: '{"en": "Alauda Container Platform Compliance for Kyverno",
      "zh": "Alauda Container Platform Compliance for Kyverno"}'
  labels:
    cpaas.io/cluster-name: global		
    cpaas.io/module-name: kyverno
    cpaas.io/module-type: plugin
    cpaas.io/product: Platform-Center
  name: kyverno-global				
spec:
  version: v4.2.0							

Field explanations:

• name: Temporary name for the cluster plugin. The platform will rename it after creation based on the content, in the format <cluster-name>-<hash of content>, e.g., global-ee98c9991ea1464aaa8054bdacbab313.
• label cpaas.io/cluster-name: Specifies the cluster where the plugin should be installed.
• label cpaas.io/module-name: Plugin name, must match the ModulePlugin resource.
• label cpaas.io/module-type: Fixed field, must be plugin; missing this field causes installation failure.
• .spec.config: If the corresponding ModuleConfig is empty, this field can be left empty.
• .spec.version: Specifies the plugin version to install, must match .spec.version in ModuleConfig.

#Uninstallation Procedures

1. Follow steps 1-3 from the installation process to locate the plugin
2. Click Uninstall to remove the plugin