mirror of
https://github.com/puppetmaster/typhoon.git
synced 2024-12-26 09:39:34 +01:00
60c70797ec
* Use a single admin kubeconfig for initial bootkube bootstrap and for use by a human admin. Previously, an admin kubeconfig without a named context was used for bootstrap and direct usage with KUBECONFIG=path, while one with a named context was used for `kubectl config use-context` style usage. Confusing. * Provide the admin kubeconfig via `assets/auth/kubeconfig`, `assets/auth/CLUSTER-config`, or output `kubeconfig-admin`
4 lines
78 B
HCL
4 lines
78 B
HCL
output "kubeconfig-admin" {
|
|
value = "${module.bootkube.kubeconfig-admin}"
|
|
}
|