Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conflicting arguments with Kubernetes provider 2.21.0 #188

Closed
avidspartan1 opened this issue Jun 2, 2023 · 3 comments
Closed

Conflicting arguments with Kubernetes provider 2.21.0 #188

avidspartan1 opened this issue Jun 2, 2023 · 3 comments
Labels
bug 🐛 An issue with the system wontfix This will not be worked on

Comments

@avidspartan1
Copy link

avidspartan1 commented Jun 2, 2023

Describe the Bug

When using the latest version of this module with version 2.21 of the Kubernetes provider (released this morning), the new conflictsWith rules break the provider configuration in auth.tf.

I've opened a PR with a fix that's working for me - #189.

Expected Behavior

When executing a plan with version 2.8.1 of this module and version 2.21.0 of the Kubernetes provider, I expect the plan to succeed.

Steps to Reproduce

  1. Upgrade to the latest Kubernetes provider: terraform init -upgrade or terragrunt init -upgrade

  2. Attempt a plan: terraform plan or terragrunt plan

Screenshots

Error message:

╷
│ Error: Conflicting configuration arguments
│
│   with module.eks_cluster.provider["registry.terraform.io/hashicorp/kubernetes"],
│   on .terraform/modules/eks_cluster/auth.tf line 100, in provider "kubernetes":
│  100:   host                   = local.cluster_auth_map_endpoint
│
│ "host": conflicts with config_path
╵

Environment

No response

Additional Context

No response

@Nuru
Copy link
Sponsor Contributor

Nuru commented Jun 2, 2023

I would like to wait and see what the next release of the Kubernetes provider brings before making changes. Historically, this kind of breaking change in a minor version release is reverted due to community feedback. Also, I hope that a future version will continue to provide the ability to override the environment variables rather than fail due to a conflict.

Meanwhile, you can pin your provider version by adding != 2.21.0 to avoid this issue. For example:

terraform {
  required_version = ">= 1.0.0"

  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = ">= 4.0"
    }
    kubernetes = {
      source  = "hashicorp/kubernetes"
      version = ">= 2.7.1, != 2.21.0"
    }
  }
}

@jrhouston
Copy link

Just FYI: We've reverted this change for now and pushed a new release of the kubernetes provider.

@Nuru Nuru added the wontfix This will not be worked on label Jun 5, 2023
@Nuru Nuru changed the title Conflicting arguments with Kubernetes provider 2.21+ Conflicting arguments with Kubernetes provider 2.21.0 Jun 5, 2023
@Nuru
Copy link
Sponsor Contributor

Nuru commented Jun 5, 2023

Closing because this was caused by a breaking change in the provider, which has since been rolled back.

@Nuru Nuru closed this as completed Jun 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 An issue with the system wontfix This will not be worked on
Projects
None yet
3 participants