Introducing provider-http: Crossplane with HTTP Interactions
Learn about Crossplane provider-http, explore its capabilities, and see how it can enhance your infrastructure management.| The Crossplane Blog
The base Crossplane installation consists of two pods, the crossplane pod and the crossplane-rbac-manager pod. Both pods install in the crossplane-system namespace by default. Crossplane pod Init …| Crossplane Documentation
Providers enable Crossplane to provision infrastructure on an external service. Providers create new Kubernetes APIs and map them to external APIs. Providers are responsible for all aspects of …| Crossplane Documentation
A Usage is a Crossplane resource that defines a usage relationship for a Managed Resource or a Composite Resource. Two main use cases for the Usages are as follows: Protecting a resource from …| Crossplane Documentation
A Configuration package is an OCI container image containing a collection of Compositions, Composite Resource Definitions and any required Providers or Functions. Configuration packages make your …| Crossplane Documentation
Learn about Crossplane provider-http, explore its capabilities, and see how it can enhance your infrastructure management.| The Crossplane Blog
Announcing the donation of function-kcl to Crossplane! KCL, a constraint-based record and functional language, enhances writing complex configurations.| The Crossplane Blog
Explore Crossplane 1.15! Discover enhanced CLI, improved DevEx for platform engineers, and new features for cloud infrastructure management.| The Crossplane Blog
Crossplane changes the default registry from DockerHub to xpkg.upbound.io in the Crossplane v1.15.0 release.| The Crossplane Blog
