Environments

Shows all the environments in which the service is deployed, including the cluster name, namespace, ingress status, etc. This page also allows you to create new environments to deploy your service over.

​

Environment Fields

For every environment, KoalaOps displays the fields below.

​

Cluster

The Cluster field identifies the Kubernetes cluster associated with the environment. Clusters are collections of nodes that run containerized applications.

​

Namespace

Kubernetes Namespace provides a mechanism for isolating groups of resources within a single cluster.

​

Ingress Enabled

The Ingress Enabled field indicates whether an Ingress resource has been configured for the environment. Ingress manages external access to the services in a cluster, typically HTTP.

​

Auto Deploy

Auto Deploy specifies whether the deployment of updates to the environment is automated on commit.

​

Live Deployment

The Live Deployment field names the current deployment within the environment.

​

Image

The Image field specifies the container image used in the deployment, including the name and tag of the image.

​

Strategy

Strategy defines the deployment strategy used when updating applications within the environment. Common strategies include RollingUpdate.

​

Creation Time

The Creation Time field records when the environment or resource was initially created.

​

Last Update

Last Update indicates the most recent update to the environment or resource.

​

Number of Pods

This field shows the Number of Pods currently running within the environment.

​

Pod Details

• Pod Name and Status: Lists each pod’s name and its current status, such as Running.

​

Last Applied YAML

The Last Applied YAML field provides the YAML configuration most recently applied to the environment, offering insights into the current configuration state.

​

Port Forwarding

Port Forwarding instructions are provided for accessing services within the environment directly from a local machine.

​

Run Profiling

This section includes commands for profiling applications running within the environment, useful for performance analysis.

​

SSH into Pod

Instructions for accessing a shell inside a pod via SSH, allowing for direct interaction with the running environment for troubleshooting or maintenance purposes.

​

Editing Environment Configurations

For each Kubernetes service environment, certain fields can be updated to reflect changes in configuration, requirements, or deployments. This section outlines the fields available for editing in the environment edit dialogue and provides guidance on how to modify them.

To edit an environment’s configuration, navigate to the environment you wish to modify and select the “Edit” icon. This will open the edit dialogue, where the following fields can be updated:

​

General Settings

• Environment Name: This field allows you to update the name of the environment. The environment name is a human-readable identifier used to reference the environment within the portal.

• Kubernetes Namespace: The Kubernetes namespace associated with this environment can be changed here. Namespaces are used to isolate environments within the cluster.

​

Auto Deploy

• Auto Deploy: Toggle the auto deploy feature on or off. When enabled, updates to this environment are automatically deployed, integrating seamlessly with CI/CD pipelines.

​

Ingress Settings

• Enable Ingress: This switch allows you to enable or disable the Ingress for the environment. Ingress controls the external access to the services in the cluster, typically HTTP or HTTPS access.

• Ingress Host: If Ingress is enabled, you can specify an ingress host. By default, the system generates a host name based on the environment and cluster configuration. This field allows for an optional override if a custom host name is required.

​

Saving Changes

After making the necessary edits, click the “Save” button, and a Pull Request will be created for you to approve. It’s advisable to review the environment’s status and functionality after editing to ensure all services are operating as expected.