<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Replications on Capsule</title><link>https://deploy-preview-188--docs-projectcapsule.netlify.app/docs/replications/</link><description>Recent content in Replications on Capsule</description><generator>Hugo -- gohugo.io</generator><language>en</language><atom:link href="https://deploy-preview-188--docs-projectcapsule.netlify.app/docs/replications/index.xml" rel="self" type="application/rss+xml"/><item><title>GlobalTenantResources</title><link>https://deploy-preview-188--docs-projectcapsule.netlify.app/docs/replications/global/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://deploy-preview-188--docs-projectcapsule.netlify.app/docs/replications/global/</guid><description>Use admission triggers to reconcile source changes between periodic resyncs.
Overview GlobalTenantResource is a cluster-scoped CRD designed for cluster administrators. It lets you automatically replicate Kubernetes resources - such as Secrets, ConfigMaps, or custom resources - into the Namespaces of selected Tenants. Tenant owners cannot create GlobalTenantResource objects; for tenant-scoped replication, see TenantResource.
The diagram below shows that an Administrator can create a GlobalTenantResource. In the GlobalTenantResource spec, an Administrator specifies which resource they would like to replicate, and where this resource should be replicated to.</description></item><item><title>TenantResources</title><link>https://deploy-preview-188--docs-projectcapsule.netlify.app/docs/replications/tenant/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://deploy-preview-188--docs-projectcapsule.netlify.app/docs/replications/tenant/</guid><description>Use admission triggers to reconcile source changes between periodic resyncs.
Overview TenantResource is a namespace-scoped CRD that lets Tenant owners automatically replicate Kubernetes resources across all Namespaces in their Tenant - without manual distribution or custom automation. It is the tenant-level counterpart to GlobalTenantResource, which is reserved for cluster administrators.
The diagram below shows that an Administrator or a Tenant Owner can create a TenantResource inside a Tenant. In the TenantResource spec, a user specifies which resource they would like to replicate across the Tenant.</description></item><item><title>Admission triggers</title><link>https://deploy-preview-188--docs-projectcapsule.netlify.app/docs/replications/triggers/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://deploy-preview-188--docs-projectcapsule.netlify.app/docs/replications/triggers/</guid><description>TenantResource and GlobalTenantResource support optional admission triggers. Triggers request reconciliation when a matching namespaced resource is created, updated, or deleted. This is useful when templates or replicated items depend on objects that can change between periodic reconciliations.
The resource behavior and destination namespace profiles remain defined in spec.resources. Triggers only control when Capsule requests reconciliation. Existing replications without triggers retain their behavior.
Example This GlobalTenantResource generates a count of selected Secrets in production namespaces.</description></item></channel></rss>