mirror of
https://github.com/puppetmaster/typhoon.git
synced 2024-12-26 08:29: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`
37 lines
820 B
HCL
37 lines
820 B
HCL
output "kubeconfig-admin" {
|
|
value = "${module.bootkube.kubeconfig-admin}"
|
|
}
|
|
|
|
# Outputs for Kubernetes Ingress
|
|
|
|
output "ingress_static_ipv4" {
|
|
value = "${azurerm_public_ip.ingress-ipv4.ip_address}"
|
|
description = "IPv4 address of the load balancer for distributing traffic to Ingress controllers"
|
|
}
|
|
|
|
# Outputs for worker pools
|
|
|
|
output "region" {
|
|
value = "${azurerm_resource_group.cluster.location}"
|
|
}
|
|
|
|
output "resource_group_name" {
|
|
value = "${azurerm_resource_group.cluster.name}"
|
|
}
|
|
|
|
output "subnet_id" {
|
|
value = "${azurerm_subnet.worker.id}"
|
|
}
|
|
|
|
output "security_group_id" {
|
|
value = "${azurerm_network_security_group.worker.id}"
|
|
}
|
|
|
|
output "backend_address_pool_id" {
|
|
value = "${azurerm_lb_backend_address_pool.worker.id}"
|
|
}
|
|
|
|
output "kubeconfig" {
|
|
value = "${module.bootkube.kubeconfig-kubelet}"
|
|
}
|