Due to an issue of how HTTP2 behaves using a single field for the components routes certificate turned to undesired outcomes. OCP allows to specify the hostname and tls secret reference to each individual component route. This aims to allow the same configuration of OCP to managed clusters.

This functionality was previously handled in HAC-5128

OCM-6028 | The API on stage is already available, but still under QE review

Example patch request below

{
  "component_routes": {
    "oauth": {
      "hostname": "",
      "tls_secret_ref": ""
    },
    "console": {
      "hostname": "",
      "tls_secret_ref": ""
    },
    "downloads": {
      "hostname": "",
      "tls_secret_ref": ""
    }
  }
} 

Acceptance criteria

• Allow changes to parameters of component routes for each component (oauth, downloads, console)
• The parameters are hostname and tlsSecretRef
• The changes are only for day 2 when editing the default ingress (apps) of the cluster