Crossplane Concepts: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 37: | Line 37: | ||
===Configuration Package=== | ===Configuration Package=== | ||
{{External|https://crossplane.io/docs/v1.10/concepts/packages.html#configuration-packages}} | {{External|https://crossplane.io/docs/v1.10/concepts/packages.html#configuration-packages}} | ||
| Line 42: | Line 43: | ||
=Provider= | =Provider= | ||
<font color=darkkhaki>Is the provider a package?</font> | <font color=darkkhaki>Is the provider a package?</font> | ||
==Provider Kinds== | ==Provider Kinds== | ||
===Kubernetes Provider=== | ===Kubernetes Provider=== | ||
Revision as of 23:38, 1 November 2022
External
Internal
TODEPLETE
Overview
Resources in a Crossplane Context
Custom Resource
Managed Resource (MR)
Managed Resource Name
Reconciliation
Composite Resource (XR)
- 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?