What context to use?

[stianmathisen]

Hello, we are currently building a multi cluster platform where we have a bare metal kubernetes cluster functioning as the the host cluster with kubevirt and hosted control planes. We are using argocd to deploy system application and services, and plan to use the same argocd to deploy system services in the child cluster deployed on top of the same infrastructure cluster, using the hub and spoke model.

When we attempt to run clusteradm init --wait --context ${CTX_HUB_CLUSTER}, we get the error Error: context "PATH/TO/KUBECONFIG" does not exist, I understand OCM might need a different context to run, but I can't find any information in the getting started section!

Any input appreciated.

[dosubot]

Hi @stianmathisen! I'm Dosu and I’m helping the ocm team.

The --context flag in clusteradm expects the name of a Kubernetes context from your kubeconfig, not a file path. The error you’re seeing means the value you passed (likely "PATH/TO/KUBECONFIG") isn’t a context name in your kubeconfig file.

To fix this, run kubectl config get-contexts --kubeconfig to list available context names. Set CTX_HUB_CLUSTER to the context name that points to your hub (host) cluster, then run clusteradm init --wait --context ${CTX_HUB_CLUSTER} again.

You can also set the KUBECONFIG environment variable to your kubeconfig file path and omit --context if you want to use the current context. More details and examples are in the official docs: see here.

If you’re running in hosted mode, use the hosting cluster’s context for --context, and provide the managed cluster’s kubeconfig with --managed-cluster-kubeconfig as needed reference.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[qiujian16]

I think you will need to check your kubeconfig file, CTX_HUB_CLUSTER actually means a context in the kubeconfig that points to the the cluster to deploy the hub control plane of ocm.