Closed bykvaadm closed 4 years ago
HI @bykvaadm - AFAIK the Terraform Kubernetes provider has no support for CRD's yet, so I've not added support in k2tf
either.
Hi @sl1pm4t, First of all, thanks a lot for the tool. It's awesome. I agree that's not supported, but my understanding is that it should return warn like for other kind (ie MutatingWebhookConfiguration) instead of crashing. The problem is the YAML comes from a third-party and I want to avoid to create my own script to parser the YAML and remove the CRDs declaration. If I understood the code correctly kube-aggregator is the problem. Am I correct?
Maybe a more desirable solution would be to output the support features as a tf and a trimmed version of the yaml for inclusion as standards kubectl command using the external feature?
Hi @thiagonache - Ah I didn't realise k2tf crashed when it came across a CRD yaml. I agree it should be possible to ignore unsupported resources and process all the rest.
Maybe a more desirable solution would be to output the support features as a tf and a trimmed version of the yaml for inclusion as standards kubectl command using the external feature?
yeah... that would be awesome
thank you @sl1pm4t !!!!!
So the Kubernetes Terraform provider now has support for CRD's apparently: https://github.com/hashicorp/terraform-provider-kubernetes/issues/215
Could this be re-opened?
4:13PM Fatal | %!s() error="2 errors occurred:\n\t could not decode yaml object with main scheme #1: no kind \"CustomResourceDefinition\" is registered for version \"apiextensions.k8s.io/v1beta1\" in scheme \"pkg/runtime/scheme.go:101\"\n\t could not decode yaml object with aggregator scheme #1: no kind \"CustomResourceDefinition\" is registered for version \"apiextensions.k8s.io/v1beta1\" in scheme \"pkg/runtime/scheme.go:101\"\n\n"
i.e.