3.0.X
Search…
⌃K

Examples

Refer to the example provided below for managing the TrilioVaultManager Custom Resource Definition.

TrilioVaultManager

TrilioVaultManager CRD, owned by TrilioVault Operator for Upstream/Non-Operator Lifecycle Manager (OLM) based environments, manages the lifecycle of TrilioVault for Kubernetes Application.
The following snippet provides an example on how to use the TrilioVaultManager CRD.
The version number provided below is only for illustrative purposes. Please refer to the Compatibility Matrix to find the latest version to use.
apiVersion: triliovault.trilio.io/v1
kind: TrilioVaultManager
metadata:
labels:
triliovault: triliovault
name: trilio-app
spec:
trilioVaultAppVersion: 0.2.5
helmVersion:
version: v3
tillerNamespace: "kube-system"
applicationScope: Namespaced
restoreNamespaces: ["kube-system", "default", "restoreinme", "restore-namespace", "restore"]
resources:
requests:
memory: 400Mi
In the above CRD restoreNamespaces is optional. Application scope of Namespaced, will enable additonal namespaces that can be restored into. Application scope of clustered will restrict restores to those specific namespaces only.

Provide Resource Limits for TrilioVault Pods

apiVersion: triliovault.trilio.io/v1
kind: TrilioVaultManager
metadata:
labels:
triliovault: k8s
name: tvk
spec:
trilioVaultAppVersion: 2.5.0
applicationScope: Cluster
# TVK components configuration, currently supports control-plane, web, exporter, web-backend, ingress-controller, admission-webhook.
# User can configure resources for all componentes and can configure service type and host for the ingress-controller
componentConfiguration:
web-backend:
resources:
requests:
memory: "400Mi"
cpu: "200m"
limits:
memory: "2584Mi"
cpu: "1000m"
ingress-controller:
service:
type: LoadBalancer
host: "trilio.co.in"