Skip to main content

WebSSH Console

WebSSH Console Overview

The WebSSH Console allows you to access your deployment's namespace in Kubernetes via a secure, browser-based terminal. This is especially helpful for:

  • Advanced debugging
  • Running custom kubectl commands
  • Inspecting resource configurations beyond what the dashboard provides

When you click "Start WebSSH", the system automatically creates a temporary pod inside your deploymentโ€™s namespace. This pod includes:

  • โœ… kubectl (pre-configured for your namespace)
  • โœ… All necessary credentials and tools for CLI access

Start WebSSH + Credentials

Each user gets their own isolated CLI session. A unique link, username, and password are generated when you start WebSSH.
If another user wants to access the CLI, they must also click Start WebSSH to create their own session.

To simplify access, just click the "Open WebSSH Console" button โ€” this auto-fills your credentials and launches the terminal in a new tab.

WebSSH Browser Terminal

Auto Login View
๐Ÿ“ธ WebSSH terminal window opened in browser with CLI access

โš ๏ธ Note: You will only have access to your assigned namespace. You cannot read or modify resources in other namespaces.

Namespace Restriction Info

If your WebSSH pod is not responding properly, you can either click "Restart", or stop it and start again to refresh the session.

Restart WebSSH Pod

๐Ÿ› ๏ธ What You Can Do with WebSSHโ€‹

  • View and debug advanced pod configurations
  • Run commands like kubectl get, kubectl describe, or kubectl exec
  • Access real-time logs beyond what's shown in the UI
  • Apply quick fixes or test configurations directly from the CLI

โš ๏ธ Note: Use WebSSH mainly for viewing and troubleshooting.
Avoid making changes directly with kubectl, as those changes may not sync with the Unifie database.

๐Ÿ›‘ Importantโ€‹

When you're done, click the "Stop" button to delete your WebSSH pod.
The CLI pod is temporary and should be cleaned up to avoid unnecessary resource usage.

Stop WebSSH Pod