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 container Before starting the core Crossplane container an init container runs. The init container installs the core Crossplane Custom Resource Definitions (CRDs), configures Crossplane webhooks and installs any supplied Providers or Configurations. Tip The Kubernetes documentation contains more info...| Concepts on Crossplane
A composite resource represents a set of managed resources as a single Kubernetes object. Crossplane creates composite resources when users access a custom API, defined in the CompositeResourceDefinition. Tip Composite resources are a composite of managed resources. A Composition defines how to compose the managed resources together. Confused about Compositions, XRDs, XRs and Claims? Crossplane has four core components that users commonly mix up: Compositions - A template to define how to cre...| Concepts on Crossplane
A Crossplane EnvironmentConfig is a cluster-scoped, strongly typed, ConfigMap-like resource used by Compositions. Compositions can use the environment to store information from individual resources or to apply patches. Crossplane supports multiple EnvironmentConfigs, each acting as a unique data store. When Crossplane creates a composite resource, Crossplane merges all the EnvironmentConfigs referenced in the associated Composition and creates a unique in-memory environment for that composite...| Concepts on Crossplane
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 accidental deletion. Deletion ordering by ensuring that a resource isn’t deleted before the deletion of its dependent resources. See the section Usage for Deletion Protection for the first use case and the section Usage for Deletion Ordering for the second one.| Concepts on Crossplane
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 configuration fully portable. Important Crossplane Providers and Functions are also Crossplane packages. This document describes how to install and manage configuration packages. Refer to the Provider and Composition Functions chapters for details on their usage of packages. Install a Conf...| Concepts on Crossplane
ImageConfig is an API for centralized control over the configuration of Crossplane package images. It allows you to configure package manager behavior for images globally, without needing to be …| 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 managed resource (MR) represents an external service in a Provider. When users create a new managed resource, the Provider reacts by creating an external resource inside the Provider’s …| Crossplane Documentation
Compositions are a template for creating multiple managed resources as a single object. A Composition composes individual managed resources together into a larger, reusable, solution. An example …| Crossplane Documentation
Composite resource definitions (XRDs) define the schema for a custom API. Users create composite resources (XRs) and Claims (XCs) using the API schema defined by an XRD. Note Read the composite …| Crossplane Documentation
Claims represents a set of managed resources as a single Kubernetes object, inside a namespace. Users create claims when they access the custom API, defined in the CompositeResourceDefinition. Tip …| Crossplane Documentation