Crossplane Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 20: | Line 20: | ||
=Composition= | =Composition= | ||
<font color=darkkhaki>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?</font> | |||
=<span id='Crossplane_Resource_Model'></span><span id='XRM'></span>Crossplane Resource Model (XRM)= | =<span id='Crossplane_Resource_Model'></span><span id='XRM'></span>Crossplane Resource Model (XRM)= | ||
Revision as of 23:01, 1 November 2022
External
Internal
TODEPLETE
Overview
Custom Resource
Managed Resource (MR)
Managed Resource Name
Reconciliation
Composite Resource (XR)
Composite Resource Claim (Claim)
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?