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

Avoid to register Openshift components when running in Kubernetes

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Minor Minor
    • 0.12.0
    • 0.11.0
    • Operator
    • 2020 Week 25-27 (from Jun 15)

      When deploying the Kogito Operator, we can see these warnings:

       

      {"level":"info","T":"2020-06-09T08:42:07.872Z","logger":"cmd","msg":"Registering Components."}
      {"level":"warn","T":"2020-06-09T08:42:07.875Z","logger":"framework","msg":"Impossible to register GroupVersion apps.openshift.io/v1. CRD not installed in the cluster, controller might not behave as expected"}
      {"level":"warn","T":"2020-06-09T08:42:07.875Z","logger":"framework","msg":"Impossible to register GroupVersion route.openshift.io/v1. CRD not installed in the cluster, controller might not behave as expected"}
      {"level":"warn","T":"2020-06-09T08:42:07.875Z","logger":"framework","msg":"Impossible to register GroupVersion image.openshift.io/v1. CRD not installed in the cluster, controller might not behave as expected"}
      ...
       

      As the logs are working, the priority is set to minor, but if we know we're installing the components in Kubernetes, we should not try to register Openshift resources.

              rhn-support-zanini Ricardo Zanini
              jcarvaja@redhat.com Jose Carvajal Hilario
              Karel Suta Karel Suta
              Karel Suta Karel Suta
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: