Uploaded image for project: 'OpenShift Installer'
  1. OpenShift Installer
  2. CORS-2743

Hybrid SRE: Mix of public and private API server and ingress configurability

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Undefined Undefined
    • openshift-4.15
    • None
    • None
    • Hybrid SRE: Mix of public and private API server and ingress configurability
    • False
    • None
    • False
    • Green
    • To Do
    • OCPSTRAT-716 - Mixed public/private exposure for OpenShift API and OpenShift Ingress on Azure
    • OCPSTRAT-716Mixed public/private exposure for OpenShift API and OpenShift Ingress on Azure
    • 0% To Do, 0% In Progress, 100% Done
    • Hide

      Nov 27

      Status: Green

      PR needs to merge.

      Nov 20

      Status: Yellow

      PR is almost done fixing a few errors. Keeping this to Yellow in case I don't fix them in time.

      31/10/2023
      Colour: Yellow
      Testing has been hard and putting the epic at risk.

      Show
      Nov 27 Status: Green PR needs to merge. Nov 20 Status: Yellow PR is almost done fixing a few errors. Keeping this to Yellow in case I don't fix them in time. 31/10/2023 Colour: Yellow Testing has been hard and putting the epic at risk.

      Feature Overview:

      • Enablement of creation of a mix of public and private API servers and ingress configuration on Azure for improving access to the kubernetes cluster in certain circumstances

      Goals:

      • Allow for the users to create the new mix of public and private API servers and successfully resolve the URLs/IPs to access the cluster

      Requirements:

      • Users providing the setup they need in the install config
      • URL resolution is still possible after the mix is installed

      Use Cases:

      Questions to Answer:

      • A spike is needed to figure out how this needs to be done

      Out of Scope:

      • ...

      Background:

      • ARO needs this for a setup they have in mind

      Customer Considerations:

      • Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status

      Documentation Considerations:

      • Docs for the install config and the architecture in general need to be done as the change is significant

      Interoperability Considerations:

      • Possibly the cluster ingress operator and the CAPI need to be checked if they need to be changed to accommodate this

            rna-afk Aditya Narayanaswamy
            jhixson_redhat John Hixson
            Jinyun Ma Jinyun Ma
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: