Uploaded image for project: 'Network Edge'
  1. Network Edge
  2. NE-1317

Update the cluster ingress operator manifests with the ingress capability

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • None
    • None
    • None
    • None
    • Sprint 238, Sprint 239, Sprint 240, Sprint 241, Sprint 242, Sprint 243, Sprint 244, Sprint 245, Sprint 246, Sprint 247, Sprint 248, Sprint 249, Sprint 250, Sprint 251, Sprint 252

      Goal
      The goal of this user story is to add the new (ingress) capability to the cluster operator's payload (manifests: CRDs, RBACs, deployment, etc.).

      Out of scope

      • CRDs and operands created at runtime (assets: gateway CRDs, controllers, subscription. etc.)

      Acceptance criteria

      • The ingress capability is known to the openshift installer.
      • The new capability does not introduce any new regression to the e2e tests.

      Links

              alebedev@redhat.com Andrey Lebedev
              alebedev@redhat.com Andrey Lebedev
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: