Documentation

Environment Management Guide

Create, configure, and operate reusable environments in NebuaCloud

Environments are reusable deployment profiles that standardize how teams deploy apps and add-ons across clusters.

Use an environment when you want consistent defaults for:

infrastructure provider context
access URL, storage, and add-on defaults
gateway exposure and published sites
add-on access and credential workflows

Why Environments Matter

An environment lets you define platform policy once and reuse it everywhere.

Typical outcomes:

faster application onboarding
fewer manual config mistakes
consistent gateway and add-on behavior across clusters
easier operations because every app follows the same base profile

Create an Environment

From Dashboard > Environments:

Select Create.
Provide a clear, team-oriented name.
Add a short description so teams understand intended usage.
Select the provider profile.
Enable required add-ons (for example Argo CD, cert-manager, access URL, storage provider).
Save.

Naming recommendations:

production-shared
sandbox-team-a
edge-gateway-public

Environment Details

Each environment contains:

provider and cluster attachment information
installed add-on preferences
gateway runtime status
environment ID (used by gateway connector flows)

Use the environment details view to validate that your profile is correctly attached to the expected clusters.

Gateway Sites

The Gateway Sites tab manages public domain routing for the selected environment.

You can:

create and edit site routes
define domain, target host, target port, and protocol
enable or disable routes without deleting them
track sync and agent status

If gateway connector health is degraded or offline, route propagation may fail until the connector reconnects.

Add-on Access Information

The Add-on Access tab discovers runtime access points and credential metadata.

For each discovered add-on you can review:

access URLs and endpoint origin
relevant Kubernetes resources
credential references and password reveal actions

Use this panel when operators need immediate access to tools like Argo CD without manually searching cluster secrets.

Add-on Configuration

The Add-on Configuration tab allows saving desired values and applying them.

Recommended workflow:

Save desired values first.
Review changes.
Apply when ready.

This separates draft configuration from active rollout and reduces accidental production drift.

Warning History

Environment warning history aggregates recent agent warnings per cluster.

Use it to quickly identify:

failing add-on reconciliations
gateway connection problems
gateway connector connection problems
repeated environment-level errors requiring host intervention

Mobile Usage

The environment list is optimized for mobile cards.

On smaller screens:

use card expansion for details
open warning history per environment
use tabbed detail sections to avoid horizontal scrolling

Operational Best Practices

Keep environments small and purpose-specific.
Avoid changing production defaults during active rollouts.
Review warning history before deleting or reusing an environment.
Delete only environments not referenced by active clusters or apps.
Document internal ownership for each environment profile.

Common Troubleshooting

Cannot reveal add-on password

Check:

environment has valid cluster attachment
add-on is installed in the expected cluster scope
credential secret/key exists
session and organization permissions are valid

Gateway site status not syncing