Merge pull request #289 from natasha41575/deprecationdocs

kustomize: add deprecation warning to docs

Author: k8s-ci-robot

site/content/en/references/kustomize/kustomization/bases/_index.md

@@ -8,7 +8,14 @@ description: >
 ---
 
 {{% pageinfo color="warning" %}}
-The `bases` field was deprecated in v2.1.0
+The `bases` field was deprecated in v2.1.0. This field will never be removed from the
+kustomize.config.k8s.io/v1beta1 Kustomization API, but it will not be included
+in the kustomize.config.k8s.io/v1 Kustomization API. When Kustomization v1 is available,
+we will announce the deprecation of the v1beta1 version. There will be at least
+two releases between deprecation and removal of Kustomization v1beta1 support from the
+kustomize CLI, and removal itself will happen in a future major version bump.
+
+You can run `kustomize edit fix` to automatically convert `bases` to `resources`.
 {{% /pageinfo %}}
 
 Move entries into the [resources](/references/kustomize/kustomization/resource)

site/content/en/references/kustomize/kustomization/patchesStrategicMerge/_index.md

@@ -7,6 +7,20 @@ description: >
     Patch resources using the strategic merge patch standard.
 ---
 
+{{% pageinfo color="warning" %}}
+The `patchesStrategicMerge` field was deprecated in v5.0.0. This field will never be removed from the
+kustomize.config.k8s.io/v1beta1 Kustomization API, but it will not be included
+in the kustomize.config.k8s.io/v1 Kustomization API. When Kustomization v1 is available,
+we will announce the deprecation of the v1beta1 version. There will be at least
+two releases between deprecation and removal of Kustomization v1beta1 support from the
+kustomize CLI, and removal itself will happen in a future major version bump.
+
+Please move your `patchesStrategicMerge` into
+the [patches](/references/kustomize/kustomization/patches) field. This field supports patchesStrategicMerge,
+but with slightly different syntax. You can run `kustomize edit fix` to automatically convert
+`patchesStrategicMerge` to `patches`.
+{{% /pageinfo %}}
+
 Each entry in this list should be either a relative
 file path or an inline content
 resolving to a partial or complete resource
@@ -59,7 +73,7 @@ patch that performs all the needed deletions.
 
 A patch can refer to a resource by any of its previous names or kinds.
 For example, if a resource has gone through name-prefix transformations, it can refer to the
-resource by its current name, original name, or any intermediate name that it had. 
+resource by its current name, original name, or any intermediate name that it had.
 
 ## Patching custom resources
 

site/content/en/references/kustomize/kustomization/patchesjson6902/_index.md

@@ -7,6 +7,20 @@ description: >
     Patch resources using the [json 6902 standard](https://tools.ietf.org/html/rfc6902)
 ---
 
+{{% pageinfo color="warning" %}}
+The `patchesJson6902` field was deprecated in v5.0.0. This field will never be removed from the
+kustomize.config.k8s.io/v1beta1 Kustomization API, but it will not be included
+in the kustomize.config.k8s.io/v1 Kustomization API. When Kustomization v1 is available,
+we will announce the deprecation of the v1beta1 version. There will be at least
+two releases between deprecation and removal of Kustomization v1beta1 support from the
+kustomize CLI, and removal itself will happen in a future major version bump.
+
+Please move your `patchesJson6902` into
+the [patches](/references/kustomize/kustomization/patches) field. This field supports patchesJson6902,
+but with slightly different syntax. You can run `kustomize edit fix` to automatically convert
+`patchesJson6902` to `patches`.
+{{% /pageinfo %}}
+
 Each entry in this list should resolve to a kubernetes object and a JSON patch that will be applied
 to the object.
 The JSON patch is documented at <https://tools.ietf.org/html/rfc6902>
@@ -94,4 +108,4 @@ patchesJson6902:
 
 A patch can refer to a resource by any of its previous names or kinds.
 For example, if a resource has gone through name-prefix transformations, it can refer to the
-resource by its current name, original name, or any intermediate name that it had. 
+resource by its current name, original name, or any intermediate name that it had.

site/content/en/references/kustomize/kustomization/vars/_index.md

@@ -9,10 +9,25 @@ description: >
 
 [replacements]: https://kubectl.docs.kubernetes.io/references/kustomize/kustomization/replacements/
 
-WARNING: There are plans to deprecate vars. For existing users of vars, we recommend migration to [replacements]
-as early as possible. There is a guide for convering vars to replacements at the bottom of this page under
-"convert vars to replacements". For new users, we recommend never using vars, and starting with replacements
-to avoid migration in the future.
+{{% pageinfo color="warning" %}}
+The `vars` field was deprecated in v5.0.0. This field will never be removed from the
+kustomize.config.k8s.io/v1beta1 Kustomization API, but it will not be included
+in the kustomize.config.k8s.io/v1 Kustomization API. When Kustomization v1 is available,
+we will announce the deprecation of the v1beta1 version. There will be at least
+two releases between deprecation and removal of Kustomization v1beta1 support from the
+kustomize CLI, and removal itself will happen in a future major version bump.
+
+Please try to migrate to the
+the [replacements](/references/kustomize/kustomization/replacements) field. If you are
+unable to restructure your configuration to use replacements instead of vars, please
+ask for help in slack or file an issue for guidance.
+
+We are experimentally attempting to
+automatically convert `vars` to `replacements` with `kustomize edit fix --vars`. However,
+converting vars to replacements in this way will potentially overwrite many resource files
+and the resulting files may not produce the same output when `kustomize build` is run.
+We recommend doing this in a clean git repository where the change is easy to undo.
+{{% /pageinfo %}}
 
 Vars are used to capture text from one resource's field
 and insert that text elsewhere - a reflection feature.