Skip to content

terraform 0.12 not supported with release 2.4.0 #1341

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

Closed
dschunack opened this issue Aug 3, 2021 · 4 comments · Fixed by #1345
Closed

terraform 0.12 not supported with release 2.4.0 #1341

dschunack opened this issue Aug 3, 2021 · 4 comments · Fixed by #1345
Labels

Comments

@dschunack
Copy link

dschunack commented Aug 3, 2021

Terraform Version, Provider Version and Kubernetes Version

Terraform version: Terraform v0.12.31
+ provider.aws v3.52.0
+ provider.external v2.1.0
+ provider.helm v2.2.0
+ provider.kubernetes v2.4.0
+ provider.local v2.1.0
+ provider.null v3.1.0
+ provider.random v2.2.1
+ provider.template v2.2.0

Kubernetes provider version: 2.4.0
Kubernetes version: 1.20

Affected Resource(s)

All kubernetes resources that use the kubernetes provider.

Steps to Reproduce

Use terraform 0.12.31

  1. terraform init
  2. terraform apply

3: Output
Error: Incompatible terraform version

on .terraform/modules/ebs-csi-driver/kubernetes.tf line 1, in provider "kubernetes":
1: provider "kubernetes" {

This provider requires Terraform v0.14.8 or above

Expected Behavior

Kubernetes provider 2.3.2 runs without problems.

Actual Behavior

Error: Incompatible terraform version

on .terraform/modules/ebs-csi-driver/kubernetes.tf line 1, in provider "kubernetes":
1: provider "kubernetes" {

This provider requires Terraform v0.14.8 or above

@dschunack dschunack added the bug label Aug 3, 2021
@dschunack dschunack changed the title terraform 0.12 not support in version 2.4.0 terraform 0.12 not supported with release 2.4.0 Aug 3, 2021
@ifs-anthonylecarrer
Copy link

neither 0.12.x nor 0.13.x without any communication ......

@simonvanderveldt
Copy link

simonvanderveldt commented Aug 3, 2021

We're using

  required_providers {
    kubernetes = {
      version = ">= 2.0.0, < 3.0.0"
    }
  }

to make sure that allout breakage doesn't happen, but that assumes proper use of versions/tags by the provider (i.e. a bump of the major version in case of backwards incompatible changes).
Can this be fixed?

P.S. 2.4.0 also doesn't have a proper release here in the repo, only a tag

@jrhouston
Copy link
Collaborator

Sorry for the disruption folks. This version constraint was not intentional and was carried over when we merged the kubernetes-alpha code into this repository.

We have a hotfix incoming.

@github-actions
Copy link

github-actions bot commented Sep 3, 2021

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 3, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants