Configuring Cloud Code settings

Most Cloud Code settings, such as enabling cluster resource completion, opting for YAML formatting and validation, and customizing your Kubeconfig path, can be configured using the Settings menu.

Specifying preferences using VS Code Settings

To configure VS Code Settings, click Manage icon Manage > Settings.

Configuring preferences this way lets you change the defaults that Cloud Code saved when you were first prompted for preferences.

You can use VS Code settings to toggle your preferences around YAML formatting and completion, explorer visibility, telemetry collection, and other Cloud Code options. You can also use it to define an alternative kubeconfig file path, determine a preferred style of prose wrapping, and define criteria for YAML file matching.

Other Cloud Code settings are configurable using your settings.json file.

Working with additional kubeconfig files

By default, Cloud Code uses the default kubeconfig file (located under the '$HOME/.kube' directory) for retrieving Kubernetes resources and running commands.

Importing a new kubeconfig

To import an alternative kubeconfig file into Cloud Code, follow these steps:

  1. Navigate to the Kubernetes Explorer Kubernetes Explorer icon.
  2. Hover over the default config name.
  3. Click Switch kubeconfig icon Switch kubeconfig next to the Default Config and then click select + Load kubeconfig. A file explorer opens.
  4. Select the kubeconfig that you want to import from the file explorer. This switches the active kubeconfig file that Cloud Code uses to the one you just imported.

Tip: If you've imported multiple kubeconfigs, you can easily switch between them by clicking the Switch kubeconfig button and then selecting the kubeconfig you'd like to switch to.

Switching kubeconfigs and then removing a kubeconfig

Removing a kubeconfig

To remove the kubeconfig(s) that you've imported, run the Remove kubeconfig from Cluster Explorer command and select as many configs as you'd like to remove.

Getting Support

To send feedback, report issues on GitHub, or ask a question on Stack Overflow.