-
Notifications
You must be signed in to change notification settings - Fork 40k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix kubeconfig serialization #6476
fix kubeconfig serialization #6476
Conversation
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project, in which case you'll need to sign a Contributor License Agreement (CLA). 📝 Please visit https://cla.developers.google.com/ to sign. Once you've signed, please reply here (e.g.
|
LGTM, provided e2e is passing. It's unfortunate that this makes |
2298a2b
to
06c9dbd
Compare
Rebased to get vagrant e2e working again. I got most of them passing on vagrant. I get the same success/failures on master against vagrant.
|
Partially addresses #5625.
This updates
kubectl config view
to produce the output based on the serialization format instead of the in memory copy.I attempted to do this before, but I failed to handle the different templates that already existed and that resulted in e2e failures. This time I've update the templates in the scripts (see the
update scripts with correct templates
commit). I'm running e2e now, but the individual formats were equivalent when I tested them. See https://gist.github.com/deads2k/c294a882c9358ea7679f for how I located them and what the equivalence was.