Accessing Kubectl Shell
Platformer Console has a Kubernetes Shell enabled, which let’s you run commands on your cluster even if your cluster is inside a private network. This is ensured by the functionality behind the Platformer Agent that will be running inside your cluster when you Connect a Kubernernetes Cluster to the Console.
In Platformer, All the users are synced with a Service Account that is created for each user in the cluster. The permissions for the service account are determined by the access set in the Platformer Console. When a user requests a Shell session in the cluster, Platformer Agent will automatically create a session shell container for the user binding the service account of that user.
If the user has Cluster Admin rights defined in Platformer console, the user has full access to the cluster resources inside the kubectl shell.
Platformer Shell has the following tools bundled within it.
- Helm 3
Because Platformer Kubernetes Shell always runs inside the server, you can use Platformer Kubernetes shell to debug in-cluster network issues and dns issues.
Before you begin¶
- Ensure that you have a cluster connected at Platformer Console. Read more on Cluster Connection here
- Go to Clusters at Platformer Console
Make sure your cluster is Active and navigate into the cluster.
If the cluster is not at Active state, Please refer Kubernetes agent troubleshooting
Press Open Kubectl Shell to open the shell.
Shell may take upto 1-2 minutes to provision on the first go.
Once connected, You should be able to run your desired commands on the shell.
This section will be updated soon