From c15e2a5bdbfe6101a04ef9df3cdb00f195ff1c86 Mon Sep 17 00:00:00 2001 From: asifdxtreme Date: Tue, 26 Apr 2022 19:17:55 +0530 Subject: [PATCH] Add the usage guide for new CRD --- .../update-configmap-using-crd.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 docs/getting-started/update-configmap-using-crd.md diff --git a/docs/getting-started/update-configmap-using-crd.md b/docs/getting-started/update-configmap-using-crd.md new file mode 100644 index 0000000..065316e --- /dev/null +++ b/docs/getting-started/update-configmap-using-crd.md @@ -0,0 +1,19 @@ +## CompatibilityConfig + +The newly introduced CRD gives user a simpler way to update the compatibility matrix +without using the `vdoctl`. + +To use the new CRD you can create the object referred below +```shell +apiVersion: vdo.vmware.com/v1alpha1 +kind: CompatibilityConfig +metadata: + name: compat-matrix-config + namespace: vmware-system-vdo +spec: + matrixURL: "https://github.com/vmware-tanzu/vsphere-kubernetes-drivers-operator/releases/download/0.3.0-rc/compatibility.yaml" +``` + +You can update the matrixURL as per your requirement. + +**Note** : Make sure you keep the name of the CompatibilityConfig(`compat-matrix-config`) unchanged. The namespace can be updated as per usage. \ No newline at end of file