Components and Deployments

This article covers the day-to-day workflow for Components: finding one,
changing its configuration, creating, cloning and deleting Components, and what
to do when a save fails. Everything you run is managed through the Environment
→ Service → Component model — see Key Concepts if those terms
are new.

Finding your deployment

1. Open the Environment your application runs in.
2. Open the Service that contains it.
3. Click the application Component to open its dashboard.

The dashboard shows the Component's current configuration, status, variables,
and secrets.

Changing a component's configuration

1. Open the Component dashboard.
2. Edit the configuration — values, variables, resource limits, and whatever
   else applies to that Component type.
3. Click Save. The platform applies the change automatically.

Watch the status after saving rather than assuming the change landed. A save is
a deployment.

Creating a new Component

Every new Component is created from Applications → Deployments:

1. Go to Applications → Deployments and click + New.

   

2. Under ENVIRONMENTS, select the Environment.

3. Under APPLICATIONS, which appears once an Environment is selected, select the Catalog item you want.

4. Choose the SERVICE and NAMESPACE, and enter a NAME.

   

5. Fill in the configuration and click Save.

Applications → Catalog lists every item you can create, by category — K8s
Services, Applications, Managed Databases, Self Managed Databases, Databases,
Streaming, Environments, and AWS, GCP and Azure Services. It is a reference
list; you create the Component from + New, not from the Catalog.

The platform provisions it and it appears in your Service.

Cloning a Component

To copy a Component's configuration into another Environment or Service —
promoting a staging setup to production, for example:

1. Open the Component you want to clone.
2. Select Clone from the actions menu.
3. Choose the target Environment, Service, and namespace.
4. Override any configuration values that differ in the target.
5. Save.

Cloning copies configuration only. It does not copy data, persistent storage, or
any runtime state.

Deleting a Component

1. Open the Component.
2. Select Delete from the actions menu and confirm.

When a save fails or a Component shows degraded

A Degraded state means the Component is deployed but not healthy. The reason
is shown on the Component dashboard itself, so read the status indicator before
raising anything.

1. Read the reason on the dashboard. A rejected configuration value or a failed
   deployment is usually named there directly.
2. Check the Component's Logs tab. If the configuration applied but the
   application will not start, the cause is in the log output — see
   Workload Resources and Health Checks
   for the common failure states and what they mean.
3. If the change you just made caused it, revert that change and save again to
   get back to a known-good state.
4. If the dashboard reason is not actionable from your side, raise a request
   with the Environment, Service, Component name, what you changed, and the
   status message shown.

If the save never finishes deploying at all, see
Deployment Stuck and Never Reaches Synced or Deployed.

Related articles

• Workload Resources and Health Checks
• Deploy Without Downtime or Killing Running Work
• Deployment Stuck and Never Reaches Synced or Deployed
• CronJobs
• Application Dependencies
• Container Registry Repositories and CI Push Access
• Getting Help