Web SSH Access (Cluster Admin)

Web SSH provides a CLI environment for cluster access via a web browser. Therefore, there is no need to configure a separate local environment, as the installed cluster can be utilized.

Web SSH, which is specialized for clusters, has different characteristics from a local environment and requires precautions when used. Please check the Web SSH Characteristics section below.

Web SSH Connection

First, connect to the remote shell just like standard SSH. 

To establish a connection:

1. Select DevOps > Web SSH from the side menu.
2. Select the 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 be displayed along with the following message.

Web SSH Utilization

Web SSH connects with commands and settings pre-configured for cluster utilization.

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

Below is a list of installed commands.

Relationship with Kubernetes Permissions

Kubernetes has permission settings for creating, retrieving, modifying, and deleting resources, which may restrict resource access and kubectl usage.
In ZCP, Kubernetes permissions can be granted or revoked through the Console's user/namespace management functions.
Permission errors may occur while using related functions.

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

Web SSH Characteristics

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

Therefore, it has the following characteristics:

• A separate Pod is created for each namespace.
• A separate Pod is created for each user.
• A Pod is created upon the initial connection and remains active. As long as the Pod persists, reconnection occurs without delay.
• When all connections are terminated, the Pod is deleted.
• No separate disk is attached. When the Pod is deleted, all internal files are permanently deleted due to container characteristics.