Skip to content

fix: correct non-breaking space formatting for Red Hat references #665

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
gaurav-nelson merged 1 commit into from
Apr 16, 2026
Merged

fix: correct non-breaking space formatting for Red Hat references #665

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 11 additions & 11 deletions content/patterns/trilio-continuous-recovery/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,9 +4,9 @@ date: 2026-04-08
tier: sandbox
summary: A demonstration of Trilio Continuous Restore for stateful applications
rh_products:
- Red{nbsp}Hat OpenShift Container Platform
- Red{nbsp}Hat OpenShift GitOps
- Red{nbsp}Hat Advanced Cluster Management
- Red Hat OpenShift Container Platform
- Red Hat OpenShift GitOps
- Red Hat Advanced Cluster Management
partners:
- Trilio
industries:
Expand All @@ -19,16 +19,16 @@ links:
feedback: https://docs.google.com/forms/d/e/1FAIpQLScI76b6tD1WyPu2-d_9CCVDr3Fu5jYERthqLKJDUGwqBg7Vcg/viewform
---

# Trilio Continuous Restore — Red{nbsp}Hat Validated Pattern
# Trilio Continuous Restore — Red Hat Validated Pattern

## Overview

This Validated Pattern delivers an automated, GitOps-driven Disaster Recovery (DR) solution for stateful applications running on Red{nbsp}Hat OpenShift. By integrating [Trilio for Kubernetes](https://trilio.io) with the [Red{nbsp}Hat Validated Patterns framework](https://validatedpatterns.io), the pattern delivers:
This Validated Pattern delivers an automated, GitOps-driven Disaster Recovery (DR) solution for stateful applications running on Red Hat OpenShift. By integrating [Trilio for Kubernetes](https://trilio.io) with the [Red Hat Validated Patterns framework](https://validatedpatterns.io), the pattern delivers:

- **Automated backup** of stateful workloads on the primary (hub) cluster
- **Continuous Restore** — Trilio's accelerated Recovery Time Objective (RTO) DR path that continuously pre-stages backup data on the DR cluster so that recovery requires only metadata retrieval, not a full data transfer
- **Automated DR testing** — the full backup-to-restore lifecycle runs as a scheduled, self-healing GitOps workflow with no human intervention after initial setup
- **Multi-cluster lifecycle management** through Red{nbsp}Hat Advanced Cluster Management (ACM)
- **Multi-cluster lifecycle management** through Red Hat Advanced Cluster Management (ACM)

### Use case

Expand Down Expand Up @@ -78,9 +78,9 @@ graph TD
|-----------|-------|------|
| Trilio Operator | Hub + Spoke | Installed through Operator Lifecycle Manager (OLM) from the `certified-operators` catalog, channel `5.3.x` |
| TrilioVaultManager | Hub + Spoke | Trilio operand Custom Resource (CR); manages the Trilio data plane |
| Red{nbsp}Hat OpenShift | Hub + Spoke | Container orchestration platform; provides OLM, storage, networking, and the GitOps operator substrate |
| Red{nbsp}Hat OpenShift GitOps (ArgoCD) | Hub + Spoke | GitOps sync engine; all configuration is driven from Git |
| Red{nbsp}Hat Advanced Cluster Management (ACM) | Hub | Cluster lifecycle, policy enforcement, and spoke provisioning |
| Red Hat OpenShift | Hub + Spoke | Container orchestration platform; provides OLM, storage, networking, and the GitOps operator substrate |
| Red Hat OpenShift GitOps (ArgoCD) | Hub + Spoke | GitOps sync engine; all configuration is driven from Git |
| Red Hat Advanced Cluster Management (ACM) | Hub | Cluster lifecycle, policy enforcement, and spoke provisioning |
| Validated Patterns Imperative CronJob | Hub + Spoke | Runs the automated DR lifecycle on a 10-minute schedule |
| BackupTarget | Hub + Spoke | Points to the shared S3 bucket; the spoke BackupTarget has the EventTarget flag set |
| BackupPlan | Hub | Defines backup scope (wordpress namespace), quiesce/unquiesce hooks, and retention |
Expand All @@ -99,9 +99,9 @@ graph TD
## Links

- [Trilio for Kubernetes documentation](https://docs.trilio.io/kubernetes)
- [Red{nbsp}Hat Validated Patterns](https://validatedpatterns.io)
- [Red Hat Validated Patterns](https://validatedpatterns.io)
- [Validated Patterns imperative framework](https://validatedpatterns.io/learn/imperative-actions/)
- [Red{nbsp}Hat Advanced Cluster Management (ACM)](https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes)
- [Red Hat Advanced Cluster Management (ACM)](https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes)
- [External Secrets Operator](https://external-secrets.io)

## Next steps
Expand Down
2 changes: 1 addition & 1 deletion content/patterns/trilio-continuous-recovery/prerequisites.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ aliases: /trilio-cr/prerequisites/
| DR Spoke | Disaster Recovery target | 3 worker nodes, 8 vCPU / 32 GB each |

Both clusters must:
- Run Red{nbsp}Hat OpenShift 4.18 or later
- Run Red Hat OpenShift 4.18 or later
- Have network access to the shared S3 bucket
- Be reachable by ACM on the hub

Expand Down