I've Installed the Plugin - Nothing Happens

[Fosol]

Anyone have a tutorial to install and get working?

I've installed the plugin, but it doesn't do anything.

I have no intelli-sense available in my yaml files.

I'd also love to have Openshift schema loaded.

[gorkem]

Your setup is probably missing a schema association. This extension needs to have a mapping that tells the extension which schema to use. We do have a built-in schema for Kubernetes, which you can configure as described on the README.

[agreedSkiing]

@gorkem
So....

Well no Hi!

How do I configure this plugin to give me intellisens andexplenations for openshift/kubernates based yamls? And maybe Istio/Maistra also since that I something I use regularly.

I have tried the settings down below to get it to work and yes it works in my kustomization.yaml but no where else :(

    "yaml.completion": true,
    "yaml.format.enable": false,
    "yaml.schemaStore.enable": true,
    "yaml.schemas": {
          "https://json.schemastore.org/kustomization.json": "kustomization.yaml",
          "Kubernetes": "/*.yaml"
    }

Those settings have been tried it in a strategic merge yaml file (a file that is used in the patchStrategicMerge: section of my kustomization.yaml) and its deployment base file.

Strategic merge yaml file

apiVersion: apps/v1
kind: Deployment
metadata:
  name: ca-cmc-admin
spec:
  template:
    spec:
      containers:
        - name: ca-cmc-admin
          volumeMounts:
            - name: ca-cmc-admin-properties
              mountPath: /opt/ca-cmc-admin/
            - name: ca-cmc-admin-cmc-crt
              mountPath: /opt/ca-cmc-admin/cmc/
            - name: ca-cmc-admin-jks
              mountPath: /opt/ca-cmc-admin/keystore/
      volumes:
        - name: ca-cmc-admin-cmc-crt
          configMap:
            name: ca-cmc-admin-crt
        - name: ca-cmc-admin-properties
          configMap:
            name: ca-cmc-admin-properties
        - name: ca-cmc-admin-jks
          configMap:
            name: ca-cmc-admin-jks

Base deployment yaml file

apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    app: ca-cmc-admin
    app.openshift.io/runtime: spring-boot
  name: ca-cmc-admin
spec:
  replicas: 1
  revisionHistoryLimit: 5
  selector:
    matchLabels:
      app: ca-cmc-admin
  strategy:
    type: Recreate
  template:
    metadata:
      labels:
        app: ca-cmc-admin
    spec:
      containers:
        - env:
            - name: SPRING_PROFILES_ACTIVE
              value: base
          name: ca-cmc-admin
          ports:
            - containerPort: 8080
              name: http
              protocol: TCP
          image: always:latest
          imagePullPolicy: Always
          resources:
            limits:
              cpu: 500m
              memory: 2Gi
            requests:
              cpu: 200m
              memory: 1Gi

I just feel like I can't be the only one having problems with this configuration and to my knowledge I'm not the only one in my company that has these problem, and if you point me to the https://github.com/redhat-developer/vscode-yaml#associating-schemas explain this section to me like I'm a five year old.

[Fosol]

Good luck! I gave up a long time ago.

[agreedSkiing]

Did that once before now I'm instead asking questions :) since I want to get it working

[gorkem]

Usually, you should not need to explicitly set the schema for 'kustomization.yaml' it should be picked up from the schema store API. Do you see anything on the logs that may indicate a connection issue ?

[agreedSkiing]

To much text in that log file to print it into a code block
Yaml-Support.log

[agreedSkiing]

Right shared settings.shared.json is the same as settings.json thanks to Swellaby.workspace-config-plus

[agreedSkiing]

Right.... that file was with the old config...
So the last picture was with

  "yaml.schemas": {
    "Kubernetes": "/*.yaml"
  },

where is a log without yaml.schemas and now only kustomization.yaml have hints.
Yaml-support.log

[agreedSkiing]

And these settings kinda work but give me some error in the kustomization.yaml

{
  "editor.defaultFormatter": "esbenp.prettier-vscode",
  "editor.formatOnSave": true,
  "editor.formatOnPaste": true,
  "yaml.completion": true,
  "yaml.format.enable": false,
  "yaml.schemaStore.enable": true,
  "yaml.trace.server": "verbose",
  "yaml.schemas": {
    "https://json.schemastore.org/kustomization.json": "kustomization.yaml",
    "https://raw.githubusercontent.com/garethr/openshift-json-schema/master/v4.1.0/all.json": "*.yaml"
  }
}

Log
Yaml-support.log

Picture

[agreedSkiing]

Negative look ahead sorted that out "https://raw.githubusercontent.com/garethr/openshift-json-schema/master/v4.1.0/all.json": ["*.yaml","!kustomization.yaml"] but now the error has move to my deployment yaml 🤣

[gorkem]

Do you use vscode-kubernetes-tools, I have found that in complicated cases like k8s an extension that manages the schemas like the k8s extension helps.

[agreedSkiing]

No, been only using the vscode-yaml and nothing more for my configuration projects, well except for the swellaby.workspace-config-plus and esbenp.prettier-vscode. Also whilst asking this question I had only those 3 plug-ins/extensions active. Currently it feels like the matching for applying the correct json scheme seems to whacky to my limited knowledge.

[agreedSkiing]

So this I the configuration I got working, and turned off validation since some stuff are added through - op: add or - op: replace , strategic merges or by the server like in the openshift routes (validation can be a nightmare).

{
  "editor.defaultFormatter": "esbenp.prettier-vscode",
  "editor.formatOnSave": true,
  "editor.formatOnPaste": true,
  "yaml.completion": true,
  "yaml.format.enable": false,
  "yaml.schemaStore.enable": true,
  "yaml.validate": false,
  "yaml.schemas": {
    "https://json.schemastore.org/kustomization.json": "kustomization.yaml",
    "Kubernetes": ["*", "!kustomization.yaml"],
    "https://raw.githubusercontent.com/garethr/openshift-json-schema/master/v4.1.0/all.json": [
      "*",
      "!kustomization.yaml"
    ]
  }
}

This gives me my current need for suggestions, but I needed to specific the kustomization.json schema since the base didn’t show me any explanation for patchesStrategicMerge.