Terraform-provider-kubernetes: Wait for StatefulSet rollout status

[yaman]

Hi,

Like Deployment Resource, StatefulSet rollout status should be successful before kubernetes provider decides that it is successfully deployed. Is there any obstacles no to use same kind of strategy used in Deployment Resource(waitForDeploymentReplicasFunc)? If not, I would gladly to contribute with a similar implementation.

Terraform&Providers' Version

• Terraform v0.12.7
• terraform-providers/kubernetes: 1.9.0

Affected Resource(s)

Please list the resources as a list, for example:

• StatefulSet

Expected Behavior

Provider should wait before StatefulSet is deployed&running state.

Actual Behavior

Provider successfully terminates saying that StatefulSet is created successfully.

Steps to Reproduce

Please list the steps required to reproduce the issue;

1. terraform apply with a StatefulSet resource.

Important Factoids

Running at GKE

[LiuVII]

Alternatively and more generally it'd be nice to depend on the success of some script/command, like pre-start hook

[dsymonds]

Related, I'd like a way to avoid waiting for rollouts. I have some Deployments and StatefulSets that can take 30m to fully update, but I don't want terraform apply to wait that long. In other words, I'd like either a per-resource property or some provider-wide option to skip the whole waitForDeploymentReplicasFunc step, and exit with the status of the Patch.

[hashibot]

This issue has been open 180 days with no activity. If this issue is reproducible with the latest version of the provider and with Terraform 0.12, please comment. Otherwise this issue will be closed in 30 days.

[dsymonds]

Yes, it is still relevant.

[dsymonds]

I've proposed an approach here: https://github.com/terraform-providers/terraform-provider-kubernetes/pull/842

It doesn't do the StatefulSet waiting, but it does offer the control over this.

[hashibot[bot]]

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!