Aleksandr Rybolovlev

Hi @kexiaodong, Could you please give us some examples of when this feature will be useful? Thank you.

Hi @fdr2, This is expected behavior. In this particular case, version `10.7.16` is not in the Helm chart index and that is the reason you have to provide the full...

Hi @independentid, The observed behavior seems to be normal: - the Kubernetes provider sent a request to destroy a namespace - the Kubernetes cluster accepted it and is trying to...

Thank you. Let me rephrase my questions and give a bit more context. When you see that the namespace is stuck in the `terminating` state, do you see there `DeletionTimestamp`...

Hi @sdahlbac, Could you please try the following changes and let us know if it works? ```hcl resource "kubernetes_manifest" "kafka-0-certificate" { computed_fields = [“spec.ipAddresses”] manifest = { ... ``` Thank...

Hi folks, Could you please `client.authentication.k8s.io/v1alpha1` with `client.authentication.k8s.io/v1beta1` in the exec block? ```hcl provider "kubernetes" { ... exec { api_version = "client.authentication.k8s.io/v1beta1" ... } } ``` Please let me know...

Hi @dm-sumup, This issue doesn't seem to be related to the provider itself, but the community module that uses this provider. It looks like there is a big discussion in...

Hi @NagleZhang, There were a few improvements in the `kubernetes_manifest` resource since you reported this issue. Could you please try the latest provider version and let us know if the...

> I applied this patch on top of terraform-provider-kubernetes, and am successfully able to create `kubernetes_service_account` resources again, so that works, thanks :-) > > I however noted I always...

Hi @sflaherty2009, Do you still have this issue with the latest provider version? If so, please provide more details about the issue, like the error message you observe and debug...