Tiering

A replacement Pod starts with fresh memory. Decide whether the application can refill its cache or needs state recovered from a storage tier.

Need	Choice
Rebuildable cache	Memory-only sidecar
Local disk capacity or restart recovery	Atmos, a commercial option documented separately
Recovery beyond the local node	Swytch Cloud, subject to upload acknowledgement

The public operator workflow requires either DNS or Cloud discovery and provisions no PVCs. Atmos configuration is covered in the commercial documentation.

Configure Cloud discovery and storage

Generate credentials with swytch gen-passphrase --cloud and complete Cloud onboarding. Store the connection secret in the application’s namespace:

kubectl -n YOUR_NAMESPACE create secret generic swytch-cloud \
  --from-literal=connection-secret='YOUR_CONNECTION_SECRET'

Replace the profile’s spec.discovery block with:

discovery:
  cloud:
    secretKeyRef:
      name: swytch-cloud
      key: connection-secret

Use exactly one discovery mode. Cloud replaces DNS discovery and the separate cluster passphrase. The operator does not create the account or Secret.

Recreate existing sidecar Pods for the change to take effect. Cloud uploads are asynchronous; an acknowledged Redis write is not an acknowledgement of durable Cloud storage. See durability semantics.