(Appears on: TrilioAppCondition)
(Appears on: TrilioVaultManagerSpec)
Field | Description |
| Helm Chart version |
| Namespace for Tiller (Helm V2 only) |
(Appears on: TrilioVaultManagerSpec)
(Appears on: TrilioVaultManagerStatus)
Field | Description |
| ConditionType of TrilioVault Application |
| ConditionStatus of TrilioVault Application |
| ConditionReason of TrilioVault Application |
| ApplicationCondition message |
| TransitionTime of last status |
(Appears on: TrilioAppCondition)
(Appears on: TrilioAppCondition)
(Appears on: TrilioVaultManagerStatus)
Field | Description |
| Name of TrilioAppRelease |
| Manifest referencing the TrilioAppRelease |
TrilioVaultManager is the Schema for the triliovaultmanagers API
Field | Description |
| Refer to the Kubernetes API documentation for the fields of the |
| Spec for TrilioVaultManager |
| Status for TrilioVaultManager |
(Appears on: TrilioVaultManager)
TrilioVaultManagerSpec defines the desired state of TrilioVaultManager
Field | Description |
| Helm Chart version of TrilioVault Application |
| Helm Version |
| Scope for the application which will be installed in the cluster NamespaceScope or ClusterScope |
| ResourceNamespaces are the namespace where you want to restore your applications |
| Resources is the resource requirements for the containers. |
| DeploymentLimits are the resource limits for all the deployments. |
| MetadataJobLimits are the resource limits for all the meta processing jobs. |
| DataJobLimits are the resource limits for all the data processing jobs. |
| NodeSelector specifies a map of key-value pairs. For the pod to be eligible to run on a node, the node must have each of the indicated key-value pairs as labels. |
| The scheduling constraints on application pods. |
| The toleration of application against the specific taints on the nodes |
(Appears on: TrilioVaultManager)
Field | Description |
| Trilio Application condition |
| Trilio Application deployed release |