Ivan Ka

I didn’t spend too much time on this, so my analyse could be incorrect, but I wanted to provide an overview of why the current implementation is slow and why...

By any chance, could you first do simple improvements? Step 1. - support for labelselector https://github.com/kubernetes-sigs/external-dns/blob/0aababa74156664680a6dd525ce92a2b03417f7b/source/istio_virtualservice.go#L142 - and here https://github.com/kubernetes-sigs/external-dns/blob/0aababa74156664680a6dd525ce92a2b03417f7b/source/istio_gateway.go#L130 This is not a killer feature, but a good starting...

Any chance to share helm examples?

That's an excellent feature. While Helm currently only validates values, implementing basic checks would be straightforward. The key question is, what specific features are planned to be prioritized for the...

I can share one more use case - Example we are on karpenter `0.37.0` - Karpenter team releases new version `1.0` - There is number of custom CRDs in helm,...

There is one gotcha `crds/karpenter.sh_nodeclaims.yaml` this is not a schema ((

I need that feature more and more as well. Trying to find the best option how to implement.

Is it still a problem or fixed for now?

There is no drop-in replacement. Example helm uses `sigs.k8s.io/yaml` which is a wrapper/fork `https://github.com/kubernetes-sigs/yaml/tree/master/goyaml.v3`

5+ years old unmainted dependent library "https://github.com/dprotaso/go-yit" and 4+ unmainted library "github.com/vmware-labs/yaml-jsonpath/pkg/yamlpath" Problem with `gopkg.in/yaml.v3` it uses no interfaces, so the only way is to rewrite things from the ground