-
Notifications
You must be signed in to change notification settings - Fork 93
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
Version 1.11 of Terraform kubernetes provider causes stack launch failure #90
Comments
The provider versions are supposed to be pinned, see: https://github.com/kbst/terraform-kubestack/blob/master/aws/cluster/providers.tf Each cluster module has this. If this does not ensure the provider has the correct version, this needs investigation. Moving the provider version pinning to the versions.tf may be one option. Reading the issue you linked, it seems this does not only apply to EKS, but also GKE and AKS. It seems it's related to creating the cluster and the k8s resources on it in the same TF apply run. This is something Kubestack depends heavily on and which worked fine before this upstream change. |
I will try to look at this again later to see if I get the same behaviour. Although I did follow the quick start guide it is possible that I missed something. |
I tried this again and got the same behaviour. After a bit of digging I found that it seems to be the way that the pessimistic constraint operator evaluates the allowed versions. If you include the patch version in the version string it seems to work as intended. e.g. 1.10.0 or alternatively use the exact version operator. Someone has raised an issue here hashicorp/go-version#55 some time ago but have no response. |
|
Lock provider major, minor and patch versions fix #90
Using the latest version of the kubernetes provider fails to launch the aws quickstart stack (quickstart/src/configurations/eks) with error:
This seems to be a known issue - see hashicorp/terraform-provider-kubernetes#759
Pinning the provider at 1.10 seems to be a workaround for the issue:
The text was updated successfully, but these errors were encountered: