After bootstrapping with kubeadm we create a kubeconfig for
an additional user via kubeadm alpha kubeconfig. However there
is validation logic which prevents us from using a CNAME for
the API server's advertised address, despite being able to
do this when using kubeadm init.
This workaround simply uses sed to swap out the server location
so that the user has a more robust config without having to
manually change it.
After bootstrapping with kubeadm we create a kubeconfig for an additional user via
kubeadm alpha kubeconfig. However there is validation logic which prevents us from using a CNAME for the API server's advertised address, despite being able to do this when usingkubeadm init.This workaround simply uses sed to swap out the server location so that the user has a more robust config without having to manually change it.
Fixes #235
Signed-off-by: John Schnake jschnake@vmware.com