Server tries to fetch CRD schema for some builtin kubernetes resources

[artem-nefedov]

Describe the bug

The new functionality to fetch k8s CRD schema that was introduced in version 1.20.0 does incorrectly try to fetch it for some (not all) builtin resources.

For example, I get the error Yamlls: Unable to load schema from 'https://raw.githubusercontent.com/datreeio/CRDs-catalog/main/rbac.authorization.k8s.io/rolebinding_v1.json': No content. [768] with document:

apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding

I believe this happens for all resources in rbac.authorization.k8s.io/v1, all of which are builtin resources, not CRDs.

Environment

• Windows
• Mac
• Linux
• other (please specify)

yaml-language-server version 1.21.0, used in integration with helm-ls

[datho7561]

Something's definitely up, because the resolution works fine without helm-ls, but with it, it's broken. I'd have to look into how helm-ls works to understand what's going wrong.

[datho7561]

yaml-language-server downloads https://raw.githubusercontent.com/yannh/kubernetes-json-schema/master/v1.32.1-standalone-strict/all.json and checks all the resources in there before trying to resolve against a custom resource definition schema. I think the problem is likely that if the https://raw.githubusercontent.com/yannh/kubernetes-json-schema/master/v1.32.1-standalone-strict/all.json download fails, then currently it'll fall back to CRD resolution, which doesn't seem like a good idea.

[artem-nefedov]

I would assume then it would try to do CRD schema download for all manifests, but in my case only some of the resources have this problem. For example, this manifest does not cause the problem:

apiVersion: policy/v1
kind: PodDisruptionBudget

[datho7561]

Okay, I played around with it a bit more and it seems like the Microsoft Kubernetes extension was doing something weird on my end that you probably didn't see. I've uninstalled it and am going to continue investigating tomorrow.