github.com/GoogleContainerTools/skaffold/v2@v2.13.2/docs-v1/content/en/docs/references/deprecation.md (about)

     1  ---
     2  title: "Deprecation Policy"
     3  linkTitle: "Deprecation Policy"
     4  weight: 60
     5  ---
     6  
     7  This document sets out the deprecation policy for Skaffold, and outlines how the Skaffold project will approach the introduction of breaking changes over time.
     8  
     9  Deprecation policy applies only to Stable Builds. Bleeding Edge builds may have less stable implementations.  
    10  
    11  Deprecations to a flag or CLI command require the following notification periods, depending on the release track:
    12  
    13  | Release Track | Deprecation Period |
    14  | -------- | -------- |
    15  | Alpha (experimental)    |0 releases     |
    16  | Beta (pre-release) | 3 months or 1 release (whichever is longer)|
    17  | GA (generally available)   | 6 months or 1 release (whichever is longer) |
    18  
    19  **Breaking changes**
    20  A breaking change is when the primary functionality of a feature changes in a way that the user has to make changes to their workflows/configuration.
    21  - **Breaking config change**:  In case of Skaffold's pipeline config (skaffold.yaml) a breaking change between an old and new version occurs when the skaffold binary cannot parse the input yaml with auto-upgrade. This can happen when the new version removes a feature or when the new version introduces a mandatory field with no default value
    22  - **Breaking functional change**: functional changes that force user workflow changes even when the config is the same or upgradeable.
    23  
    24  ## How do we deprecate things?
    25  
    26  A "deprecation event" would coincide with a release.
    27  
    28  1. We document the deprecation in the following places if applicable
    29      1. deprecation policy - this document 
    30      1. [Document on this site]({{< relref "/docs" >}}) changes in relevant sections
    31      1. [Release notes](https://github.com/GoogleContainerTools/skaffold/blob/main/CHANGELOG.md)
    32      1. [Command help]({{< relref "/docs/references/cli" >}})
    33      1. Log messages
    34      1. [skaffold yaml reference]({{< relref "/docs/references/yaml" >}})
    35      
    36  
    37  2. if applicable, [inspired by the Kubernetes policy](https://kubernetes.io/docs/reference/using-api/deprecation-policy/#deprecating-a-flag-or-cli):
    38      > Rule #6: Deprecated CLI elements must emit warnings (optionally disable) when used.
    39  
    40  # Current maturity of skaffold
    41  
    42  Skaffold and its features are considered GA unless specified (in this document, CLI reference, config YAML reference or in docs in skaffold.dev).  
    43  Skaffold is constantly evolving with the tools space, we want to be able to experiment and sometimes change things. 
    44  In order to be transparent about the maturity of feature areas and things that might change we offer the feature level maturity matrix that we keep up to date.
    45  
    46  ## Skaffold.yaml (pipeline config)
    47  
    48  You can safely depend on the skaffold config with the assumption that skaffold will auto-upgrade to the latest version:
    49  
    50  - Removal and other non-upgradeable changes are subject to the deprecation policy for all (even new) features under the config.
    51  - Auto-upgradeable changes are not considered breaking changes.
    52  
    53  ## Skaffold features
    54  
    55  We are committed to design for auto-upgradeable changes in the config.
    56  However the **behavior** of individual component might suffer breaking changes depending on maturity.
    57  
    58  The following is the maturity of the larger feature areas: 
    59  
    60  {{< maturity-table >}}
    61  
    62  ## Exceptions 
    63  
    64  No policy can cover every possible situation. 
    65  This policy is a living document, and will evolve over time. 
    66  In practice, there will be situations that do not fit neatly into this policy, or for which this policy becomes a serious impediment. 
    67  Examples could be getting fixes fast for a serious vulnerability, a destructive bug or requirements that might be imposed by third parties (such as legal requirements).
    68  Such situations should be discussed on the given bugs / feature requests and during Skaffold Office Hours, always bearing in mind that Skaffold is committed to being a stable system that, as much as possible, never breaks users. 
    69  Exceptions will always be announced in all relevant release notes.
    70  
    71  ## Current deprecation notices
    72  
    73  04/07/2021: Release v1.22.0 deprecates the `--render-only` and `--render-output` flags from `skaffold run` and `skaffold dev`, in favor of simply using the `skaffold render` command directly.
    74  05/05/2021: Release v1.23.0 deprecates the `--add-skaffold-labels` flag from `skaffold render`, and implicitly deprecates the addition of Skaffold-internal labels to any Kubernetes resources
    75  hydrated by Skaffold through `skaffold render`.
    76  
    77  ## Past deprecation notices
    78  
    79  10/21/2019: With release v0.41.0 we mark for deprecation the `$IMAGES` environment variable passed to custom builders. Variable `$IMAGE` should be used instead.
    80  
    81  **This environment variable flag was removed in version v1.22.0.**
    82  
    83  03/15/2019: With release v0.25.0 we mark for deprecation the `flags` field in kaniko (`KanikoArtifact.AdditionalFlags`), instead Kaniko's additional flags will now be represented as unique fields under `kaniko` per artifact (`KanikoArtifact` type).
    84  
    85  **This field was removed in version 1.0.0.**
    86  
    87  02/15/2019: With release v0.23.0 we mark for deprecation the following env variables in the `envTemplate` tagger:
    88  - `DIGEST`
    89  - `DIGEST_ALGO`
    90  - `DIGEST_HEX`
    91  
    92  Currently these variables resolve to `_DEPRECATED_<envvar>_`, and the new tagging mechanism adds a digest to the image name thus it shouldn't break existing configurations.
    93  
    94  **This compatibility behavior was removed in version v1.22.0.**