crossplane/crossplane v0.13.0

on GitHub

Major Themes

Our main focus in v0.13 is paving the way for a v1.0 release of Crossplane. Over the course of this release we have honed our core Composition and Package Manager APIs. With the help of the community we’ve arrived at APIs that we feel confident will reach v1beta1 imminently without significant breaking changes.

Notable Updates

• #1675 introduces a brand new package manager, focused on installing and managing Crossplane providers and configuration. The new package manager supports updating and rolling back packages. It also deploys packages much faster, and paves the way for automatic package dependency resolution.
• #1679 merges the InfrastructureDefinition and InfrastructurePublication types into the new CompositeResourceDefinition (XRD). Requirements are now known as Composite Resource Claims (XRCs), and no longer require any specific kind suffix.
• #1728 introduces the Crossplane RBAC manager. The RBAC manager automatically manages the RBAC roles and bindings required by providers and composite resources. It is an optional deployment that uses RBAC privilege escalation - Crossplane no longer requires cluster-admin privileges.
• crossplane/provider-aws#331 promotes support for AWS S3 Buckets to v1beta1 thanks to @krishchow and @RedHatOfficial!

Deprecations

• #1720 marks the workload APIs (e.g. KubernetesApplication) as deprecated, slated for removal in v0.14. Take a look at provider-helm for an alternative way to run workloads.
• crossplane/crossplane-runtime#189 marks each Crossplane provider’s Provider resource deprecated (e.g providers.aws.crossplane.io - not to be confused with providers.pkg.crossplane.io), slated for removal in the next provider releases. Provider has been replaced by a similar type named ProviderConfig.

Breaking Changes

• #1749 removes support for Crossplane’s original resource claims (e.g. MySQLInstance), which were deprecated in v0.12. It also removes support for Crossplane’s original package manager (e.g. ClusterPackageInstall).

There is no officially supported and documented upgrade path from v0.12.0. We expect v0.13 to be the last release without a documented upgrade path, due to our new support for upgrading packages, and our confidence in our updated APIs.