This reference explains how to create local VCF CLI contexts for an existing Supervisor and its VKS workload clusters in VMware Cloud Foundation 9.1.1. Follow the commands to authenticate through the Supervisor API, create the required context, activate it, and verify Kubernetes access.
The DEV and QA procedures use example cluster names and namespaces. Replace the connection details and target names with values for your environment. The accompanying Bash scripts are optional examples of these commands.
Repository: github.com/jmnicolescu/create-vks-context
Access the example Supervisor, DEV, and QA context scripts and their technical documentation in this repository.
vcf) and kubectl, and
make them available in PATH.The commands below use https://192.168.197.31 as the
example Supervisor endpoint and administrator@vsphere.local
as the example SSO username. Complete CLI authentication when prompted.
Do not store real passwords in documentation or committed scripts.
The examples include --insecure-skip-tls-verify for this
lab. This option disables server certificate verification; review your
certificate trust requirements before using it elsewhere.
Use vcf context create <context-name> with the
connection parameters below. The Supervisor API is the entry point for
both Supervisor and workload context creation.
| Parameter | Purpose | Example |
|---|---|---|
<context-name> |
Name assigned to the local VCF CLI context | supervisor or dev-cluster-01 |
--endpoint |
Supervisor API URL used for context creation | https://192.168.197.31 |
--username |
Authorized vSphere SSO identity | administrator@vsphere.local |
--type |
Context type | k8s |
--auth-type |
Authentication method used in these examples | basic |
--workload-cluster-namespace |
Supervisor namespace containing the VKS cluster; used for workload contexts | dev-namespace |
--workload-cluster-name |
Existing VKS cluster to access; used for workload contexts | dev-cluster-01 |
--insecure-skip-tls-verify |
Disable server certificate verification for the lab connection | Flag with no value |
The examples use the following names:
| Target | Supervisor namespace | Context created | Context activated |
|---|---|---|---|
| Supervisor | Not specified | supervisor |
supervisor |
| DEV | dev-namespace |
dev-cluster-01 |
dev-cluster-01:dev-cluster-01 |
| QA | qa-namespace |
qa-cluster-02 |
qa-cluster-02:qa-cluster-02 |
For the workload examples, the activation name combines the local
context name and workload cluster name as
<context-name>:<cluster-name>. Use
vcf context list --wide to inspect the available
contexts.
Create a context for the Supervisor API:
vcf context create supervisor \
--endpoint https://192.168.197.31 \
--username administrator@vsphere.local \
--insecure-skip-tls-verify \
--type k8s \
--auth-type basicAfter creation succeeds, activate the context and check the selection:
vcf context use supervisor
vcf context list
kubectl config current-contextConfirm that the active Kubernetes context is supervisor
before continuing. Check the target API server and query its nodes:
kubectl config view --minify -o jsonpath='{.clusters[0].cluster.server}{"\n"}'
kubectl get nodesVerify that the API server belongs to the intended target and inspect node readiness. If creation or activation fails, resolve the error before proceeding; an earlier context may still be active.
Create a context for dev-cluster-01 in the Supervisor
namespace dev-namespace:
vcf context create dev-cluster-01 \
--endpoint https://192.168.197.31 \
--username administrator@vsphere.local \
--workload-cluster-namespace dev-namespace \
--workload-cluster-name dev-cluster-01 \
--insecure-skip-tls-verify \
--type k8s \
--auth-type basicThe argument definitions below follow the VCF CLI context command reference.
| Argument in this example | Explanation |
|---|---|
dev-cluster-01 after
vcf context create |
Names the local VCF CLI context. This positional argument labels the connection configuration. |
--endpoint https://192.168.197.31 |
Specifies the Supervisor API URL used to establish the connection. Supply your Supervisor address here. |
--username administrator@vsphere.local |
Supplies the login identity for the Kubernetes context. This example uses a vSphere SSO account. |
--workload-cluster-namespace dev-namespace |
Selects the Supervisor namespace that contains the existing workload cluster. |
--workload-cluster-name dev-cluster-01 |
Selects the existing VKS workload cluster within that namespace. This value identifies the cluster; the positional argument above names the local context. |
--insecure-skip-tls-verify |
Bypasses endpoint TLS certificate verification. This Boolean flag takes no value and is included for the lab configuration. |
--type k8s |
Explicitly selects a Kubernetes context. The reference lists this
flag as optional; k8s is the short form of
kubernetes. |
--auth-type basic |
Explicitly selects basic authentication instead of leaving authentication type detection to the CLI. |
For this SSO workflow, --auth-type basic directs
authentication to vCenter SSO identity sources, bypassing the VCF
Automation identity-provider flow described in Broadcom KB
417617.
Complete the credential prompt when requested; --username
supplies only the account name.
The VCF CLI Quick Start
Guide
separates context creation from activation and describes the vCenter SSO
credential prompt on the first vcf context use.
Each trailing \ continues the same Bash command onto the
next line. Keep it as the last character on the line; comments after it
would break command continuation.
After creation succeeds, activate the context and check the selection:
vcf context use dev-cluster-01:dev-cluster-01
vcf context list
kubectl config current-contextConfirm that the active Kubernetes context is
dev-cluster-01:dev-cluster-01 before continuing. Check the
target API server and query its nodes:
kubectl config view --minify -o jsonpath='{.clusters[0].cluster.server}{"\n"}'
kubectl get nodesVerify that the API server belongs to the intended target and inspect node readiness. If creation or activation fails, resolve the error before proceeding; an earlier context may still be active.
Create a context for qa-cluster-02 in the Supervisor
namespace qa-namespace:
vcf context create qa-cluster-02 \
--endpoint https://192.168.197.31 \
--username administrator@vsphere.local \
--workload-cluster-namespace qa-namespace \
--workload-cluster-name qa-cluster-02 \
--insecure-skip-tls-verify \
--type k8s \
--auth-type basicAfter creation succeeds, activate the context and check the selection:
vcf context use qa-cluster-02:qa-cluster-02
vcf context list
kubectl config current-contextConfirm that the active Kubernetes context is
qa-cluster-02:qa-cluster-02 before continuing. Check the
target API server and query its nodes:
kubectl config view --minify -o jsonpath='{.clusters[0].cluster.server}{"\n"}'
kubectl get nodesVerify that the API server belongs to the intended target and inspect node readiness. If creation or activation fails, resolve the error before proceeding; an earlier context may still be active.
List available contexts:
vcf context list --wideRun the activation command for the target you want to use:
| Target | Activation command |
|---|---|
| Supervisor | vcf context use supervisor |
| DEV | vcf context use dev-cluster-01:dev-cluster-01 |
| QA | vcf context use qa-cluster-02:qa-cluster-02 |
Confirm the active Kubernetes context before running commands against the cluster:
kubectl config current-contextOnce the selection matches the intended target, verify access:
kubectl get nodesIf a context already exists and its connection settings are correct, activate it using the commands above. To replace a local context, delete its VCF context name and repeat the corresponding creation and verification procedure.
For example, to replace the DEV context:
vcf context delete dev-cluster-01 -yThen follow Create the DEV VKS cluster context. The deletion
command removes the named local context without confirmation; it does
not delete the VKS cluster. Use supervisor or
qa-cluster-02 when replacing those example contexts.
Kubernetes access uses local kubeconfig connection and authentication
settings. Inspect the active context with
kubectl config current-context and its API server with the
verification commands above. If you use a custom kubeconfig setup,
confirm which configuration is active.
Protect kubeconfig files and authentication material. A successful context creation command establishes connection configuration; verify the active target and node access separately.
| Symptom | Check and next action |
|---|---|
vcf or kubectl is missing |
Install the executable or correct PATH. |
| Supervisor endpoint is unreachable | Restore lab/VPN access and verify the --endpoint
value. |
| Authentication fails | Confirm the SSO username, credentials, and access permissions, then complete CLI authentication. |
| Workload context cannot be created | Verify the workload cluster name, Supervisor namespace, permissions, and cluster availability. |
| Plugin discovery or download fails | Inspect the CLI error and network access. Verify context selection and Kubernetes access separately. |
| Nodes are returned for an unexpected cluster | Inspect kubectl config current-context and the selected
API server; an earlier context may remain active after a failure. |
Node query returns Forbidden |
Check Kubernetes access permissions for the selected identity and target. |
| Context deletion succeeded but recreation failed | Correct the connection or authentication error, then repeat the relevant creation procedure. |
The GitHub repository includes three optional Bash examples that automate context deletion, creation, activation, context listing, and a node query.
| Example script | Target |
|---|---|
| 01-create-supervisor-context.sh | Supervisor context supervisor |
| 02-create-dev-cluster-01-context.sh | dev-cluster-01 in dev-namespace |
| 03-create-qa-cluster-02-context.sh | qa-cluster-02 in qa-namespace |
To use an example, review the direct assignments near the top of that script: Supervisor endpoint, SSO username, context name, and any workload cluster name and namespace. Each script has its own settings. The local password assignment is neither explicitly exported nor passed as a CLI argument; complete authentication when prompted.
From the repository directory, run only the example for your intended target:
bash ./01-create-supervisor-context.shFor DEV, use bash ./02-create-dev-cluster-01-context.sh.
For QA, use bash ./03-create-qa-cluster-02-context.sh.
Each example deletes and recreates its named local context. Strict error handling is commented out, and the final success message is unconditional. Inspect command errors and verify the active context and node access using the procedures in this reference.