-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
None
-
False
-
-
False
-
None
-
None
-
None
-
None
-
None
Currently the ConsoleLink supports an option for href to allow a user to provide a URL such as the following:
apiVersion: console.openshift.io/v1 kind: ConsoleLink metadata: name: application-menu-link-1 spec: href: 'https://www.example.com' location: ApplicationMenu text: Link 1 applicationMenu: section: My New Section # image that is 24x24 in size imageURL: https://via.placeholder.com/24
It would be fantastic to support an option to instead provide a route object and allow the ConsoleLink to dynamically pull the route URL from the route object directly.
An example CR could look something like this:
apiVersion: console.openshift.io/v1 kind: ConsoleLink metadata: name: application-menu-link-1 spec: linkType: route route: name: example-route namespace: example-namespace location: ApplicationMenu text: Link 1 applicationMenu: section: My New Section # image that is 24x24 in size imageURL: https://via.placeholder.com/24
Why?
This would be very flexible for configuring ConsoleLinks for applications deployed directly on the cluster, without requiring you to know the exact URL that a route will generate for a specific application.
This would also be very useful for managing configurations across multiple clusters where you can utilize the exact same ConsoleLink object on each environment without having to manually update the href with the correct cluster URL.