-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Output variables are available before nodes are up #212
Comments
I don't know if this is possible from the API endpoint. |
Or have the output variable be module.gke.state? |
One of the issues is that I think the cluster actually slips between RUNNING and RECONCILING as it spins up node pools so we can't simply wait for it to become 'RUNNING' the first time. |
boo |
That being said, I think added |
How would that work? output variable --> [triggered in] --> null resource --> [depends on] --> all that |
nm. I think I figured it out. https://www.terraform.io/docs/configuration/outputs.html#depends_on-explicit-output-dependencies |
Yeah, do you think you could open a PR? |
I am working on it as we speak |
I am thinking of making the |
Probably all the variables should, but you can start with whichever ones are important for your use case. |
understood. |
merged and closed |
In most (if not all) cases, the output variables are available before the nodes of the cluster are up. For example, the
endpoint
variable is populated as soon as it is known to Terraform (makes sense).It would be helpful to not populate these variables until the nodes are up in a node pool. Or add an output variable that is along the lines of
pods_schedualable
to provide a check whether or not other resources can be deployed in the cluster.The text was updated successfully, but these errors were encountered: