We follow the Kubernetes Deprecation Policy and API Versioning Scheme: alpha, beta, GA.
The project is currently in
beta state. Please try the
beta features and provide feedback. After the features exits beta, it may not be practical to make more changes.
- The support for a feature may be dropped at any time without notice.
- The API may change in incompatible ways in a later software release without notice.
- The software is recommended for use only in short-lived testing clusters, due to increased risk of bugs and lack of long-term support.
- The software is well tested. Enabling a feature is considered safe. Features are enabled by default.
- The support for a feature will not be dropped, though the details may change.
- The schema and/or semantics of objects may change in incompatible ways in a subsequent beta or stable release. When this happens, migration instructions are provided. Schema changes may require deleting, editing, and re-creating API objects. The editing process may not be straightforward. The migration may require downtime for applications that rely on the feature.
- The software is not recommended for production uses. Subsequent releases may introduce incompatible changes. If you have multiple clusters which can be upgraded independently, you may be able to relax this restriction.
- The stable versions of features appear in released software for many subsequent versions.
- Use it in production ;)
We define the following scope that is covered by our deprecation policy. We follow the 9 Rules of the Kuberenetes Deprecation Policy.
- API Objects and fields:
- Enums and constant values
- Controller Configuration: CLI flags & environment variables
- Metrics as defined in the Kubernetes docs
- a feature or specific behavior:
We do not provide stability guarantee for source code imports. The Interfaces and the behavior will change in a unexpected and backwards-incompatible way. However, The maintained helm chart is not part of this deprecation policy.