-
Feature Request
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
None
-
Product / Portfolio Work
-
None
-
False
-
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
-
None
1. Proposed title of this feature request Hosted Console
2. What is the nature and description of the request?
Cluster console runs on the data plane and the route is published using the cluster's default ingress controller and load balancer in the hosted cluster's cloud account. This request to provide an ability to run cluster workloads in the hosting cluster and publish the console to the internet from the hosting cloud account, and to the cluster VPC through AWS Private Link or equivalent service.
Additionally, provide the ability to optionally install console using Openshift's cluster capabilities.
3. Why does the customer need this? (List the business requirements here)
- Cluster as a service provider: Could not offer Openshift's console reliably. Separation of concerns on the default ingress controller is poor because both cluster components like console and applications are hosted on the same ingress controller. When offering zero worker nodes, console becomes unavailable too.
- Cluster Owner: Console needs to be highly available for good UX and observability of the platform/workloads. On other cloud platforms, console is hosted and does not consume resources or adds to our bill. Need to be able to access the console privately or publicly, independent of visibility of API Server.
4. List any affected packages or components.
Hosted Control Plane, Console, Ingress Controller
- relates to
-
RFE-7280 Disabled Capabilities at install time
-
- Backlog
-