search

eddycharly / terraform-provider-kops

Brings kOps into terraform in a fully managed way
Apache License 2.0
85 stars 20 forks source link

Unable to validate cluster with kops_cluster_updater #969

Closed b4ird closed 1 year ago

b4ird commented 1 year ago

I've built a new cluster using terraform-provider-kops==1.25.3 and kubernetes==1.23.2.

I can use the kops_cluster_updater for both apply and rolling-update functionality, however when I try to enable validation it just keeps on trying until the timeout is reached.

I'm only able to see the kops output when setting TF_LOG="WARN" and when I do I get a load of kops messages about the v1 ComponentStatus deprecation, e.g.

2023-03-30T13:36:02.659+0100 [WARN]  unexpected data: registry.terraform.io/eddycharly/kops:stderr="W0330 13:36:02.659216   19593 warnings.go:70] v1 ComponentStatus is deprecated in v1.19+"
module.cluster.kops_cluster_updater.updater: Still modifying... [id=mycluster.example.com, 7m0s elapsed]
module.cluster.kops_cluster_updater.updater: Still modifying... [id=mycluster.example.com, 7m10s elapsed]
module.cluster.kops_cluster_updater.updater: Still modifying... [id=mycluster.example.com, 7m20s elapsed]
2023-03-30T13:36:28.676+0100 [WARN]  unexpected data: registry.terraform.io/eddycharly/kops:stderr="W0330 13:36:28.675957   19593 warnings.go:70] v1 ComponentStatus is deprecated in v1.19+"
module.cluster.kops_cluster_updater.updater: Still modifying... [id=mycluster.example.com, 7m30s elapsed]
module.cluster.kops_cluster_updater.updater: Still modifying... [id=mycluster.example.com, 7m40s elapsed]

I am however able to validate the cluster using the 1.25.3 kops binary and the same state-store so am a little confused. Shouldn't this validation now be using the new endpoints?

b4ird commented 1 year ago

Just to add, i've now rebuilt the cluster with kops==1.20.0-beta.2 and kubernetes==1.18.20 and validation works so it does sound like it is the deprecated API