Stano Bocinec

@matilote by chance could you rebase from the base branch (`master`) and try to push the changes to satisfy the CI? It would be awesome if this feature can finally...

@schlichtanders @cyberslot you mention using kustomize bundled with kubectl (`kubectl kustomize`) - can you ensure you use kubectl version 1.27+ ? Older versions of kubectl bundled v4 version of the...

@ross-p-smith I guess you already found a solution, only for future reference - I think the issue was not caused by the docker-compose, but the fact Temporal has removed the...

I confirm, we do experience exactly the same issue as @rigman24 - when `wait { rollout = true }` is provided for a Daemonset in the `kubernetes_manifest` resource, the apply...

I've tried to use `kubernetes_daemon_set_v1` resource - it does not throw `Error: Provider produced inconsistent result after apply` error, but it does not respect `wait_for_rollout = true` and is always...

I'm experiencing siimilar error with `devenv gc` and devenv `1.0.4` caused by the unknown `impure` argument: ``` cloudv on  main [$!?] via 🐹 v1.22.1 via  v18.12.1 with 🐃...

@domenkozar thanks for working on the issue :raised_hands: Btw is there a way how to run `gc` manually? I've tried to remove `impure: true` from my `devenv.yaml`, but it's still...

> `sudo -E nix-collect-garbage` Awesome, TY! One OT note for others: the command didn't work with `-E` ( I have devenv & nix installed on Ubuntu 22.04): ``` $ sudo...

@BBBmau I confirm, the issue is valid and still present. Here is a short reproducer: ``` terraform { required_version = "~> 1.7" kubernetes = { source = "hashicorp/kubernetes" version =...

I have identified the issue and trying to prepare a fix https://github.com/hashicorp/terraform-provider-kubernetes/pull/2419 - need to test the fix yet.