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

Data Index Dev UI not shown in the Operator Dev Mode

XMLWordPrintable

    • False
    • None
    • False
    • ---
    • ---
    • 2023 Week 21-23 (from May 22)

      When we deploy a SW using the Operator Dev Mode, the Data Index GraphQL UI is not shown well.

       

      NOTE: if you access the UI by using the http://xxxxxxx:yyyy/q/graphql-ui (it works well, the problem is when it's called from the quarkus dev UI)

       

      Please follow these steps to reproduce:

      1) Start minikube with the following command:

      minikube start --cpus 4 --memory 4096 --addons registry --addons metrics-server --insecure-registry "10.0.0.0/24" --insecure-registry "localhost:5000"

      2) Install the kogito-serverless-workflow operator in your minikube installation.

      kubectl create -f https://raw.githubusercontent.com/kiegroup/kogito-serverless-operator/main/operator.yaml

      3) Create the following namespace

      kubectl create namespace kogito-workflows

      4) Install the following workflow

      kubectl apply -f https://raw.githubusercontent.com/kiegroup/kogito-serverless-operator/main/config/samples/sw.kogito_v1alpha08_kogitoserverlessworkflow_devmode.yaml -n kogito-workflows

      5) verify the greeting workflow is running

      kubectl get pod -n kogito-workflows

      6) Expose the greeting workflow

      kubectl patch svc greeting -n kogito-workflows -p '{"spec": {"type": "NodePort"}}'
      minikube service greeting -n kogito-workflows --url

      with the expose command you'll see a url like this: http://192.168.49.2:32204

      7) Using the url produce in set 6) open the following link and you'll see the quarkus dev UI

      http://192.168.49.2:32204/q/dev

      8) Click on the card link corresponding to the "Data Index GraphQL UI"

       

              cnicolai@redhat.com Cristiano Nicolai (Inactive)
              wmedvede@redhat.com Walter Medvedeo
              Tristan Radisson Tristan Radisson
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: