domhanak commented on code in PR #721: URL: https://github.com/apache/incubator-kie-kogito-docs/pull/721#discussion_r2070191437
########## serverlessworkflow/modules/ROOT/pages/cloud/operator/gitops-profile.adoc: ########## @@ -0,0 +1,124 @@ += GitOps Profile +:compat-mode!: +// Metadata: +:description: Using GitOps profile for deploying SonataFlow workflows in production environments +:keywords: sonataflow, workflow, serverless, operator, kubernetes, gitops, cicd +// Links: +:rh_jdk17_url: https://catalog.redhat.com/software/containers/ubi9/openjdk-17/61ee7c26ed74b2ffb22b07f6 + +This document describes how to use the GitOps profile for deploying {product_name} workflows in production environments. + +== Recommended for Production + +Using the GitOps profile is recommended for production environments. It provides complete control over workflow image builds, enabling compliance, security, and seamless integration into your existing CI/CD pipelines. + +== Workflow Image Structure + +The GitOps profile uses container images based on the link:{rh_jdk17_url}[Red Hat OpenJDK 17 UBI 9] runtime. You can review its documentation for detailed information about the image architecture. + +The table below highlights important paths in the container image file system. + +.Important file system paths +[cols="1,1"] +|=== +|Path | Description + +|`/deployments` +|Application deployment directory containing Quarkus application components + +|`/deployments/lib` +|Directory for application libraries + +|`/deployments/app` +|Directory for application-specific resources + +|`/deployments/quarkus` +|Quarkus-specific configuration files + +|=== + +== Building Workflow Container Images + +Below is an example Dockerfile illustrating how to build a container image using the GitOps profile. + +.Example Dockerfile +[source,dockerfile,subs="attributes+"] +---- +FROM {sonataflow_builder_imagename}:{kogito_branch} AS builder <1> Review Comment: ```suggestion FROM {sonataflow_builder_imagename}:{operator_version} AS builder <1> ``` kogito_branch: would change to 10.0.x on release branches so we have operator_version that is should correspond to the TAG of images and operator. Hence my suggestion. On release branch this would become `10.1.x` and we want to have `10.1.0` or `main` as tag iirc -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
