Skip to content

Glossary

Short definitions for the vocabulary used across these docs, alphabetised for lookup. For how these pieces fit together, see Core Concepts.

Terms

Section titled “Terms”
  • Access token: A registry credential for CI and other automation, pull only or push and pull, that expires 1 to 365 days after it is created. Its secret is shown once.
  • API Key: A tenant-scoped credential for machine-to-machine access to the Kupe API.
  • AppProject: An Argo CD project that defines allowed repositories and destinations for a set of applications.
  • Argo CD Application: A resource that defines where manifests come from and where they are deployed.
  • Cluster connection: A link between a tenant’s registry and one of its clusters that lets every pod in the cluster pull from the registry, and can give chosen namespaces a Secret to push with.
  • Custom Domain: A tenant-owned domain name mapped to an application running on Kupe Cloud.
  • Database: A PostgreSQL database owned by a tenant, alongside its clusters rather than inside one. Deleting a cluster never deletes a database.
  • Database binding: A grant of one role of one database to one or more namespaces of one cluster. It delivers a Service named after the database and a credentials Secret into each of those namespaces and opens a network path from them.
  • GitOps: An operating model where Git is the source of truth and a controller reconciles live state to match it.
  • Grafana Explore: Grafana’s query interface for inspecting logs and metrics directly.
  • High Availability (HA): An option that helps keep the cluster API available during maintenance or a node failure.
  • HTTPRoute: A Gateway API resource that defines hostname, path matching, and backend routing.
  • Image: One pushed build in a registry repository, identified by its digest. A multi-platform image is an index that points to one image per platform.
  • Managed Cluster: A Kupe cluster created and operated through the platform.
  • OIDC kubeconfig: A kubeconfig that uses interactive login and short-lived tokens for CLI access.
  • Registry: A tenant’s private container registry at registry.kupe.cloud/<tenant>. A tenant has at most one.
  • Repository: A named set of images in a registry, such as team-a/api, created by the first push to that name.
  • Secret: A platform-managed secret definition delivered to selected namespaces.
  • SLO: Service Level Objective, a measurable reliability target for a service.
  • Sync Target: A cluster and namespace pair that a managed secret is delivered to.
  • Tag: A movable name for an image in a registry repository, such as 1.4.0 or latest.
  • Tenant: The primary isolation boundary in Kupe Cloud. A tenant owns clusters, databases, a registry, secrets, members, and API keys.
  • Token kubeconfig: A kubeconfig that uses a generated bearer token for automation.