You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if a v-cluster is installed via helm, there is only one kubeconfig secret created: the one for access via localhost and port-forwarding.
(Optionally a secret can be created for the exposed access via Ingress / Loadbalancer service.)
A secret which is not created, is the one for access from host: https://www.vcluster.com/docs/using-vclusters/access#from-host-cluster
Which solution do you suggest?
Create the secret similar to the one for "localhost access". No extra helm value is required.
Which alternative solutions exist?
No response
Additional context
We need this feature to allow creating vclusters with "full gitops approach" (e.g. with flux).
This should work without usage of the vcluster command line tool.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
Currently if a v-cluster is installed via helm, there is only one kubeconfig secret created: the one for access via localhost and port-forwarding.
(Optionally a secret can be created for the exposed access via Ingress / Loadbalancer service.)
A secret which is not created, is the one for access from host: https://www.vcluster.com/docs/using-vclusters/access#from-host-cluster
Which solution do you suggest?
Create the secret similar to the one for "localhost access". No extra helm value is required.
Which alternative solutions exist?
No response
Additional context
We need this feature to allow creating vclusters with "full gitops approach" (e.g. with flux).
This should work without usage of the vcluster command line tool.
The text was updated successfully, but these errors were encountered: