Repository navigation
[FEATUTE REQUEST]: Do not require the ITS kubeconfig to be context in the local kubeconfig #25
Description
Currently the plugin expect the target ITS (e.g. its1) to be a context of the specified kubeconfig.
This create a dependency on kflex cli to import the kubeconfig as a context that, in my opinion, is undesirable.
Like we do in multiple initContainers and kubestellar_snapshot.sh, it would be better that the plugin only rely on the knowledge of the kubeconfig where KS core is installed and retrieved the ITS information necessary from the cluster directly without expecting the ITS kubeconfigto be a context of the local kubeconfig.
Activity
clubanderson commentedon Aug 27, 2025
/help-wanted
Om-Beast commentedon Jul 20, 2026
Hi @francostellari,
I'd like to work on this enhancement.
From my understanding, the current plugin depends on the ITS kubeconfig being imported as a local context, which creates an unnecessary dependency on the kflex CLI. Instead, the plugin should be able to rely only on the kubeconfig for the KubeStellar core installation and discover the required ITS connection information directly from the cluster.
My plan is to:
If this issue is still available, I'd be happy to work on it. Please let me know if there are any design considerations or existing implementation discussions that I should review before starting.