kubernetes-sigs/kustomize
1
0
Fork 0
mirror of https://github.com/kubernetes-sigs/kustomize.git synced 2026-06-12 01:14:22 +00:00
Code Issues Packages Projects Releases 1 Wiki Activity

Fix markdownlint warnings

Browse Source
This commit is contained in:
Yujun Zhang
2019-03-09 17:02:39 +08:00
parent 0f571b9120
commit 3d0e29075d
1 changed files with 24 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
docs/versioningPolicy.md
View File

@@ -160,7 +160,7 @@ a kustomization file: [`kind`] and [`apiVersion`].
If either field is present, they both must be, and If either field is present, they both must be, and
they must have the following values: they must have the following values:
``` ``` yaml
kind: Kustomization kind: Kustomization
apiVersion: kustomize.config.k8s.io/v1beta1 apiVersion: kustomize.config.k8s.io/v1beta1
``` ```
@@ -171,7 +171,7 @@ domain-squatting behavior for some future API. A
kustomize user gains nothing from adding these kustomize user gains nothing from adding these
fields to a kustomization file. fields to a kustomization file.
### Why not require `kind` and `apiVersion`? ### Why not require `kind` and `apiVersion`
#### Ease of use and setting proper expectations #### Ease of use and setting proper expectations
@@ -203,7 +203,6 @@ locked into `/v1beta1` or `/v1` and the `kind`
and `apiVersion` fields can be required from that and `apiVersion` fields can be required from that
moment forward. moment forward.
[field change policy]: #field-change-policy [field change policy]: #field-change-policy
[some range]: https://kubernetes.io/docs/reference/using-api/deprecation-policy [some range]: https://kubernetes.io/docs/reference/using-api/deprecation-policy
[proposal]: https://github.com/kubernetes/community/blob/master/contributors/design-proposals/api-machinery/customresources-versioning.md [proposal]: https://github.com/kubernetes/community/blob/master/contributors/design-proposals/api-machinery/customresources-versioning.md