Web SSH Access

Web SSH provides a CLI environment for cluster access through a web browser. Therefore, you can utilize the installed cluster without needing to set up a separate local environment.

Web SSH, which is specialized for clusters, has different characteristics from a local environment and requires important usage considerations. Please check the Web SSH Features section below.

Web SSH Connection

First, connect to the remote shell in the same way as a standard SSH connection.

To establish a connection:

1. Select DevOps > Web SSH from the side menu.
2. Select Namespace at the top of the content area.
3. Choose the Shell type and click the Connect button.
4. Once the connection is complete, a prompt will appear along with the following message.

Using Web SSH

Web SSH connects with the necessary commands and configurations pre-set for cluster usage.

Below is an example of querying resources using kubectl and helm.

Here is a list of installed commands:

Relationship with Kubernetes Permissions

Kubernetes has permission settings for resource creation, retrieval, modification, and deletion, which may restrict resource access and kubectl usage.
In ZCP, Kubernetes permissions can be granted or revoked through the Console's user/namespace management function,
and permission errors may occur while using related features.

If you encounter permission issues, check the user/namespace permission settings or contact the Cluster Admin.

Web SSH Features

Web SSH is created as a Kubernetes Pod and connects via WebSocket.

Thus, it has the following characteristics:

• A different Pod is created for each namespace.
• A different Pod is created for each user.
• The Pod is created upon the initial connection and is connected once the setup is complete. As long as the Pod is maintained, reconnection occurs without delay.
• The Pod is deleted when all connections are closed.
• No separate disk is attached. When the Pod is deleted, all internal files are erased due to container characteristics.