Skip to content

Platform Concepts

Today, Kupe Cloud is operated through the console for:

  • Cluster create, upgrade, and delete
  • Workload visibility and troubleshooting
  • CLI access and day-2 operations

Terraform provider and public API are planned, but not yet generally available.

Every cluster follows a clear lifecycle:

  • Pending or Provisioning during creation
  • Running when ready for workloads
  • Upgrading during platform-managed Kubernetes upgrades
  • Terminating when being deleted

Treat lifecycle phases as gates for automation and changes.

Application delivery is Git-driven using Argo CD:

  • Git is the source of truth.
  • Argo reconciles desired and live state.
  • Drift is visible and can be self-healed.

Traffic management is based on Kubernetes Gateway API resources:

  • Gateway provides ingress infrastructure.
  • HTTPRoute defines app routing behavior.
  • DNS and certificates should be automated for production paths.

Operate every workload with a standard triage path:

  1. Dashboards and alerts for high-level health.
  2. Metrics for trend and saturation analysis.
  3. Logs and events for root-cause detail.