Maintaining the TrilioVault Controller Cluster
The TrilioVault Controller Cluster can be maintained utilizing the TrilioVault deployment binary and the helm commands
TrilioVault binary overview
Provides all available commands of the TrilioVault binary.
Configuring local DNS nameservers for wlm-workloads and wlm-api
In certain scenarios it might be necessary to set additional local DNS nameservers for the wlm-workloads and wlm-api pods.
This can be done through the TrilioVault binary
Updating the TrilioVault Controller Cluster
To update the TrilioVault Controller Cluster to the latest version available the helm commands are used on any of the Kubernetes Master Nodes. In case of a 3 node Cluster, all nodes are Kubernetes Master Nodes. In case of a 5 or more node Cluster, the first 3 nodes in the deployment.json are the master nodes.
To upgrade the cluster the following commands are run. It is required to reconfigure the Cluster after the upgrade.
Redeploy the TrilioVault Controller Cluster
Deletes the complete TrilioVault Controller cluster and all its artifacts before redeploying the same based on the last deployment. Requires a new configuration of the redeployed containers.
Reset the TrilioVault Controller Cluster
Deletes the TrilioVault containers and redeploys the same. Requires a new configuration of the redeployed containers
Cleanup the TrilioVault Controller Cluster
Deletes the complete TrilioVault Controller Cluster and all its artifacts.
Last updated