Daniel Roth

Understood, using newer images already just found it weird that one of my old tests was failing and thought it might be worth reporting.

I actually found it was still working in v0.14 as well, v0.15 must be the first version it failed.

Nope like I said in the initial report, e.g. this config works: ``` kind: Cluster apiVersion: kind.x-k8s.io/v1alpha4 nodes: - role: control-plane - role: worker image: kindest/node:v1.24.6@sha256:97e8d00bc37a7598a0b32d1fabd155a96355c49fa0d4d4790aab0f161bf31be1 - role: worker ```...

``` kind: Cluster apiVersion: kind.x-k8s.io/v1alpha4 nodes: - role: control-plane image: kindest/node:v1.24.6@sha256:97e8d00bc37a7598a0b32d1fabd155a96355c49fa0d4d4790aab0f161bf31be1 - role: worker image: kindest/node:v1.23.12@sha256:9402cf1330bbd3a0d097d2033fa489b2abe40d479cc5ef47d0b6a6960613148a - role: worker image: kindest/node:v1.24.6@sha256:97e8d00bc37a7598a0b32d1fabd155a96355c49fa0d4d4790aab0f161bf31be1 ``` This config works without problems.

Hey @imjasonh, sure if that helps setup things I believe there's room for us to add more functionality. I'd be happy to merge that in.

Possible fix in [commit](https://github.com/tehcyx/terraform-provider-kind/commit/1e52120c3f9ffdfed908b42de76148d01dff1071)

> Shouldn't the k8s context be deleted after issuing `terraform destroy`? I can see that it's still there for me. The only leftover should be an empty file. The content...

I'll have to dig a little bit into that. This might be kind itself, or the provider not calling a cleanup function on kind. Since the provider itself does not...

I can reproduce it, still figuring out how to best delete the context. kind, minikube and other tools all have their own kubeconfig wrapper, see e.g. here: https://github.com/anencore94/minikube/blob/2c08f62ed21489cfd5db89289b4306b84b39868d/pkg/minikube/kubeconfig/context.go#L66 Wondering how...

Hi, I'll have to see if I can find a better solution. Luckily until then you already have a workaround. Thanks for documenting the workaround here.