Bug 1998616 - Show fully qualified domain name (FQDN) a Service's page
Summary: Show fully qualified domain name (FQDN) a Service's page
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.8
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 4.9.0
Assignee: Jakub Hadvig
QA Contact: Yanping Zhang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-27 18:12 UTC by Patrick Strick
Modified: 2021-10-18 17:49 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: Missing logic that constructs the FQDN of a Service. Consequence: Missing service's fully qualified domain name (FQDN) on the Service details page. Fix: Add logic that constructs the FQDN. Result: Service's FQDN is available on the details page.
Clone Of:
Environment:
Last Closed: 2021-10-18 17:49:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Service FQDN shown in v3 (28.33 KB, image/png)
2021-08-27 18:12 UTC, Patrick Strick
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 9979 0 None None None 2021-09-02 18:53:32 UTC
Red Hat Product Errata RHSA-2021:3759 0 None None None 2021-10-18 17:49:58 UTC

Description Patrick Strick 2021-08-27 18:12:36 UTC
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:

Comment 1 Jakub Hadvig 2021-09-02 10:32:20 UTC
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?

Comment 2 Samuel Padgett 2021-09-02 13:09:56 UTC
Yes, looks like that's what we want.

Comment 5 Yanping Zhang 2021-09-06 05:01:07 UTC
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.

Comment 8 errata-xmlrpc 2021-10-18 17:49:46 UTC
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


Note You need to log in before you can comment on or make changes to this bug.