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

Operator: Check the route name

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Minor
    • 1.8.0.Final
    • 0.8.1
    • Operator
    • None
    • Workaround Exists
    • Hide

      Reduce namespace and/or application name

      Show
      Reduce namespace and/or application name
    • Hide 
      $ oc new-project tradisso-I-want-a-really-long-namespace-name

      deploy ruleunit-quarkus-example (or any other example with quite a long name)

      $ kogito deploy-service ruleunit-quarkus-example-really-long-name https://github.com/kiegroup/kogito-examples.git -c ruleunit-quarkus-example

      If it not sufficient because server name is short, set longer names

      Show
      $ oc new -project tradisso-I-want-a-really- long -namespace-name deploy ruleunit-quarkus-example (or any other example with quite a long name) $ kogito deploy-service ruleunit-quarkus-example-really- long -name https: //github.com/kiegroup/kogito-examples.git -c ruleunit-quarkus-example If it not sufficient because server name is short, set longer names

    Description

      I just came across an issue on the route name:

      host name validation errors: spec.host: Invalid value: "ruleunit-quarkus-example-jenkins-kogito-1499-smoke-cucumber-rijy.apps.{SERVER_NAME}": must be no more than 63 characters

      Name of the route is composed of:

      • name of the Kogito service
      • name of the namespace
      • `apps` Openshift endpoint

      And that time, the route name was too long and so rejected, which lead to the application not reachable.

      As we want to setup automatic creation of route via the operator, we should add a check of the route and display an error in operator if that happens.

      Attachments

        Issue Links

          is related to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) KOGITO-1688 Consistency in Kogito services naming

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              rhn-support-fspolti Filippe Spolti
              tradisso@redhat.com Tristan Radisson
              Karel Suta Karel Suta
              Karel Suta Karel Suta
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: