#How do I proceed when using TridentBackendConfig CR instead of tridentctl

1 messages · Page 1 of 1 (latest)

native token
#

The official Trident documentation describes an update of the Trident backend configuration (without changing any key-values !) using "tridentclt" for certain processes. (e.g. detecting new aggregates..)
e.g.
./tridentctl update backend <backend-name> -f <backend-json-file> -n <namespace>

We are using TridentBackendConfig CR instead of tridentctl for the backend management regarding: https://docs.netapp.com/us-en/trident/trident-use/backend_options.html

How do I proceed when using TridentBackendConfig CR instead of tridentctl for the backend update ?

Move between backend management options

Learn about the different ways of managing backends in Trident.

jolly panther
#

tridentctl update backend just applies the changes you made in your YAML file.

When using the CRDs, you can just kubectl apply -f my-backend.yaml to achieve the same

rapid kettle
#

you don't really need to do anything to "discover new aggregates" than a rollout-restart of trident after the SVM has been configured to have the new aggregates in the SVM's "aggr-list" option