ddelange

the env var idea with multi-arch enabled by default sounds like a good plan! I recently took a similar approach [here](https://github.com/stevearc/pypicloud-docker/pull/37) > I'm guessing we'd have to do them all...

Hi! That was quick :) Not on the latest now that you say so. How is it relevant? Just curious ``` $ terraform version Terraform v1.0.9 on darwin_amd64 + provider...

Yes, was also big surprise to me that there is no `depends_on` for providers (ref https://github.com/hashicorp/terraform/issues/2430) Regarding the plan when there is no cluster yet: it's probably the same when...

My current hack to write the kubeconfig to a local file and use it downstream (will need to have the `kops` executable available): ```terraform resource "kops_cluster_updater" "updater" { ... provisioner...

I would say every time, after a couple applies like that I just checked this morning and again the same scenario on a `terraform apply`: revision = 13 -> 14...

Hmm, interesting! Thanks for checking guys. This was not the case before upgrading to 1.23. The only diff to `cluster.tf` apart from the version bump, was adding the `containerd.config_override` block....

Correct, `1.23.0-alpha.1` and ```tf variable "kubernetes_version" { type = string description = "Kubernetes version to use for the cluster. MAJOR.MINOR here should not be newer than the kops provider version...

Looks like unrelated indeed. Behaviour stays the same 🤔

The file exists, looks like a valid manifest. Created (r/w perms) by my AWS account yesterday when I created the 1.23 cluster. Same permissions as the rest of the files,...

Many thanks for taking the time! I would just close with that for now and if it disappears over time (or I miraculously find a fix) I will report back...