Closed developer-guy closed 2 years ago
@developer-guy thanks for creating this issue! We already have a flag for this called --update-current
, so you could run:
KUBECONFIG=my-config.yaml vcluster connect ... --update-current
Or is this not what you want?
@developer-guy thanks for creating this issue! We already have a flag for this called
--update-current
, so you could run:KUBECONFIG=my-config.yaml vcluster connect ... --update-current
Or is this not what you want?
Exactly, sorry I didnt see this flag, thank you, Im closing this one
Wouldn't it be nice to add support of merging if the
kubeconfig.yaml
file already exists instead of overriding it? Because in some cases, like avoiding connection issues while forwarding port to local port, I might prefer to change the service type from ClusterIP to NodePort or I can already have itkubeconfig.yaml
; in such cases, I might want to edit the existingkubeconfig.yaml
file, so when I runconnect
again, all my changes were lost.cc: @dentrax @erkanzileli