Andrew

DigitalOcean provider in same situation mark cluster for recreation. It is sane and expectable behaviour. First thought was "wow, they spin up new cluster and migrate old one to it...

I confirm this issue! same behavior

> Can you open a DigitalOcean support ticket so the team can take a closer look? If `s3cmd getlifecycle` is returning the lifecycle rule as defined in Terraform, that suggests...

Hmm, it's hard, this failure was unintentional. The only solution to recreate it is to run similar virtual machines in smaller scale on workstation and abort them. It was not...

Hello @ChiefMateStarbuck! Yes, after some trials and tests `lifecycle_rule` works for me. My issue was wrong prefix value. My final code looks almost same as OP policy. I dunno why,...

Hello @gabrieljackson! We run without license; we activate trial license to look around and cancel it couple of weeks later. It was 2 weeks ago and users start to complain...

Thanks for clarification! However it is very very bad user experience since MM Operator creates 2 replicas by default (also no "red alarm" fires in my head while I read...

Confirm! It's still very actual, especially in face of upcoming one `ru-central1-c` deprecation! Master was moved to `ru-central1-d` with CLI https://yandex.cloud/ru/docs/managed-kubernetes/tutorials/migration-to-an-availability-zone#regional and now there is no way to sync tf...

`slice` option can't be changed with tf too

Confirm! I got my PAT deleted yesterday, replaced it in provider config, but doks token do not renewed in state so all my attempts to use `kubernetes` provider lead to...