Bug 1623338 - Misunderstanding about svc hostname from Webconsle
Summary: Misunderstanding about svc hostname from Webconsle
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 3.9.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 3.11.z
Assignee: Samuel Padgett
QA Contact: Yadan Pei
Depends On:
TreeView+ depends on / blocked
Reported: 2018-08-29 06:34 UTC by wangzhida
Modified: 2021-12-10 17:12 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2019-02-20 14:11:01 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:0326 0 None None None 2019-02-20 14:11:07 UTC

Description wangzhida 2018-08-29 06:34:09 UTC
Description of problem:

This is concern from customer. They found that from WebConsole, The service hostname shows a info and says: This address is only resolvable from within the cluster.

However when they $nslookup the hostname such as: <svc>.<project>.svc from node. The DNS will return : <svc>.<project>.svc.cluster.local instead of the one without .cluster.local.

The question is, which is correct that our internal DNS service (skyDNS) can do. 

From my test, the resolve can not be directly success and sent to upstream DNS Server. If the upstream return no match then it will auto add the search domain "cluster.local" and then get the correct answer from local DNS.

The customer concern about the info from WebConsole which tells them that "<svc>.<project>.svc" can be resolved inside the cluster and the result doesn't match that.

Actual results:

- The result doesn't match the info provided from webconsole.

Expected results:

- 1. Need to know which kind of name could be resolved. Must contains "cluster.local"?

- 2. Is there any details info about skyDNS ? how to config it ?
- 3. If sky DNS can only resolve the name contains cluster.local, the info from WebConsole may caused some misunderstanding for customer.

This question can be repo in all of OCP version begin from 3.6

Thanks a lot.

Comment 1 Samuel Padgett 2019-01-30 00:17:04 UTC
`<service>.<namespace>.svc` should resolve from inside a pod as well, but we will update the hostname in the console to use the fully-qualified `.cluster.local`.


Comment 3 shahan 2019-02-11 10:30:14 UTC
check service instance on web console, hostname will be <svc>.<ns>.svc.cluster.local with suffix 'cluster.local'.

OpenShift Master:
Kubernetes Master:
OpenShift Web Console:
verified this bug

Comment 5 errata-xmlrpc 2019-02-20 14:11:01 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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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