Initializing the MSDP operator
Run the following command to initialize MSDP operator.
kubectl msdp init -i <acr-url>/msdp-operator:<version> -s <storage-class-name> [-l agentpool=<nodepool-name>]
You can use the following init command options.
Table: init command options
Option | Description |
|---|---|
-i | MSDP operator images on your ACR. |
-s | The storage class name. |
-l | Node selector of the MSDP operator. By default, each node pool has a unique label with key-value pair agentpool=<nodepool-name>. If you have assigned a different and cluster-wise unique label for the node pool, you can use that instead of agentpool. |
-c | Core pattern of the operator pod. Default value: "/core/core.%e.%p.%t" |
-d | Enable debug-level logging in MSDP operator. |
-a | The maximum number of days to retain the old log files. Range: 1-365 Default value: 28 |
-u | The maximum number of old log files to retain. Range: 1-20 Default value: 20 |
-n | Namespace scope for this request. Default value: msdp-operator-system |
-o | Generate MSDP operator CRD YAML. |
-h | Help for the init command. |
This command installs Custom Resource Definitions (CRD) msdpscaleouts.msdp.veritas.com and deploys MSDP operator in the Kubernetes environment. MSDP operator runs with Deployment Kubernetes workload type with single replica size in the default namespace msdp-operator-system.
MSDP operator also exposes the following services:
Webhook service
The webhook service is consumed by Kubernetes api-server to mutate and validate the user inputs and changes of the MSDP CR for the MSDP Scaleout configuration.
Metrics service
The metric service is consumed by Kubernetes/AKS for Azure Container Insight integration.
You can deploy only one MSDP operator instance in an AKS cluster.
Run the following command to check the MSDP operator status.
kubectl -n msdp-operator-system get pods -o wide