편집을 취소할 수 있습니다. 이 편집을 되돌리려면 아래의 바뀐 내용을 확인한 후 게시해주세요.
최신판 | 당신의 편집 | ||
271번째 줄: | 271번째 줄: | ||
==P== | ==P== | ||
;Patch | ;Patch | ||
A set of instructions describing modifications to a Kubernetes object. Examples include JSON Patch and JSON Merge Patch. | |||
Kubernetes | |||
;Pivot | ;Pivot | ||
Pivot is a process for moving the provider components and declared cluster-api resources from a Source Management cluster to a Target Management cluster. | |||
The pivot process is also used for deleting a management cluster and could also be used during an upgrade of the management cluster. | |||
;Provider | ;Provider | ||
Or Cluster API provider | |||
This term was originally used as abbreviation for Infrastructure provider, but currently it is used to refer to any project that can be deployed and provides functionality to the Cluster API management Cluster. | |||
See Bootstrap provider, Control plane provider, Core provider, Infrastructure provider, IPAM provider Runtime extension provider. | |||
;Provider components | ;Provider components | ||
; | Refers to the YAML artifact published as part of the release process for providers; it usually includes Custom Resource Definitions (CRDs), Deployments (to run the controller manager), RBAC, etc. | ||
In some cases, the same expression is used to refer to the instances of above components deployed in a management cluster. | |||
See Provider repository | |||
;Provider repository | ;Provider repository | ||
; | Refers to the location where the YAML for provider components are hosted; usually a provider repository hosts many version of provider components, one for each released version. | ||
==R== | ==R== |