6장. Configuring workflow services
This section describes how to configure a workflow service by using the OpenShift Serverless Logic Operator. The section outlines key concepts and configuration options that you can reference for customizing your workflow service according to your environment and use case. You can edit workflow configurations, manage specific properties, and define global managed properties to ensure consistent and efficient execution of your workflows.
6.1. Modifying workflow configuration 링크 복사링크가 클립보드에 복사되었습니다!
The OpenShift Serverless Logic Operator decides the workflow configuration based on two ConfigMaps for each workflow: a workflow for user-defined properties and a workflow for Operator managed-properties:
-
User-defined properties: if your workflow requires particular configurations, ensure that you create a
ConfigMapnamed<workflow-name>-propsthat includes all the configurations before workflow deployment. For example, if your workflow name isgreeting, theConfigMapname isgreeting-managed-props. If suchConfigMapdoes not exists, the Operator creates the workflow to have empty or default content. -
Managed properties: automatically generated by the Operator and stored in a
ConfigMapnamed<workflow-name>-managed-props. These properties are typically related to configurations for the workflow. The properties connect to supporting services, the eventing system, and so on.
Managed properties always override user-defined properties with the same key. These managed properties are read-only and reset by the Operator during each reconciliation cycle.
Prerequisites
- You have OpenShift Serverless Logic Operator installed on your cluster.
- You have created your OpenShift Serverless Logic project.
- You have access to a OpenShift Serverless Logic project with the appropriate roles and permissions to create applications and other workloads in OpenShift Container Platform.
-
You have installed the OpenShift CLI (
oc). -
You have previously created the workflow
user-definedpropertiesConfigMap, or the Operator has created it.
Procedure
Open your terminal and access the OpenShift Serverless Logic project. Ensure that you are working within the correct project,
namespace, where your workflow service is deployed.$ oc project <your-project-name>Identify the name of the workflow you want to configure.
For example, if your workflow is named
greeting, the user-defined properties are stored in aConfigMapnamedgreeting-props.Edit the workflow
ConfigMapby executing the following example command:$ oc edit configmap greeting-propsReplace
greetingwith the actual name of your workflow.Modify the
application.propertiessection.Locate the
datasection and update theapplication.propertiesfield with your desired configuration.Example of
ConfigMapapiVersion: v1 kind: ConfigMap metadata: labels: app: greeting name: greeting-props namespace: default data: application.properties: | my.properties.key = any-value ...- After updating the properties, save the file and exit the editor. The updated configuration will be applied automatically.
The workflow runtime is based on Quarkus, so all the keys under application.properties must follow Quarkus property syntax. If the format is invalid, the OpenShift Serverless Logic Operator might overwrite your changes with default values during the next reconciliation cycle.
Verification
To confirm that your changes are applied successfully, execute the following example command:
$ oc get configmap greeting-props -o yaml