redhat-developer / redhat-developer/vscode-yaml
Edit Yaml of CRD: metadata fields are considered invalid?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 830
- Forks
- 260
- Avg merge
- 5h 43m
- Merged PRs (30d)
- 1
Description
Describe the bug
I edit the CRD of the kubebuilder example:
That is valid: Great!
foo: bar
That is not valid: Great!
does-not-exit: broken
But why are the metadata fields (labels, name, namespace, ...) considered invalid?
I see:
Property namespace is not allowed.yaml-schema: kubernetes://schema/webapp.my.domain/v1%40guestbook(513)
I attached the guestbook CRD.
Environment
- Linux
extension version: 1.18.0
vscode:
Version: 1.104.1
Commit: 0f0d87fa9e96c856c5212fc86db137ac0d783365
Date: 2025-09-17T23:36:24.973Z
Electron: 37.3.1
ElectronBuildId: 12404162
Chromium: 138.0.7204.235
Node.js: 22.18.0
V8: 13.8.258.31-electron.0
OS: Linux x64 6.8.0-79-generic
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the validation warning in VS Code using the attached guestbook-crd.yaml and the kubebuilder example, focusing on metadata fields such as labels, name, and namespace. Compare those results with the accepted foo and rejected does-not-exit fields; the issue is done when valid Kubernetes metadata no longer produces schema errors while unknown fields remain invalid.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- devops, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100