Install extension using the Kustomize and CR YAMLs
The extension folder contains two sample YAMLs - kustomize.yaml, and cloudpoint_crd.yaml, based on which you need to create new YAMLs with the relevant values as per your environment.
kustomize.yaml
In the kustomize.yaml, update the parameters in the section with relevant values as described in the following table.
Parameter | Description |
|---|---|
newName | Specify the CloudPoint image name, along with the container registry path. Example: <account_id>.dkr.ecr.us-east-2.amazonaws.com/veritas/flexsnap-cloudpoint |
newTag | Specify the tag of the CloudPoint image to be deployed. Example: |
Example:
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
resources:
- cloudpoint_service.yaml
patchesStrategicMerge:
- node_select.yaml
namespace: demo-cloudpoint-ns
images:
- name: CLOUDPOINT_IMAGE
newName: <account_id>.dkr.ecr.us-east-2.amazonaws.com/veritas/flexsnap-cloudpoint
newTag: 10.2.0.9129
vars:
- name: ServiceAccount.cloudpoint-acc.metadata.namespace
objref:
kind: ServiceAccount
name: cloudpoint-acc
apiVersion: v1
fieldref:
fieldpath: metadata.namespace
configurations:
- cloudpoint_kustomize.yamlcloudpoint_crd.yaml
In the cloudpoint_crd.yaml custom resource, update the parameters in the section with relevant values as described in the following table.
Parameter | Description |
|---|---|
cloudpointHost | Specify the CloudPoint hostname or IP. |
cloudpointExtensionToken | Paste the contents of the CloudPoint token that was downloaded earlier from NetBackup Web UI - Add extension dialog. |
storageClassName | Kubernetes storage class that was created earlier in the preparation steps. Example: |
size | Volume size in GB to be provisioned as per your scaling requirements. |
namespace | The namespace that was created earlier in the preparation steps, in which to deploy CloudPoint. |
Example:
apiVersion: veritas.com/v1
kind: CloudpointRule
metadata:
name: cloudpoint-config-rule
namespace: demo-cloudpoint-ns
spec:
CLOUDPOINT_HOST: 3.17.**.*** .
CLOUDPOINT_EXTENSION_TOKEN: workflow-3s3tlpwpy62dyoingxqmfeojlky7bub9rbzx8srh8kdgmsqo6f-q85lflg8a5i72hqarl7icb9xl0ydzfociziedicxlflesd4z4mljn8tfqs70vvzhzrt7z3gbqyv765s7nuivrzl0d0vg6bstjpge9xbft2ox92kdkmje8ysm3l276eu0fvgolnkeu5fdesfdnl845p9psbpw9nei67c2rn0bc71gf1a7yx5ua74rmc40on0c27h8zt
RENEW: false
LOG_STORAGE:
STORAGE_CLASS_NAME: efs-sc-new-root
SIZE: 100Then run the following commands from the folder where the YAML files are located.
To apply the Kustomize YAML: kubectl apply -k ./
To apply the CloudPoint CR.kubectl apply -f cloudpoint_crd.yaml
node_select.yaml
In the node_select.yaml nodeSelector under the section, replace the values of NODE_AFFINITY_KEY and NODE_AFFINITY_VALUE in node_select.yaml. User can obtain these details using the following commands:
Use the following command to obtain the name of any node:
# kubectl get nodes
Depending on the specific cloud provider, use the following respective commands based on the the label:
For Azure: # kubectl describe node <node_name> | grep -i labels
Output example:
agentpool=cpuserpoolFor AWS: # kubectl describe node <node_name> | grep -i <node_group_name>
Output example:
eks.amazonaws.com/nodegroup=Demo-NG
Parameter | Description |
|---|---|
NODE_AFFINITY_KEY |
|
NODE_AFFINITY_VALUE | Name of the node pool.
|