Open spam-n-eggs opened 3 years ago
Same thing when supplying a non-existing config_path
instead (eg. generated by Terraform).
Looks like this provider doesn't wait for any of the data to be available, unlike the kubernetes
provider?
I've the same issue. The only way you can bypass this issue atm. is to deploy the cluster first.
Or im doing it also wrong 😂
Same issue here, I'm using the terraform-aws-modules
which works well with the official kubernetes
when following the recommended provider setup:
provider "kubernetes" {
host = data.aws_eks_cluster.cluster.endpoint
cluster_ca_certificate = base64decode(data.aws_eks_cluster.cluster.certificate_authority.0.data)
token = data.aws_eks_cluster_auth.cluster.token
load_config_file = false
}
This doesn't work with kubernetes-alpha
though.
Terraform, Provider, Kubernetes versions
Affected Resource(s)
Terraform Configuration Files
Debug Output
https://gist.github.com/spam-n-eggs/0ccefde28ea8de7249619f13d57c8314
Panic Output
Steps to Reproduce
terraform plan
Expected Behavior
What should have happened? A plan should have been produced
Actual Behavior
What actually happened? The error message is returned:
Important Factoids
Running on Alpine Linux v3.13
References
Community Note