Alex Somesan

TL;DR; The next provider release should work as expected with these resources. It looks like this is a case of non-structural CRDs. I was able to install them using these...

@chrisadkin We just released 0.5.0 which contains improvements relevant to your issue. Can you give it a try and share your results with us?

@ggolub I just tried your configuration with the new v0.3.0 and I can apply it successfully. Be aware of that you currently need to specify a value for the `protocol`...

For reference, this is the configuration that worked for me: ``` resource "kubernetes_manifest" "namespace_istio" { provider = kubernetes-alpha manifest = { "apiVersion" = "v1" "kind" = "Namespace" "metadata" = {...

Hi @thecodeassassin. It is expected that this configuration will not work reliably as Terraform doesn't officially support supplying provider configuration values from other resources or datasources. In the case of...

> > Terraform doesn't officially support supplying provider configuration values from other resources or datasources > > Since when? This is literally the most common method of configuring the helm...

@thecodeassassin can you try this again with provider version v0.3.1 ? I'd like to find out if this is still an issue after the refactoring.

@jbg What you are seeing here is a response from the cert-manager admission web-hook (as denoted by the `API response status` message). This is not an error in the provider,...

@jbg Thanks for the clarification. That puts some perspective on the whole issue. We do have an ongoing battle with the empty blocks in this provider. In most cases, apart...

This issue is currently on hold pending discussion about test frameworks to use going forward.