NRP Cluster Access via kubectl

Install kubectl

Install the Kubernetes command-line tool, kubectl from the official instructions of each OS.

Install the kubelogin plugin, or kubeconfig file will not work.
Once installed, move kubelogin from `/usr/local/bin` to `~/.local/bin` (create the directory when nonexistent) if it does not exist on `~/.local/bin`. Set `export PATH=”~/.local/bin:${PATH}”` for local user


sudo mv ./kubelogin /usr/local/bin/kubectl-oidc_login
sudo chown root: /usr/local/bin/kubectl-oidc_login

Save the config file as config (without any extension) and put it in your $HOME/.kube folder.
This folder may not exist on your machine. Create the .kube folder first on your home folder.

Run the command “kubectl config get-contexts” to list available Kubernetes contexts.
If you have access to multiple Kubernetes clusters, you need to choose use-context nautilus by “kubectl config use-context nautilus”


$ kubectl config get-contexts
CURRENT   NAME       CLUSTER    AUTHINFO   NAMESPACE
*         nautilus   nautilus   oidc

Verify cluster access using kubectl. Run the “kubectl get pods -n <YOUR_NAMESPACE>” command on your terminal
If you see the message “No resources found in your namespace” it means there are no pods in your namespace yet. This indicates that you have access to the resources of your namespace.

If you know you’re a member of a namespace, you can set it as default.

kubectl config set contexts.nautilus.namespace YOUR_NAMESPACE

2. NRP Office Hours time available in NRP Website