Thank for this nice introduction to dynamic SA using k8s auth engine. Quick question: Why is the kubernetes provider configured with "insecure" set to "true" ?
In this demo we set the Kubernetes provider attribute: insecure = true so that it ignores the self-signed certificates from the Kubernetes API. In a real world environment we would have configured a valid certificate on the Kubernetes API and configured the Terraform provider to trust this certificate authority. Learn more about the Kubernetes provider here → registry.terraform.io/providers/hashicorp/kubernetes/latest/docs#insecure
Thank for this nice introduction to dynamic SA using k8s auth engine. Quick question: Why is the kubernetes provider configured with "insecure" set to "true" ?
In this demo we set the Kubernetes provider attribute:
insecure = true
so that it ignores the self-signed certificates from the Kubernetes API. In a real world environment we would have configured a valid certificate on the Kubernetes API and configured the Terraform provider to trust this certificate authority. Learn more about the Kubernetes provider here → registry.terraform.io/providers/hashicorp/kubernetes/latest/docs#insecure