📘Container Deployment Guide

overview this guide explains how to deploy docuflow using sample yaml files or integrating with your ci/cd pipeline 📦 provided yaml configurations we offer example yaml files for deployment service route these can be used as templates or modified to suit your environment 🐳 container registry & tags docuflow containers are published to our container registry versafile azurecr io pull credential for the container registry will be provides by your account manager available image tags latest tags the latest image of that version qa latest tags the qa latest image of that version, will be typically released 1 week before tagged as latest date stamp (e g , 20250710 ) the tag will stay and is available for up to 12month example versafile azurecr io/docuflow/6 9/df4sap\ latest you may pull directly from our container registry copy to your own container registry 🌐 ingress configuration supported ingress methods ingress or route service type loadbalancer ingress or route currently each port should have a dedicated ingress/route configuration 1 for docuflow gui 1 per archivelink or cmis content server 1 per websocket rfc connection service type loadbalancer one per docuflow deployment 🗂️ storage and configuration docuflow can operate without rwx (readwritemany) storage gui runs in read only mode configuration files loaded via configmap sap certificate added to an secret logs written to stdout and stderr (assumes container output is collected by a monitoring solution)