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

Error: failed to configure: execProvider and authProvider cannot be used in combination #1239

Closed
tachang opened this issue Apr 15, 2021 · 4 comments
Labels

Comments

@tachang
Copy link

tachang commented Apr 15, 2021

Terraform Version, Provider Version and Kubernetes Version

Terraform version: v0.14.3
Kubernetes provider version: v2.0.3
Kubernetes version: 

Affected Resource(s)

  • Provider itself

Terraform Configuration Files

provider "kubernetes" {
  host                   = var.cluster_endpoint
  cluster_ca_certificate = base64decode(var.cluster_certificate_authority[0].data)
  exec {
    api_version = "client.authentication.k8s.io/v1alpha1"
    command     = "aws"
    args        = ["eks", "get-token", "--cluster-name", var.cluster_name, "--region", "us-east-1"]
  }
}

Debug Output

Panic Output

Steps to Reproduce

Expected Behavior

What should have happened?

Everything should have been configured properly. Works on Terraform 13.4

Actual Behavior

What actually happened?

Got an error:

Error: failed to configure: execProvider and authProvider cannot be used in combination

Important Factoids

References

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment
@tachang tachang added the bug label Apr 15, 2021
@tachang
Copy link
Author

tachang commented Apr 16, 2021

It seems like I had a working kubectx. As soon as I switched it to another cluster it worked on my command line.

@alexsomesan
Copy link
Member

@tachang is this still an issue for you or have you solved it?

@tachang
Copy link
Author

tachang commented Apr 21, 2021

I solved it so this can be closed. The issue was the kubectx was pointing to a valid cluster so it used that I assume? Weird but solved.

@tachang tachang closed this as completed Apr 21, 2021
@ghost
Copy link

ghost commented May 22, 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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!

@ghost ghost locked as resolved and limited conversation to collaborators May 22, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants