Environments List
The Environments List displays all the environments defined within your infrastructure. For each environment, you can view:- Kubernetes Clusters: The clusters hosting the environment.
- Deployed Services: The number of services currently deployed in the environment.
- Upcoming Feature: Soon, you’ll be able to add or remove environments directly from this section, making environment management more flexible and intuitive. For now, environments are defined at the service level.
Common Use Cases:
- Development: Used for implementing and testing individual features.
- QA: Dedicated for integration and regression testing.
- Staging: Mimics the production setup closely for final validations.
Environment Page
The Environment Page provides a detailed view of a specific environment, showcasing:Services - Deploy Section
This section lists all services within the environment and provides deployment management features. Below are the key columns and their descriptions:- Name:
- Displays the name of each service.
- Links to more detailed service-specific pages for further inspection.
- Cluster:
- Indicates the Kubernetes cluster running the service.
- Namespace:
- Specifies the namespace in which the service resides within the cluster.
- Location:
- Denotes the physical or logical location of the cluster (e.g.,
us-east1-b
).
- Denotes the physical or logical location of the cluster (e.g.,
- GitHub:
- Linking to the service’s repository or workflow configurations in GitHub.
- Select Version (Git Tag):
- A dropdown to select a specific version or Git tag for deployment.
- GitHub Workflow:
- Links to the deployment workflows associated with the service, providing insights into CI/CD pipelines.
Batch Deployment
- Select multiple services using checkboxes to deploy them simultaneously:
- Choose the desired version for each service from the dropdown.
- Click Deploy to trigger the deployment workflows.
- Monitor the deployment status directly from the page.
Technical Benefits:
- Stability: Static environments offer consistent configurations, reducing variability during testing.
- Predictability: Predefined infrastructure ensures reliable results when testing changes.
- Shared Resources: Efficiently manage team workflows by leveraging shared, persistent environments.
Best Practices for Managing Static Environments
- Clear Environment Definitions: Maintain explicit naming conventions for environments (e.g.,
dev
,qa
,staging
) to avoid confusion. - Environment Health Monitoring: Use monitoring tools to ensure the environment remains stable and performant.