How services relate to environments
Scope of Services per Environment, shared compute, internal networking to databases, and links to Environment docs.
Written By Zoro
Last updated 3 days ago
Every Service belongs to exactly one Environment.
The Environment is the stage (for example production or staging) inside an Application; Services in that Environment share the same Worker Node or managed compute attachment.
Read Environments (concept) under Core Concepts in the sidebar and Environments overview under Environments in the sidebar for the dashboard model.
Compute
Worker Nodes (or managed instances) attach to an Environment, not to individual Services. All Services in that Environment schedule onto that compute pool. To run workloads on different hardware, use different Environments (each with its own compute) or adjust your topology as your organisation allows.
See Attach compute to an environment under Environments in the sidebar and Worker Nodes (concept) under Core Concepts in the sidebar.
Isolation and networking
- Services in Environment A do not share runtime with Services in Environment B, even inside the same Application.
- Database internal credentials are intended for other Services in the same Environment. Cross-environment connections require a deliberate pattern (for example public Expose or external networking); see Databases overview under Databases in the sidebar.
Deployments are per Service
Each Service has its own Deployments history and logs. Rolling back or redeploying one Service does not automatically change siblings in the same Environment. See Deployments (concept) under Core Concepts in the sidebar and Deployments overview under Deployments and Operations in the sidebar.
Adding or moving Services
Use Create a service from the target Environment. If the product offers Switch project or similar on Settings for certain servers, use in-product help text; self-hosted operator docs may describe server moves separately.
If something fails
- Compute and worker node issues under Troubleshooting in the sidebar: node not ready, SSH, or capacity.
- Deployment issues under Troubleshooting in the sidebar: deploy failures on the Service.