Sign in Subscribe
Concepts

K9s SSH Access Proxy

Andrios Robert

• 1 min read

The console blinks. You need access. The cluster sits behind an SSH gateway, guarded and unreachable—until you route through a proxy.

K9s SSH Access Proxy solves that exact problem. K9s is already the fastest way to interact with a Kubernetes cluster from the terminal. Add SSH access proxying, and you can securely tunnel into remote clusters without breaking workflow or opening risky ports.

Why K9s SSH Access Proxy Matters

Most production clusters hide behind bastion hosts or jump boxes. Direct access is blocked. Without a proxy, every command requires manual SSH port forwarding or custom scripts. These approaches break flow, are error-prone, and create security gaps. K9s integrates SSH proxy support, letting you authenticate once, then navigate and manage Kubernetes resources as if you were local.

Core Features

  • Native SSH Proxy Support: Connect to clusters behind an SSH gateway with minimal configuration.
  • Seamless kubeconfig Integration: Point K9s to the right context; the proxy handles the rest.
  • Secure Session Management: Reduce exposure by closing proxy sessions instantly when done.
  • Consistent Command Layer: All K9s commands work over the SSH proxy without modification.

How It Works

The K9s SSH Access Proxy uses your SSH credentials to negotiate a secure tunnel. Once the handshake completes, requests to the Kubernetes API are routed through the proxy. Your kubeconfig context aligns with the tunneled endpoint, so K9s commands execute as though you were inside the private network. The flow is clean, robust, and repeatable.

Setup Steps

  1. Ensure you have SSH access to the bastion host that can reach the Kubernetes API server.
  2. Configure your kubeconfig to use the SSH proxy for the target cluster.
  3. Launch K9s with the desired context.
  4. Verify the connection through :info in K9s to confirm the proxy is active.

This eliminates the need for external port-forwarding commands, custom networking hacks, or switching tools mid-task.

Best Practices

  • Use dedicated SSH keys with restricted permissions for proxy access.
  • Close sessions immediately after use.
  • Keep proxy configuration under version control but store keys outside repos.
  • Audit SSH access logs regularly.

A solid SSH access proxy unlocks secure, low-friction control over remote Kubernetes clusters. K9s brings that capability straight into your operative toolchain.

Ready to see it run with zero drama? Spin up a live K9s SSH Access Proxy in minutes at hoop.dev.