Crossplane Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 17: | Line 17: | ||
==<span id='Composite_Resource'></span><span id='XR'></span>Composite Resource (XR)== | ==<span id='Composite_Resource'></span><span id='XR'></span>Composite Resource (XR)== | ||
* It can be thought of as a type. | * It can be thought of as a type. | ||
* An arbitrary number of [[#Composition|compositions]] (implementations) can be mapped onto one composite resource type. | |||
* Type of composite resource - defined with a Composite Resource Definition. | * Type of composite resource - defined with a Composite Resource Definition. | ||
* Type of claim - defined with a Composite Resource Definition. | * Type of claim - defined with a Composite Resource Definition. | ||
Revision as of 00:04, 2 November 2022
External
Internal
TODEPLETE
Overview
Resources in a Crossplane Context
Custom Resource
Managed Resource (MR)
Managed Resource Name
Reconciliation
Composite Resource (XR)
- It can be thought of as a type.
- An arbitrary number of compositions (implementations) can be mapped onto one composite resource type.
- Type of composite resource - defined with a Composite Resource Definition.
- Type of claim - defined with a Composite Resource Definition.
External Resource
Composite Resource Claim (Claim, XRC)
Composition
Why do we need a 'composition' to define how a composite resource maps onto managed resources? Why is not that information built into the composite resource definition itself?
Crossplane Resource Model (XRM)
- Standard Crossplane Resource Model fields.
Package
Package Format
Package Varieties
Provider Package
Configuration Package
Crossplane Package Manager
Provider
Is the provider a package?
Provider Kinds
Kubernetes Provider
Helm Provider
Configuration
Is the configuration a package?