deploy: bd3eb30

Author: gaurav-nelson

blog/2021-12-31-medical-diagnosis/index.html

@@ -5333,10 +5333,12 @@
 Excited or intrigued by what you see here? We’d love to hear your thoughts and ideas! Try the patterns contained here and see below for links to our repositories and issue trackers.
 How can I get involved? Try out what we’ve done and submit issues to our issue trackers.
 We will review pull requests to our pattern repositories.
-`,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/blog/":{title:"Blog",tags:[],content:`Find out the latest news about Validated Patterns.
-`,url:"https://validatedpatterns.io/blog/",breadcrumb:"/blog/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:`
+`,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/netapp-dr-starter-kit/":{title:"NetApp DR Starter Kit",tags:[],content:`NetApp DR Starter Kit This pattern is under contstruction and the docs will be added soon! This pattern is currently in the sandbox tier, which means it is a work in progress and may not be fully tested or documented. We welcome contributions and feedback to help improve this pattern and move it to higher tiers.
+`,url:"https://validatedpatterns.io/patterns/netapp-dr-starter-kit/",breadcrumb:"/patterns/netapp-dr-starter-kit/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product.
+`,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:`
 Deploy complex solutions with unprecedented speed and confidence. Go beyond traditional reference architectures. Validated Patterns deliver automated, rigorously tested application stacks for your hybrid cloud, powered by GitOps.
-`,url:"https://validatedpatterns.io/",breadcrumb:"/"},"https://validatedpatterns.io/blog/2026-04-13-own-argocd-instance/":{title:"Validated Patterns now deploys its own ArgoCD instance",tags:[],content:` Preamble Until now the Validated Patterns operator relied on the default ArgoCD instance created by the OpenShift GitOps operator in the openshift-gitops namespace. While this worked, it meant that the patterns framework shared its ArgoCD instance with whatever else the cluster administrator or the gitops operator itself might configure there. Starting with the 0.0.70 version of the patterns operator, new deployments will get their own dedicated ArgoCD instance running in a brand-new vp-gitops namespace.
+`,url:"https://validatedpatterns.io/",breadcrumb:"/"},"https://validatedpatterns.io/blog/":{title:"Blog",tags:[],content:`Find out the latest news about Validated Patterns.
+`,url:"https://validatedpatterns.io/blog/",breadcrumb:"/blog/"},"https://validatedpatterns.io/blog/2026-04-13-own-argocd-instance/":{title:"Validated Patterns now deploys its own ArgoCD instance",tags:[],content:` Preamble Until now the Validated Patterns operator relied on the default ArgoCD instance created by the OpenShift GitOps operator in the openshift-gitops namespace. While this worked, it meant that the patterns framework shared its ArgoCD instance with whatever else the cluster administrator or the gitops operator itself might configure there. Starting with the 0.0.70 version of the patterns operator, new deployments will get their own dedicated ArgoCD instance running in a brand-new vp-gitops namespace.
 Why the change Sharing the default openshift-gitops ArgoCD instance had a few drawbacks:
 Potential conflicts Any other workload or operator that also relied on the default ArgoCD instance could interfere with the patterns deployment, and vice versa.
 Lifecycle coupling Upgrades or configuration changes to the gitops-operator’s default instance could unexpectedly affect a running pattern.
@@ -5349,8 +5351,7 @@
 What changes for existing deployments Nothing. If you already have a running Validated Patterns deployment that uses the default openshift-gitops ArgoCD instance, it will continue to work exactly as before. The operator detects whether the legacy openshift-gitops/openshift-gitops ArgoCD CR exists at reconciliation time. If it does, the operator operates in legacy mode: it keeps using the existing instance and does not set DISABLE_DEFAULT_ARGOCD_INSTANCE on the gitops-operator subscription. Your environment is not affected in any way.
 This detection happens automatically on every reconcile loop, so there is no manual configuration or migration step needed. Existing clusters that upgrade the patterns operator will simply keep running as they always have.
 Summary This change gives the Validated Patterns framework its own independent ArgoCD instance, improving isolation and giving the operator full control over its GitOps engine. Existing deployments are unaffected and will continue to use the openshift-gitops instance they were deployed with. New deployments will automatically get the dedicated vp-gitops instance with no additional configuration required.
-`,url:"https://validatedpatterns.io/blog/2026-04-13-own-argocd-instance/",breadcrumb:"/blog/2026-04-13-own-argocd-instance/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product.
-`,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/patterns/trilio-continuous-recovery/":{title:"Trilio Continuous Restore",tags:[],content:`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 Hat OpenShift. By integrating Trilio for Kubernetes with the Red Hat Validated Patterns framework, the pattern delivers:
+`,url:"https://validatedpatterns.io/blog/2026-04-13-own-argocd-instance/",breadcrumb:"/blog/2026-04-13-own-argocd-instance/"},"https://validatedpatterns.io/patterns/trilio-continuous-recovery/":{title:"Trilio Continuous Restore",tags:[],content:`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 Hat OpenShift. By integrating Trilio for Kubernetes with the Red Hat Validated Patterns framework, 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 Hat Advanced Cluster Management (ACM) Use case The pattern targets organizations that need a documented, repeatable DR posture for Kubernetes-native workloads — particularly those that must demonstrate RTO/Recovery Point Objective (RPO) targets through regular, automated DR tests rather than annual manual exercises.
 A WordPress + MySQL deployment is included as a representative stateful application. It serves as the reference workload for the full backup, restore, and URL-rewrite lifecycle.
 Architecture graph TD subgraph Git["Git (Source of Truth)"] values["values-hub.yaml\\nvalues-secondary.yaml\\ncharts/"] end subgraph Hub["Hub Cluster (primary)"] ACM["ACM"] ArgoCD["ArgoCD"] Vault["HashiCorp Vault + ESO"] Trilio_Hub["Trilio Operator + TVM"] CronJob["Imperative CronJob\\n(DR lifecycle automation)"] end subgraph Spoke["DR Cluster (secondary)"] Trilio_Spoke["Trilio Operator + TVM"] EventTarget["EventTarget pod\\n(pre-stages PVCs)"] ConsistentSet["ConsistentSet\\n(restore point)"] end S3["Shared S3 Bucket"] Git -->|GitOps sync| ArgoCD ArgoCD --> Trilio_Hub Vault -->|S3 creds + license| Trilio_Hub Trilio_Hub -->|backups| S3 ACM -->|provisions| Spoke S3 -->|EventTarget polls| EventTarget EventTarget --> ConsistentSet CronJob -->|restore from ConsistentSet| ConsistentSet Component roles Component Where Role 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 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 CR BackupPlan Hub Continuous Restore variant of BackupPlan; drives pre-staging on the spoke EventTarget pod Spoke Watches the shared S3 bucket for new backups; pre-stages Persistent Volume Claims (PVCs) locally ConsistentSet Spoke Cluster-scoped CR representing a fully pre-staged restore point HashiCorp Vault and External Secrets Operator (ESO) Hub Secret management; S3 credentials and Trilio license are never stored in Git How Continuous Restore works The hub creates a backup using the CR BackupPlan and writes it to the shared S3 storage. The EventTarget pod on the spoke detects the new backup and begins copying volume data locally — ahead of any DR event. When the spoke’s imperative job detects an Available ConsistentSet, it submits a Restore CR. Because the data is already local, only backup metadata is fetched — resulting in significantly lower RTO than a standard on-demand restore. The post-restore Hook CR rewrites WordPress database URLs to the DR cluster’s ingress domain. Links Trilio for Kubernetes documentation Red Hat Validated Patterns Validated Patterns imperative framework Red Hat Advanced Cluster Management (ACM) External Secrets Operator Next steps Prerequisites Getting started CR operations Troubleshooting `,url:"https://validatedpatterns.io/patterns/trilio-continuous-recovery/",breadcrumb:"/patterns/trilio-continuous-recovery/"},"https://validatedpatterns.io/blog/2026-02-16-pattern-uninstall/":{title:"Experimental support for pattern uninstall",tags:[],content:` We are excited to announce that uninstalling patterns are now experimentally supported from pattern operator version 0.0.65 To initiate the uninstallation, only the pattern cr needs to be deleted.