Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

A tour of the Trilio for Kubernetes management console on OpenShift, so you know where everything lives before you create your first backup target and backup plan. You will see: Chapters Recorded on Red Hat OpenShift 4.21 with Trilio for Kubernetes 5.4.1.

Before you install Kubernetes backup on OpenShift, check that your cluster can take CSI snapshots. This video checks the OpenShift version, StorageClasses and VolumeSnapshotClasses, and runs the Trilio for Kubernetes preflight check. You will: Best practices covered: check the compatibility matrix before every install and every OpenShift upgrade; run the preflight against every StorageClass you protect, and again when you add one; keep CPU, memory and object-count quotas off the T4K namespace.

Install the Trilio for Kubernetes backup operator on Red Hat OpenShift from the Software Catalog (OperatorHub on earlier versions), with the settings we recommend for production. You will: Best practices covered: run only GA builds in production and stay on the latest maintenance release of your minor version; approve upgrades through change control; keep T4K alone in trilio-system, because Manual approval applies to every operator in the namespace.

Deploy Trilio for Kubernetes on Red Hat OpenShift by creating the TrilioVault Manager, the resource that runs T4K, and open the T4K management console. You will: Best practices covered: change T4K only through the TrilioVault Manager and keep its manifest in version control (the operator reverts changes made anywhere else); size the job deadline from measured backup throughput (the default is 12 hours); measure datamover memory on a representative backup before production; reach the console through the HTTPS ingress, never port-forward.