You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In mid-december I was using "cloudposse/eks-cluster/aws" module pinned to version 3.0.0 to provision EKS clusters without issue. Last week I tried to provision a cluster using this module and was unable to do so. No matter which parameters I adjusted, I was unable to use make it past this error:
╷
│ Error: Value Conversion Error
│
│ with module.eks_cluster.provider["registry.terraform.io/hashicorp/kubernetes"],
│ on .terraform/modules/eks_cluster/auth.tf line 96, in provider "kubernetes":
│ 96: provider"kubernetes" {
│
│ An unexpected error was encountered trying to build a value. This is always
│ an error in the provider. Please report the following to the provider
│ developer:
│
│ Received unknown value, however the target type cannot handle unknown
│ values. Use the corresponding `types` package type or a custom type that
│ handles unknown values.
│
│ Path: exec
│ TargetType: []struct { APIVersion basetypes.StringValue
│ "tfsdk:\"api_version\""; Command basetypes.StringValue"tfsdk:\"command\"";
│ Env map[string]basetypes.StringValue"tfsdk:\"env\""; Args
│ []basetypes.StringValue"tfsdk:\"args\"" }
│ Suggested Type: basetypes.ListValue
With the "cloudposse/eks-cluster/aws" module download locally, I was able to manually pin the hashicorp/kubernetes provider to version "v2.24.0" and provision a cluster without failure. Using any version of the kubernetes provider >v2.24.0 cause the failure to appear.
Expected Behavior
Using the "cloudposse/eks-cluster/aws" I would expect to be able to provision an EKS cluster without the need to locally modify the versions.tf file provided by the module.
Steps to Reproduce
Trying to create an eks-cluster with the example provided in the repo should fail without manually editing the versions.tf file to point the hashicorp/kubernetes provider to version: v2.24.0
Screenshots
No response
Environment
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered:
This is a bug in the Hashicorp/Kubernetes provider, not this module. I do not know why the creator of hashicorp/terraform-provider-kubernetes#2388 closed that bug, because pinning to an old version is not a solution to the bug. I encourage you to open a new bug with the provider project.
We are working on entirely removing the Kubernetes provider from this module, and should have that available in the next few weeks. Because of that, we are not expecting to take any other action to resolve this issue.
Describe the Bug
In mid-december I was using "cloudposse/eks-cluster/aws" module pinned to version 3.0.0 to provision EKS clusters without issue. Last week I tried to provision a cluster using this module and was unable to do so. No matter which parameters I adjusted, I was unable to use make it past this error:
With the "cloudposse/eks-cluster/aws" module download locally, I was able to manually pin the hashicorp/kubernetes provider to version "v2.24.0" and provision a cluster without failure. Using any version of the kubernetes provider >v2.24.0 cause the failure to appear.
Expected Behavior
Using the "cloudposse/eks-cluster/aws" I would expect to be able to provision an EKS cluster without the need to locally modify the versions.tf file provided by the module.
Steps to Reproduce
Trying to create an eks-cluster with the example provided in the repo should fail without manually editing the versions.tf file to point the hashicorp/kubernetes provider to version: v2.24.0
Screenshots
No response
Environment
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: