Uploaded image for project: 'Kogito'
  1. Kogito
  2. KOGITO-8395

Missing guide how to deploy on OpenShift Serverless

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 1.40.1.Final
    • None
    • Documentation
    • None
    • False
    • None
    • False
    • ---
    • ---

      Missing guide on how to deploy on OpenShift Serverless

      There is Deploying your Serverless Workflow application on Minikube guide [1] [2], but Minikube is not production ready.

      OpenShift is Red Hat's solution for the cloud and there is no guide for OpenShift Serverless setup.

      I could deploy on OpenShift Serverless, but it was quite a pain and I already have some experience. Customers may not be so patient.

      Kogito team needs to provide simple step by step guide for nice experience with Red Hat solution. CC mmacik@redhat.com to make QE aware.

      application.properties that I used to deploy the app into OpenShift Serverless together with quarkus-openshift extension:

      quarkus.knative.name=kogito-hello-world
      quarkus.container-image.name=kogito-hello-world
      quarkus.kubernetes.deployment-target=knative
      quarkus.container-image.registry=image-registry.openshift-image-registry.svc:5000
      quarkus.openshift.build-strategy=docker
      quarkus.kubernetes.deploy=true
      quarkus.kubernetes-client.trust-certs=true
      quarkus.openshift.route.expose=true
      

      If your OCP project name is different from the username of the host system, set also quarkus.container-image.group=<ocp_project_name>.

      [1] https://kiegroup.github.io/kogito-docs/serverlessworkflow/latest/cloud/deploying-on-minikube.html
      [2]https://openshift-knative.github.io/docs/docs/latest/serverless-logic/cloud/deploying-on-minikube.html

       

              hmanwani@redhat.com Heena Manwani
              rsvoboda@redhat.com Rostislav Svoboda
              Dominik Hanak Dominik Hanak
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: