-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
google_container_cluster.cluster: unexpected EOF #4305
Comments
Hi, I have also been experiencing this. After running terraform, the resource in question is successfully created, but terraform errors out: Error: Error applying plan:
Please help! Please note: my google provider version is: 2.7.0, More detail This error is thrown upon completion of a created container_cluster, the same error is being thrown across multiple projects, and it happens right after the default nodepool deletion is finished. Actually, upon testing, the error is thrown upon completion whetehr or not the defaul nodepool is removed. This is reproducibility happening with newly named clusters, defined as below:
|
I have been seeing this since Monday as well. Looks like it creates the cluster fine but crashes when it moves onto the node pools
|
Just had the same error after last changes and trying to apply for a new cluster. Terraform Version provider.google v1.20.0 The code was running correctly for some time already, since it starts to complain about the creation and deletion of the default node pool. I needed to remove the following statements from the resource: cluster: lifecycle { I followed to change the following parameters: remove_default_node_pool = true But keeps repeating the same issue. |
It looks like in 2.11.0 of the google-beta-provider they improved the error-handling for these types of things. |
Thanks @robertb724 I tried with Google Beta provider version 2.11.0 and worked out with out any error.
|
@rohitrd0987 yes, still curious about what happened over the weekend to cause these errors to increase. Our setup had been working for months on 2.3. Probably a change on the Google side |
@robertb724 Many thanks!!! |
@robertb724 I was also working with 2.3.0 for more than 3 months, when I started using Istio plugin as a add-on config in my tf scripts for GKE. |
Hey there, this appears to be a duplicate of several other issues and it is fixed in v2.11.0 of the google provider. The preferred solution is to upgrade your version of the google provider to 2.11.0+ This is due to a nil reference to maintenance window. A workaround is listed in the following bug if upgrading the provider is not an option #4010 |
@robertb724 check this out. |
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! |
Community Note
Terraform Version
Terraform v0.11.13
I noticed this not working from August 18,2019.
Affected Resource(s)
Creating a GCP Subnet in an exsisting VPC and a GKE private Cluster with Private endpoint.
Terraform Configuration Files
Terraform code from the below repo iis used which was found in Terraform Registry and made appropriate changes which doesnot require a NAT, VPC,Cloud Router creation for my usecase.
https://github.com/dansible/terraform-google-gke-infra
Debug Output
https://gist.github.com/rohitrd0987/85ebcaf016e128066b7b53c454a3871d
Panic Output
https://gist.github.com/rohitrd0987/2a044c693f5b9a9fdc9526890413c6e9
Expected Behavior
This should have created a subnet ina existing VPC and create a GKE private cluster with private endpoint
Actual Behavior
Erroring out throwing a terraform crash message
Steps to Reproduce
Use the below repo and make sure that you change the public endpoint to private and run terraform apply with appropriate configuration.
https://github.com/dansible/terraform-google-gke-infra
In my usecase I don't need VPC, SA, Cloud NAT.
terraform apply
Important Factoids
N/A
References
The text was updated successfully, but these errors were encountered: