Open bitsofinfo opened 1 year ago
Getting this on apply as well. Doing research to see if it's related to https://support.hashicorp.com/hc/en-us/articles/4408936406803-Kubernetes-Provider-block-fails-with-connect-connection-refused-
I don't think though since the initial apply works fine and creates resources, just the state refresh fails 🤔
Getting the same issue here. It works normally and after some time it starting retrieving the same issue reported by @bitsofinfo
provider "kubectl" {
apply_retry_count = 5
host = aws_eks_cluster.this.endpoint
cluster_ca_certificate = base64decode(aws_eks_cluster.this.certificate_authority[0].data)
load_config_file = false
exec {
api_version = "client.authentication.k8s.io/v1beta1"
args = ["eks", "get-token", "--cluster-name", aws_eks_cluster.this.id]
command = "aws"
}
}
kubectl = {
source = "gavinbunney/kubectl"
version = "~> 1.14"
}
I'v switch to this provider - https://registry.terraform.io/providers/alekc/kubectl/latest/docs
Constantly get
This seems to only happen on destroy
I've tried both
load_config_file = true / false
to no avail (the option is confusing... what "path" does this pertain to? the default one on the system or the one inconfig_path
?) is this mutually exclusive or not when used in combination withconfig_path
?)