On a client machine, the kubectl command-line tool, by default, stores its configuration in the $HOME/.kube directory. This directory contains the config file, which holds sensitive information required to connect to one or more Kubernetes clusters. This information includes cluster API server endpoints, user credentials (such as client certificates and keys or authentication tokens), and context definitions. Access to this directory should be restricted as it grants cluster access.

A. /etc/kubernetes/ is the default directory on control-plane and worker nodes for Kubernetes component configuration files and static Pod manifests, not for client credentials.

C. /opt/kubernetes/secrets/ is not a standard or default directory used by Kubernetes for storing any type of configuration or credential information.

D. $HOME/.config/kubernetes/ is not the default location for kubectl configuration. While some applications follow the XDG Base Directory Specification, kubectl uses $HOME/.kube by default.

1. Kubernetes Documentation

"Organizing Cluster Access Using kubeconfig Files": This official documentation explicitly states

"By default

kubectl looks for a file named config in the $HOME/.kube directory." This file contains the credentials.

Source: Kubernetes Authors

"Organizing Cluster Access Using kubeconfig Files

" Kubernetes Documentation

tasks/access-application-cluster/configure-access-multiple-clusters.html.

2. Kubernetes Documentation

"kubectl Cheat Sheet": The cheat sheet reinforces this by showing commands that interact with the default configuration path. It notes that the KUBECONFIG environment variable can override this default path.

Source: Kubernetes Authors

"kubectl Cheat Sheet

" Kubernetes Documentation

reference/kubectl/cheatsheet.html

Section: "Config & Context".