Created attachment 1818428 [details] Service FQDN shown in v3 Description of problem: In OpenShift v4 Services no longer show their FQDN in the Console page for a Service. In OpenShift v3 they were (see screenshot). This has caused confusion and added steps for developers who are not familiar with how Kubernetes cluster DNS works. Version-Release number of selected component (if applicable): 4.* How reproducible: Always Steps to Reproduce: 1. Create a Kubernetes Service in OpenShift v4. 2. Open that Service's Console page. (e.g. Admin Console -> Networking -> Services -> example-service) 3. Note that the FQDN of the service is not shown. Actual results: Expected results: Show the FQDN of the service similar to v3 (see screenshot). Additional info:
SO it looks like we have been assembling the FQDN manually, check: https://github.com/openshift/origin-web-console/blob/enterprise-3.11/app/views/browse/service.html#L62 Sam do we want this feature parity with v3?
Yes, looks like that's what we want.
Checked on ocp 4.9 cluster with payload 4.9.0-0.nightly-2021-09-05-192114. Go to one service detail page, eg, on "console" service detail page, there is hostname: Hostname console.openshift-console.srv.cluster.local Accessible within the cluster only The bug is fixed.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:3759