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
`with kubernetes_config_map_v1_data.aws_auth, on aws_auth.tf line 1, in resource "kubernetes_config_map_v1_data" "aws_auth": 1: resource "kubernetes_config_map_v1_data" "aws_auth" {
What could be causing the Kubernetes provider to fail during the EKS upgrade from version 1.27 to 1.28?
Are there any additional configurations or Terraform-specific steps required to ensure compatibility and a successful upgrade in the GitLab CI pipeline?
Steps to Reproduce
Use the provided Terraform configuration.
Initiate an EKS cluster upgrade from version 1.27 to 1.28 in a GitLab CI pipeline.
Observe the error during the terraform apply step.
Expected Behavior
The Kubernetes provider should connect to the correct EKS cluster endpoint during the upgrade.
The EKS cluster upgrade process should complete successfully without errors.
Any insights into resolving this issue would be greatly appreciated!
Thank you in advance for your help!
The text was updated successfully, but these errors were encountered:
Description
When the pipeline runs terraform apply, it fails with the following error:
Error: Get "http://localhost/api/v1/namespaces/kube-system/configmaps/aws-auth": dial tcp [::1]:80: connect: connection refused
`with kubernetes_config_map_v1_data.aws_auth, on aws_auth.tf line 1, in resource "kubernetes_config_map_v1_data" "aws_auth": 1: resource "kubernetes_config_map_v1_data" "aws_auth" {
Error: Get "http://localhost/api?timeout=32s": dial tcp [::1]:80: connect: connection refused
with kubernetes_env.aws_node, on k8s.tf line 2, in resource "kubernetes_env" "aws_node": 2: resource "kubernetes_env" "aws_node" {`
Terraform, AWS provider and Kubernetes version
Terraform configuration
Question
Steps to Reproduce
Expected Behavior
Thank you in advance for your help!
The text was updated successfully, but these errors were encountered: