ECD Patch is meant to provide a flexible option for users to define and provision Kubernetes objects that suits their system architecture or to tailor the ECD to their preferred flavour.
| Note |
|---|
Patch is NOT the same as |
...
Introduction
The ECD patch functionality is meant to enable users to add, change and remove certain fields and functionality from the different Kubernetes objects created by the Operator through the ECD specification that might not be supported directly in the EDC specification.
An ECD patch is the YAML that defined by the user which will be part of the payload sent by MZ Online to K8S API Server. The patch and patchType are part of the ECD CRD structure and they are on child object of ECD as well. While the use case is to have the ECD (and patch) to be created by MZ Online, technically an ECD can be created through K8S CLI. Since Operator is reconciling and monitoring the cluster through K8S API Server, there is no dependency on who or what is creating the ECD. After ECD is created in the cluster, Operator will be able to detect the change in desired state and act accordingly to match the actual state - the reconciliation process.Based on current design, Operator is expecting the ECD patch to be in .
The operator is expecting the ECD patch to be in YAML format with respective parameters according to the patching strategy. Operator The operator will attempt to patch the user defined YAML with the original YAML, resulting as 1 in one YAML before applying it to the K8S cluster.
...
Patch comprises of 2 fields - Patch and Patch Type, embedded under different K8S objectobjects. Patch is the payload itself, which will be used to patch into the ECD K8S objects. Patch Type is the field where users can define the patching strategies used to patch the payload.
...