Uploaded image for project: 'Hybrid Application Console'
  1. Hybrid Application Console
  2. HAC-3994

4.13: UI work for OSD/ROSA managed Ingress improvements

XMLWordPrintable

    • UI work for OSD/ROSA managed Ingress improvements
    • False
    • False
    • None

      As discussed (more details in slack https://redhat-internal.slack.com/archives/CB53T9ZHQ/p1684218367713449 and a meeting and the meeting notes https://docs.google.com/document/d/1t0kMCyKzx9XLIXtTf3hBV-lNiUEnN_5t8ThPTHnA4KU/edit#heading=h.9tg7iikr1iz9 ) the requirements on the UI seem to be defined as:

      It needs to support these exact parameters of the cli:

      rosa create cluster \
      ...
          --private=false|true \
          --default-ingress-excluded-namespaces "stage, dev, etc" \
          --default-ingress-route-selector "foo=bar, baz=quux" \
          --default-ingress-namespace-ownership-policy "Strict|InterNamespaceAllowed" \
          --default-ingress-wildcard-policy "WildcardsAllowed|WildcardsDisallowed"

       

      rosa edit ingress -c=<cluster-id> \
      ...
          --private=false|true \
          --excluded-namespaces "stage*, dev*, etc" \
          --route-selector "foo=bar, baz=quux" \
          --namespace-ownership-policy "Strict|InterNamespaceAllowed" \
          --wildcard-policy "WildcardsAllowed|WildcardsDisallowed"

      -----------------------------------------------------------

      In terms of the UI, this means:

      • The feature is available for ROSA classic clusters, and OSD CSS AWS clusters.
      • The Openshift version used for this feature must be >= 4.13, otherwise a text appears instead of the selectors in Day1
      1. In Day1 flow, in the "Networking" step of the wizard, users get to choose between "Default application ingress settings" or "Custom settings". If they choose custom, they see new controls to define: "route selector (routes-exclude)", "excluded namespaces (namespaces-exclude)", "namespace policy", "wildcard policy"
      2. In Day2 flow, in the "Networking" tab, 

         --> Cluster ingress card is for now only editable for non STS clusters (the ones created on the UI are always STS)

        --> Application ingress card allows editing the settings, both for STS and non STS clusters. The "default application router" is the only non-editable property.

         --> Note that, as part of this ticket, the Load Balancer setting has been moved to this card. However, the API does not allow editing it for STS clusters, so it will be uneditable in those clusters.

      -------------------------------------------------

      Regarding the previous CLI commands, the following example

      rosa edit ingress -c=<cluster-id> \
...
    --private=false|true \
    --excluded-namespaces "stage, dev, etc" \
    --route-selector "foo=bar, baz=quux" \
    --namespace-ownership-policy "Strict|InterNamespaceAllowed" \
    --wildcard-policy "WildcardsAllowed|WildcardsDisallowed"

      would be equivalent to the UI settings in the screenshot "ingress-ui-example"

      -------------------------------------------------------

      OCP version support:

      • For 4.13, the fields are missing in the Day 1. But are available for Day 2. The button works, the user can enter data in the modal dialog. The Save might fail - in that case, there is a link how to workaround (means: open a support case). When retried, the Save should pass.
      • The scope of this epic is not the support for 4.14. The 4.14 is separately tracked under https://issues.redhat.com/browse/HAC-5128

        1. ingress-ui-example.png
          121 kB
          Celia Amador Gonzalez
        2. Private_router_to_public.mp4
          3.21 MB
          LAKSHMI SHIVANTHI AMARACHINTHA
        3. ROSA_NON_STS.mp4
          29.42 MB
          LAKSHMI SHIVANTHI AMARACHINTHA
        4. Screenshot 2023-08-24 at 9.38.02 PM.png
          236 kB
          LAKSHMI SHIVANTHI AMARACHINTHA
        1.
        		 DOD: Training materials supplied to Support/SRE Sub-task To Do Undefined Unassigned
        2.
        		 DOD: Docs verified by QE Sub-task To Do Undefined Unassigned
        3.
        		 DOD: Docs completed and merged Sub-task To Do Undefined Unassigned
        4.
        		 DOD: All known issues captured and blockers resolved Sub-task To Do Undefined Unassigned
        5.
        		 DOD: All work items belonging to this Epic are complete Sub-task Closed Undefined Unassigned
        6.
        		 DOD: Code merged for regular build/release testing in the HAC Common CI/CD framework Sub-task To Do Undefined Unassigned
        7.
        		 DOD: CI runs successfully with test automation Sub-task To Do Undefined Unassigned
        8.
        		 DOD: Automated/Integrated tests complete Sub-task To Do Undefined Unassigned
        9.
        		 DOD: Architectural artifacts completed, reviewed and stored Sub-task To Do Undefined Unassigned
        10.
        		 DOD: Product Manager and UX signed off on solution Sub-task To Do Undefined Unassigned
        11.
        		 DOD: Acceptance criteria related to this Epic has been identified and met Sub-task To Do Undefined Unassigned

            mlibra@redhat.com Marek Libra
            tjelinek@redhat.com Tomas Jelinek
            LAKSHMI SHIVANTHI AMARACHINTHA LAKSHMI SHIVANTHI AMARACHINTHA
            HAC
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: