v2.0.0

    2019年02月05日

    After security review, a field used in secret generation (see below) was removed from the definition of a kustomization file with no mechanism to convert it to a new form. Also, the set of files accessible from a kustomization file has been further constrained.

    Per the versioning policy, backward incompatible changes trigger an increment of the major version number, hence we go from 1.0.11 to 2.0.0. We’re taking this major version increment opportunity to remove some already deprecated fields, and the code paths associated with them.

    A kustomization file can specify paths to other files, including resources, patches, configmap generation data, secret generation data and bases. In the case of a base, the path can be a git URL instead.

    In 1.x, these paths had to be relative to the current kustomization directory (the location of the kustomization file used in the command).

    Kustomization Field Removals

    patches

    patches was deprecated and replaced by patchesStrategicMerge when patchesJson6902 was introduced. In Kustomize 2.0.0, patches is removed. Please use instead.

    imageTags

    imageTags is replaced by images since images can provide more features to change image names, registries, tags and digests.

    secretGenerator/commands

    commands is removed from SecretGenerator due to a . One can use or literals, similar to ConfigMapGenerator, to generate a secret.

    Compatible Changes (New Features)

    As this release is triggered by a security change, there are no major new features to announce. A few things that are worth mentioning in this release are:

    • will be converted to

    • Kustomization filename

      In previous versions, the name of a kustomization file had to be kustomization.yaml. Kustomize allows kustomization.yaml, and Kustomization. In a directory, only one of those filenames is allowed. If there are more than one found, Kustomize will exit with an error. Please select the best filename for your use cases.

    • Cancelled plans to deprecate applying prefix/suffix to namespace. The deprecation warning

      was removed.