Learn More on Crossplane

Release Cycle

Starting with the v1.10.0 release, Crossplane releases on a quarterly (13 week) cadence. A cycle comprises three general stages:

Weeks 1—11: Active Development
Week 12: Feature Freeze
Week 13: Code Freeze

This results in four releases per year, with the most recent three releases under maintenance at any given time. When Crossplane cuts a new release, the fourth most recent release reaches end of life (EOL). Users can expect Crossplane to maintain any given release for nine months.

Feature Lifecycle

Feature lifecycle

Crossplane follows a similar feature lifecycle to upstream Kubernetes. Crossplane adds all major new features in alpha. Alpha features graduate to beta, and then to general availability (GA). Features that languish at alpha or beta may be subject to deprecation.

Alpha features

Alpha features are off by default, and you must enable them by a feature flag, for example --enable-composition-revisions. API types for alpha features use a vNalphaN style API version, like v1alpha. Alpha features are subject to removal or breaking changes without notice, and aren’t considered ready for use in production.

Community Extension Projects

The Crossplane community has built a rich set of Community Extension Projects for use by Crossplane adopters to extend the usefulness of their Crossplane powered control planes. They’re all hosted under the crossplane-contrib organization.

Note

All Community Extension Projects should maintain good project health and adhere to the policies stated in the project governance.

If a project falls out of compliance then the repository is archived and the project is removed from this list. All projects on this page should be ready to use by Crossplane adopters.