Page Comparison

An ECD Patch is meant to provide a flexible option to define and provision Kubernetes objects that suit your system architecture, or to tailor the ECD to their preferred flavor.

...

services:
    - spec:
        type: ClusterIP
        ports:
          - port: 9092
            protocol: TCP
            targetPort: 9092
      ...
      ...
      patchType: "application/strategic-merge-patch+json"
      patch: |
        spec:
          ports:
            - name: "port-1"
              port: 9093
              protocol: TCP
              targetPort: 9093
            - name: "port-2"
              port: 9094
              protocol: UDP
              targetPort: 9094
          ...

Here is an example changing multiple (sub-)paths in the same patch:

spec:
  template:
    spec:
      hostAliases:
      - ip: 34.88.208.176
        hostnames:
        - "client"
        - "client-simulator"
      - ip: 35.228.46.60
        hostnames:
        - "proxy"
        - "proxy2"
      containers:
      - name: ec1
        resources:
          limits:
            memory: 1536Mi
          requests:
            memory: 1024Mi

Samples

Below are samples that can help you get started with an ECD patch. The “Before” section is based on the ECD, which is the definition file for the desired state. while the “After” section is based on the conversion and logic processing done by Operator - which is the actual objects provisioning yaml to be applied to the cluster. As you can see, there are several objects that will be provisioned and handled by the Operator itself.

...