Kubernetes, the open source container orchestration system, has gained a lot of traction in the past few years. It’s now one of the most popular ways to deploy and manage large-scale applications. While Kubernetes is a powerful tool, it can be daunting for beginners to get started. In this post, you’ll learn how the kubectl command can be used to manage your Kubernetes contexts, making it easier for you.

#Kubectl Series

• Kubectl Rollout Restart: 3 Ways to Use It
• Kubectl Get Context: Its Uses and How to Get Started
• Kubectl Get Nodes: Why and How to Use It
• Kubectl Proxy: When and How to Use it to Access the Kubernetes API
• Kubectl Patch: What You Can Use It for and How to Do It
• How to Restart Pods in Kubectl: A Tutorial With Examples
• Kubectl Login: Solving Authentication For Kubernetes
• Kubectl Exec: Everything You Need to Know
• Installing and Managing kubectl Plugins with Krew

#What Is Kubectl Config?

The kubectl utility is a command line interface (CLI) for interacting with Kubernetes. You can use it to manage Kubernetes resources such as pods, services, and deployments. To install kubectl, you simply need the run the commands as per the installation guide.

If you’re new to Kubernetes, the following resources can help you learn about the platform and how to get started. The Kubernetes documentation is a comprehensive resource that covers all aspects of Kubernetes. It includes conceptual guides, installation instructions, and usage examples.

The kubectl config file is a configuration file that stores all the information necessary to interact with a Kubernetes cluster. It contains the following information:

• The name of the Kubernetes cluster
• The location of the Kubernetes API server
• The credentials (username and password) for authenticating with the Kubernetes API server
• The names of all contexts defined in the cluster

In the next sections, we’ll focus on one particular use case of the kubectl command: managing Kubernetes contexts.

#Viewing the Kubernetes Configuration

To view the config file, you can use the following command:

$ kubectl config view

The output of this command is shown below.

Figure: The output of kubectl config view command

As you can see, this Kubernetes config file contains information about the clusters, contexts, and users that kubectl can access.

• The apiVersion defines the version of the config file.
• The clusters section contains information about the Kubernetes clusters that kubectl can access.
• The contexts section contains information about the contexts that kubectl can access.
• The current-context field specifies the context that kubectl is currently using.
• The users section contains information about the users that kubectl can access.

A Kubernetes context is a group of access parameters that define which cluster you’re interacting with, which user you’re using, and which namespace you’re working in. It’s helpful if you need to access different clusters for different purposes or if you want to limit your access to certain parts of a cluster. For example, if you have multiple Kubernetes clusters, each with its own set of users and permissions, you can use kubectl config use-context to switch between them.

#How To Use Kubernetes Contexts

The kubectl config get-contexts is a command that retrieves information about the current Kubernetes context. This command is part of the kubectl utility, which interacts with Kubernetes clusters. When you first install Kubernetes, a default context is created for you. This context points to a local Kubernetes cluster running on your development machine. If you want to work with multiple Kubernetes clusters, you can create additional contexts.

#Finding the Current Context in Kubectl

To find the current context, you can simply run the following command:

$ kubectl config current-context

It will print the name of the current context in kubectl. The screenshot below shows the output.

Figure: The output of kubectl config current-context command

You can switch between these contexts by using the kubectl config use-context command. You can create additional contexts if you want to work with multiple Kubernetes clusters. For example, you might have a context for each of the following:

• Your local Kubernetes cluster
• A staging Kubernetes cluster
• A production Kubernetes cluster

Let’s look at some of the most common uses for this command.

#Listing Kubernetes Contexts

As I mentioned above, the kubectl config get-contexts command can be used to list all of the available Kubernetes contexts. To do this, simply run the following command in the terminal window:

$ kubectl config get-contexts

It will print out a list of all the available contexts in your Kubernetes configuration as well as the currently active context. By default, the active context is marked with an asterisk.

Figure: The output of kubectl config get-contexts command

By default, Kubernetes uses the default context. However, you can create and use multiple contexts if you have multiple Kubernetes clusters.

#Viewing Kubernetes Context Information

In addition to listing the available contexts, the kubectl get context command can also be used to view information about a specific context. To do this, simply specify the name of the context you want to view:

kubectl get context staging

Replace <contextname> with the name of the context you want to switch to. For example, if you’re going to switch to the _staging context, you would type the following:

kubectl get context staging

It will print out information such as the cluster name, username of the author or creator, and namespace for the specified context.

Figure: The output of the kubectl config get-contexts command

#Creating a new Context

The kubectl config set-context command is used to create a new context in a kubeconfig file.

kubectl config set-context <context-name> --namespace=<namespace-name> --user=<user-name> --cluster=<cluster-name>

Here <context-name> is the new context you want to create, <namespace-name> is the namespace that this context should point to, <user-name> is the user that you want to authenticate as, and <cluster-name> is the name of the Kubernetes cluster.

For example, the following command will create a new context named staging that points to a staging Kubernetes cluster:

$ kubectl config set-context staging --cluster=staging --namespace=staging --user=staging-admin

The output of the above command is shown below:

Figure: The output of kubectl config set-context command

You can verify the creation of this new context by listing the contexts using the kubectl config get-contexts command discussed in the previous section. The kubectl set-context can also be used to modify an existing context.

#Switching Kubernetes Contexts

If you want to switch to a different Kubernetes context, you can use the kubectl config use-context command below.

kubectl config use-context <context-name>

Here <context-name> is the name of the context that you want to switch to. It will change your active Kubernetes context to the one you specified. You can verify that the context has been changed by running the kubectl get current-context command without any arguments.

Figure: The output of the kubectl config use-context command

As you can see, the command above switched the current context to a context named staging. You can verify this by running the kubectl config current-context as in the above screenshot.

#Best Practices When Using ‘kubectl config set-context’

Switching between contexts is common when working with Kubernetes. You can set aliases for your most frequently used contexts to make it easier. For example, you could define an alias in your ~/.bashrc file or your shell configuration file as shown below.

alias k8s-prod='kubectl config use-context production'

This is a simple way to shorten the command you would use to switch to the production context. After that, instead of typing the complete command, you can just type in the command k8s-prod to switch to the production context.

#Deleting a Kubernetes Context

The kubectl delete context command is used to delete an existing context from a kubeconfig file. This command has the following syntax:

kubectl config delete-context <context-name>

Here is the name of the context that you want to delete.

For example:

kubectl config delete-context demo

The above command will delete the context named demo from the current Kubernetes configuration. The below screenshot shows the output.

Figure: The output of kubectl config delete-context command

#Conclusion

In this article, we covered the kubectl command line tool. We started by showing you the kubectl config get-contexts command. This command is used to list and view Kubernetes contexts. Next, we looked at the kubectl config set-context command. This command allows you to switch between Kubernetes contexts. Next, we looked at the kubectl config create-context command. This command allows you to create custom contexts in your kubeconfig file. Finally, we looked at how to delete a context using the kubectl config delete-context command.

As you can see, the kubectl command is a versatile tool that can be used in many ways. Whether you’re looking to list, view, or switch between Kubernetes contexts, this command has you covered. To get the complete list of options for this command, take a look at the official reference for this tool and start using it today!

#Next Step : How to Access the vCluster KubeConfig

This post was written by Tarun Telang. Tarun is a software engineering leader with over 16 years of experience in the software industry with some of the world’s most renowned software development firms like Microsoft, Oracle, BlackBerry, and SAP. His areas of expertise include Java, web, mobile, and cloud. He’s also experienced in managing software projects using Agile and Test Driven Development methodologies.