mirror of
https://github.com/puppetmaster/typhoon.git
synced 2024-12-26 05:19:32 +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`
39 lines
1009 B
HCL
39 lines
1009 B
HCL
output "kubeconfig-admin" {
|
|
value = "${module.bootkube.kubeconfig-admin}"
|
|
}
|
|
|
|
# Outputs for Kubernetes Ingress
|
|
|
|
output "ingress_static_ipv4" {
|
|
description = "Global IPv4 address for proxy load balancing to the nearest Ingress controller"
|
|
value = "${google_compute_global_address.ingress-ipv4.address}"
|
|
}
|
|
|
|
output "ingress_static_ipv6" {
|
|
description = "Global IPv6 address for proxy load balancing to the nearest Ingress controller"
|
|
value = "${google_compute_global_address.ingress-ipv6.address}"
|
|
}
|
|
|
|
# Outputs for worker pools
|
|
|
|
output "network_name" {
|
|
value = "${google_compute_network.network.name}"
|
|
}
|
|
|
|
output "kubeconfig" {
|
|
value = "${module.bootkube.kubeconfig-kubelet}"
|
|
}
|
|
|
|
# Outputs for custom firewalling
|
|
|
|
output "network_self_link" {
|
|
value = "${google_compute_network.network.self_link}"
|
|
}
|
|
|
|
# Outputs for custom load balancing
|
|
|
|
output "worker_instance_group" {
|
|
description = "Full URL of the worker managed instance group"
|
|
value = "${module.workers.instance_group}"
|
|
}
|