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
I use a proxy-url flag in my kubeconfig which was introduced in v1.19 of Kubectl (kubernetes/client-go#351) since we access the cluster via a Bastion host. Now the problem is that, if I add the proxy-url flag in the config and run kubeseal, the proxy-url flag gets removed from the kubeconfig which is very inconvenient since this requires to use the environment export HTTP_PROXY logic to have a working version of kubeseal. After running that you have to set the proxy-url again to have other tooling working again.
Reproduction steps:
Add a proxy-url flag to kubeconfig for accessing the cluster via bastion
-- manually in file before server : proxy-url: http://localhost:8888
-- via kubectl : kubectl config set clusters.<name>.proxy-url "http://localhost:8888"
Run kubeseal without any input
see that proxy-url flag disappeared from the config
I can't seem to find a way to use my kubeconfig without it being tainted by the kubeseal command.
Versions used:
kubeseal version : v0.16.0
kubectl version : v1.19.7
The text was updated successfully, but these errors were encountered:
Hello,
I use a proxy-url flag in my kubeconfig which was introduced in v1.19 of Kubectl (kubernetes/client-go#351) since we access the cluster via a Bastion host. Now the problem is that, if I add the proxy-url flag in the config and run kubeseal, the proxy-url flag gets removed from the kubeconfig which is very inconvenient since this requires to use the environment export HTTP_PROXY logic to have a working version of kubeseal. After running that you have to set the proxy-url again to have other tooling working again.
Reproduction steps:
-- manually in file before
server
:proxy-url: http://localhost:8888
-- via kubectl :
kubectl config set clusters.<name>.proxy-url "http://localhost:8888"
kubeseal
without any inputI can't seem to find a way to use my kubeconfig without it being tainted by the
kubeseal
command.Versions used:
The text was updated successfully, but these errors were encountered: