Skip to content
UMKIMDocs
Search limited to 0.1.0. Switch to the latest version for up-to-date results.

App deploy and routes

This content is for 0.1.0. Switch to the latest version for up-to-date documentation.

Catalog deployment is optional in v0.1.0. For an authenticated deploy:

  1. Store sensitive field values in the target-cluster Kubernetes Secret through the supported secret-binding flow.
  2. Submit the catalog instance with secret references only.
  3. Let DCM evaluate placement against eligible ManagedCluster labels.
  4. Wait for the matching ready provider to materialize the workload.
  5. If routing is selected, let fleet-edge reconcile the resulting FleetAppRoute.

Provider readiness and configured placement are prerequisites. Do not place plaintext credentials in catalog values, logs, or source control.

Deleting an instance requests provider cleanup. The available delete modes vary in how they handle unavailable providers, but none is a substitute for a verified workload backup or recovery plan.

Public routes, certificates, and failover remain experimental and operator-managed. See fleet-edge and Backup and restore.