Elias Abacioglu

I just hit this bug with Rancher 2.6.9. @niusmallnan & @syndr thank you for the work-around.

Run it on your own computer. Change you kubectl context to one of the master nodes directly instead of via "rancher".

I've been wondering where to put the state for the remote state s3 bakend terraform setup. So I should use this module to create a remote state backend, then update...

Perhaps someone else is qualified to review the code?

Sorry, this cluster is no longer available. And I was unable to reproduce this in a new cluster. Perhaps it was a glitch in the matrix. Thanks for the effort!