kustomize deployment of all workflows

kustomize/escalation/README.md

@@ -8,7 +8,7 @@ A brief explanation of the system architecture is provided in the related [docum
 ### Image update
 Run the following to update the default image to a custom configuration
 ```
-cd overlays/prod && kustomize edit set image serverless-workflow-escalation=quay.io/orchestrator/serverless-workflow-escalation@1234
+cd overlays/prod && kustomize edit set image serverless-workflow-escalation=quay.io/orchestrator/serverless-workflow-escalation:1234
 ```
 
 ## Configure properties

kustomize/greeting/README.md

@@ -0,0 +1,40 @@
+## Prerequisites
+* The manifests are generated without the `namespace` configuration
+* Manifest names reflect the `resources` section of [kustomization.yaml](./base/kustomization.yaml)
+
+A brief explanation of the system architecture is provided in the related [document](./move2kube.md).
+
+## Kustomization options
+### Image update
+Run the following to update the default images to a custom configuration
+```
+cd base && kustomize edit set image serverless-workflow-greeting=quay.io/orchestrator/serverless-workflow-greeting:1234
+```
+
+## Deploy to the cluster
+### Deploy the production environment
+This environment applies the generated manifests with minimal customizations to:
+* Use the latest application images
+* Force the `prod` profile for the SonataFlow instance
+* Deploy by default on the `sonataflow-infra` namespace
+
+The default namespace can be customized with:
+```bash
+TARGET_NS=YOUR-NS
+cd base && kustomize edit set namespace=$TARGET_NS && cd ..
+```
+
+Once the configuration is set, apply the deployment to the configured namespace with:
+```bash
+kustomize build base | oc apply -f -
+```
+
+You can monitor the deployment status with:
+```bash
+oc get sonataflow greeting  -n sonataflow-infra -owide
+```
+
+And finally view the logs with:
+```bash
+oc logs -f  -n sonataflow-infra -l app=greeting
+```

kustomize/greeting/base/01-configmap_01-greeting-resources.yaml

@@ -0,0 +1,20 @@
+apiVersion: v1
+data:
+  greeting.sw.input-schema.json: |
+    {
+      "$schema": "http://json-schema.org/draft-07/schema#",
+      "type": "object",
+      "properties": {
+        "language": {
+          "title": "Language",
+          "description": "Language to greet",
+          "type": "string",
+          "enum": ["English", "Spanish"],
+          "default": "English"
+        }
+      }
+    }
+kind: ConfigMap
+metadata:
+  creationTimestamp: null
+  name: 01-greeting-resources

kustomize/greeting/base/01-sonataflow_greeting.yaml

@@ -0,0 +1,74 @@
+apiVersion: sonataflow.org/v1alpha08
+kind: SonataFlow
+metadata:
+  annotations:
+    sonataflow.org/description: YAML based greeting workflow
+    sonataflow.org/expressionLang: jsonpath
+    sonataflow.org/profile: dev
+    sonataflow.org/version: "1.0"
+  creationTimestamp: null
+  labels:
+    app: greeting
+    sonataflow.org/workflow-app: greeting
+  name: greeting
+spec:
+  flow:
+    dataInputSchema:
+      failOnValidationErrors: true
+      schema: specs/greeting.sw.input-schema.json
+    functions:
+    - name: greetFunction
+      operation: sysout
+      type: custom
+    start:
+      stateName: ChooseOnLanguage
+    states:
+    - dataConditions:
+      - condition: ${$.[?(@.language  == 'English')]}
+        transition:
+          nextState: GreetInEnglish
+      - condition: ${$.[?(@.language  == 'Spanish')]}
+        transition:
+          nextState: GreetInSpanish
+      defaultCondition:
+        transition:
+          nextState: GreetInEnglish
+      name: ChooseOnLanguage
+      type: switch
+    - data:
+        greeting: 'Hello from YAML Workflow, '
+      name: GreetInEnglish
+      transition:
+        nextState: GreetPerson
+      type: inject
+    - data:
+        greeting: 'Saludos desde YAML Workflow, '
+      name: GreetInSpanish
+      transition:
+        nextState: GreetPerson
+      type: inject
+    - actionMode: sequential
+      actions:
+      - actionDataFilter:
+          useResults: true
+        functionRef:
+          arguments:
+            message: $.greeting $.name
+          invoke: sync
+          refName: greetFunction
+        name: greetAction
+      end:
+        terminate: true
+      name: GreetPerson
+      type: operation
+  podTemplate:
+    container:
+      resources: {}
+  resources:
+    configMaps:
+    - configMap:
+        name: 01-greeting-resources
+      workflowPath: specs
+status:
+  address: {}
+  lastTimeRecoverAttempt: null

kustomize/greeting/base/config/image-configuration.yaml

@@ -0,0 +1,4 @@
+# This is to configure where the image is defined in the resources of kind SonataFlow
+images:
+- path: spec/podTemplate/container/image
+  kind: SonataFlow

kustomize/greeting/base/kustomization.yaml

@@ -0,0 +1,22 @@
+apiVersion: kustomize.config.k8s.io/v1beta1
+kind: Kustomization
+
+resources:
+- 01-configmap_01-greeting-resources.yaml
+- 01-sonataflow_greeting.yaml
+
+namespace: sonataflow-infra
+
+configurations:
+- config/image-configuration.yaml
+
+# Replace dev profile in SonataFlow instance(s), add image and envFrom
+patches:
+- path: sonataflow-patch.yaml
+  target:
+    kind: SonataFlow
+    name: greeting
+images:
+- name: serverless-workflow-greeting
+  newName: quay.io/orchestrator/serverless-workflow-greeting
+  newTag: f6fbb19dd531f5bcb612b28862a2303dfae87bd7

kustomize/greeting/base/sonataflow-patch.yaml

@@ -0,0 +1,11 @@
+apiVersion: sonataflow.org/v1alpha08
+kind: SonataFlow
+metadata:
+  name: m2k
+  annotations:
+    sonataflow.org/profile: prod
+spec:
+  podTemplate:
+    container:
+      image: serverless-workflow-greeting
+      resources: {}

kustomize/move2kube/README.md

@@ -0,0 +1,78 @@
+## Prerequisites
+* The manifests are generated without the `namespace` configuration
+* Manifest names reflect the `resources` section of [kustomization.yaml](./base/kustomization.yaml)
+
+A brief explanation of the system architecture is provided in the related [document](./move2kube.md).
+
+## Kustomization options
+### Image update
+Run the following to update the default images to a custom configuration
+```
+cd base && kustomize edit set image serverless-workflow-move2kube=quay.io/orchestrator/serverless-workflow-move2kube:1234 && cd ..
+cd base && kustomize edit set image serverless-workflow-m2k-kfunc=quay.io/orchestrator/serverless-workflow-m2k-kfunc:1234 && cd ..
+```
+
+## Configure properties
+Edit configuration in [replace-config.yaml](./base/replace-config.yaml), [config.properties](./base/config.properties) and 
+[secret.properties](./base/secret.properties) to match your environment configuration.
+
+## Deploy to the cluster
+### Deploy the production environment
+This environment applies the generated manifests with minimal customizations to:
+* Use the latest application images
+* Force the `prod` profile for the SonataFlow instance
+* Deploy by default on the `sonataflow-infra` namespace
+* Mount the configurations defined in [Configure properties](#configure-properties) as environment variables
+
+The default namespace can be customized with:
+```bash
+TARGET_NS=YOUR-NS
+cd base && kustomize edit set namespace=$TARGET_NS && cd ..
+```
+
+Once the configuration is set, apply the deployment to the configured namespace with:
+```bash
+kustomize build base | oc apply -f -
+```
+
+You can monitor the deployment status with:
+```bash
+oc get sonataflow m2k -n sonataflow-infra -owide
+```
+
+And finally view the logs with:
+```bash
+oc logs -f -n sonataflow-infra -l app=m2k
+```
+
+### Notes about transformation from Helm chart
+* The Helm values is converted to a `move2kube-values` ConfigMap and we use a replacement configuration to update the affected fields one by one, as in
+  [replace-config.yaml](./base/replace-config.yamll)
+  * The original [YAML](../../charts/workflows/charts/move2kube/values.yaml) is converted to a [properties file](./base/values.properties)
+  * The original Helm variable references were transformed accordingly, e.g. `{{ .Values.instance.name }}` is changed to `__instance_name__`
+  * The following properties are not managed as values but they were either not used in the chart or we map them differently (e.g. using the image transformer in [kustomization.yaml](./base/kustomization.yaml)):
+```
+# namespace=sonataflow-infra
+# workflow_backstageNotificationURL=http://orchestrator-backstage.orchestrator/api/notifications
+# kfunction_image=quay.io/orchestrator/serverless-workflow-m2k-kfunc:latest
+# workflow_move2kubeURL=https://move2kube-route-sonataflow-infra.apps.cluster-8xfw.redhatworkshops.io
+# workflow_image=quay.io/orchestrator/serverless-workflow-move2kube:latest
+```
+* In the chart, the name of some resources combined the workflow name to a fixed string. This is no more applicable using the kustomize replacements, because
+ it replaces the full content of a target path
+  * We left on purpose some "errors" of this kind as in:
+```yaml
+apiVersion: v1
+kind: Service
+metadata:
+  name: __instance_name__-svc
+...
+```
+  The above name is completely replaced to `name: move2kube`
+* Other properties are defined in [config.properties](./base/config.properties) and allow the deployer to define the runtime environment (we can simplify that [values.properties](./base/values.properties) defines instead the deployment configuration)
+  * These are mounted to the services that require such customization, e.g. the `SonataFlow` instance and the `m2k-save-transformation-func` Knative Service
+
+You can run the following diff to highlight the main changes:
+```bash
+diff -r base/ ../../charts/workflows/charts/move2kube/templates
+```