Environments

The Environments dashboard is your top-level view in SVIEW. Each
Environment corresponds to a Kubernetes cluster on a specific cloud provider
(AWS or GCP) and represents one stage of your deployment lifecycle — dev,
staging, production, or test.

Dashboard view

Each Environment card shows:

• Name and stage (dev / staging / production / test)
• Cloud provider (AWS or GCP)
• Health status — whether the Environment's services are healthy
• Compliance status — from the platform's automated compliance checks
• Cost — spend for the current period

Click an Environment to open it and see the Services and Components running
inside it.

Inside an Environment

Opening an Environment shows:

• Services — the logical groups your team has set up in this Environment
• Heartbeat status — whether the platform agent monitoring this Environment
  is connected
• Environment-level settings — cloud region, stage, and namespace
  configuration

From here you can navigate into a Service to see its Components, or add a new
Service.

Suspend and resume (dev and demo Environments)

Non-production Environments can be suspended during off-hours to reduce cost.
See Suspending Non-Production Environments and Databases for how to configure a schedule or
suspend manually.

Creating a new Environment

Creating a new Environment or namespace is not yet self-service. Raise a
request in your dedicated Slack channel with the environment name, cloud
provider, and stage, and CTO2B will provision it for you.

Related articles

• Key Concepts — Environment, Service, Component, Stage
• SVIEW — Overview — navigating the rest of the portal
• RDS Backup Retention — how long database backups are kept per
  environment, and how to change it
• Suspending Non-Production Environments and Databases — scheduling off-hours suspension