github crossplane/crossplane v0.12.0

latest releases: v1.16.0, v1.15.3, v1.14.9...
pre-release3 years ago

Major Themes

The v0.12 release introduces a few new composition features while continuing to refine the direction of the Crossplane project moving forward. Notably, claims have been marked as deprecated in this release and are scheduled to be removed by the v0.15 release. Other improvements include enabling Crossplane providers to access projected service account volumes, updated documentation, and bumping to Go 1.14.4 for a workaround for users running Linux kernel versions that are susceptible to the signal vector bug.

Notable Updates

  • #1577 made it possible to pass a non-zero fsGroup in the security context of a Deployment for a controller installed with a ClusterPackageInstall. This enables providers such as provider-aws to be able to use functionality that requires accessing a token mounted in a projected service account volume (see crossplane/provider-aws#211 for more details).
  • #1581 bumped the Go version for Crossplane's build to 1.14.4 to include a workaround for a Linux kernel bug that could cause the Crossplane and package maneger pods to crash for users with specific kernel versions. More information is available in the Go wiki: https://github.com/golang/go/wiki/LinuxKernelSignalVectorBug
  • #1585 adds the ability to set default and enforced compositions in an InfrastructureDefinition. Documentation for these features was also added in #1607.
  • #1590 updated documentation for new Crossplane contributors. Since the last release, there was also a TBS episode on implementing a new managed resource type in Crossplane that new contributors will likely find useful.

Deprecations

  • #1600 deprecated claims in Crossplane. Claims are being phased out of Crossplane in favor of composition, a more flexible abstraction layer that allows users to define their own infrastructure and publish it to their organization. A detailed overview of composition can be found in the Crossplane documentation.

Breaking Changes

There is no officially supported and documented upgrade path from v0.11.0, but in place upgrade of Crossplane and Packages will be a priority in a near term upcoming release.

Don't miss a new crossplane release

NewReleases is sending notifications on new releases.