Kubernetes v1.19 not supported

[maltalex]

I'm opening this issue here because of the plugin's claim to have "built-in Kubernetes syntax support".

Unfortunately, it looks like the K8s stops at 1.18 and there's no support for 1.19+

Expected Behavior

Schema support for Kubernetes v1.19+

Current Behavior

Kubernetes yaml v1.19+ not supported. The plugin uses older schema definitions and does not recognize new fields.

Steps to Reproduce

Copy the following yaml into vscode, select "kubernetes" as the schema. Several properties including "pathType", and "backend" will not be allowed:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: test
  annotations:
    kubernetes.io/ingress.class: nginx
spec:
  rules:
  - host: test.example.com
    http:
      paths:
      - path: /
        pathType: Prefix 
        backend:
          service:
            name: test
            port:
              number: 80

for reference, my schema definition file:

{
    "yaml.schemas": {
        "kubernetes": ["*.yaml"]
    }
}

Environment

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

[evidolob]

We need to get instrumenta/kubernetes-json-schema#28 merged first, then we can add v1.19 version support.

[maltalex]

@evidolob that repository hasn't been updated in almost a year now. The last commit was in April 2020. Perhaps it's time to consider using a different source of schemas. Kubernetes 1.20 has already been released and 1.21 is in alpha.

[JPinkney]

AFAIK there isn't really a different source of kubernetes schemas. If you want a true kubernetes editing experience in VSCode then use vscode-kubernetes-tools which depends on this extension.

[maltalex]

@JPinkney

Thanks for the suggestion, I'll take a look at vscode-kubernetes-tools.

People over at instrumenta/kubernetes-json-schema suggested some alternatives in the relevant issue from Nov 2020 (!) -see instrumenta/kubernetes-json-schema#26

Based on the fact that the K8s schema is the only schema explicitly mentioned in this plugin's README, I'm guessing that maintaining K8s compatibility is important for you guys. If instrumenta/kubernetes-json-schema is not longer being maintained, I humbly suggest you consider switching to an actively maintained fork or even host your own.

[evidolob]

We have plans to remove build-in k8s support redhat-developer/yaml-language-server#307
Maybe we need to mention that in readme before we start doing that, to give a time to migrate to vscode-kubernetes-tools

[maltalex]

@evidolob
Fair enough. Might I also suggest documenting how a user could configure the plugin to get the K8s schemas manually if and when you remove the support? This would make the transition a lot easier.

[apelisse]

is vscode-kubernetes-tools a vscode specific thing? Because not everyone uses vscode.

[evidolob]

Fixed with redhat-developer/yaml-language-server#429