Kustomize: Provide a JSON Schema for kustomization.yaml
Several editors, like VS Code and IntelliJ, support JSON Schema to provide validation and autocompletion for YAML files. I'd like Kustomize to provide a JSON Schema file for its configuration.
Ideally would be available on http://schemastore.org/json/
mxey
All 13 comments
Using vs code its kind of irritating that kustomization.yaml files marked as wrong.
fentas
on 9 Feb 2019
Since Kustomize now has apiVersion and kind in the file, maybe the schema can be put where the other Kubernetes API schemas are, so all editors that import the Kubernetes API schemas will just get it?
mxey
on 11 Feb 2019
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot
on 12 May 2019
/remove-lifecycle stale
fentas
on 12 May 2019
gorkem
on 28 May 2019
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot
on 26 Aug 2019
Hello!
I'm getting Unexpected property patches error for all my kustomization.yaml files in VSCode and COCVim :(
Am I doing something wrong?
ralgozino
on 27 Aug 2019
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
fejta-bot
on 26 Sep 2019
@ralgozino there is no patches anymore in latest kustomize. Only patchesJson6902 and patchesStrategicMerge.
michaelkrupp
on 26 Sep 2019
@michaelkrupp Are you sure that it has been removed? It was only introduced in 3.2.0 (inlinePatch doc on master branch and 3.2.0 release notes), and I can't see anything in later release notes that say it has been removed.
pgpx
on 17 Oct 2019
@pgpx you appear to be correct. I could not find any official documentation for this though, aside from the release notes you already linked.
michaelkrupp
on 22 Oct 2019
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
fejta-bot
on 21 Nov 2019
@fejta-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen.
Mark the issue as fresh with/remove-lifecycle rotten.Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
k8s-ci-robot
on 21 Nov 2019
Related issues
karlmutch
路
5Comments
lionelvillard
路
4Comments
drekle
路
4Comments
bugbuilder
路
3Comments
davidsbond
路
3Comments
Most helpful comment
Since Kustomize now has
apiVersionandkindin the file, maybe the schema can be put where the other Kubernetes API schemas are, so all editors that import the Kubernetes API schemas will just get it?