Bug 1342591 - Have the ability to define a DNS name for an endpoint (only supports IP for now)
Summary: Have the ability to define a DNS name for an endpoint (only supports IP for now)
Keywords:
Status: CLOSED DUPLICATE of bug 1293820
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Dan McPherson
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-03 15:34 UTC by Miheer Salunke
Modified: 2020-06-11 12:53 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-03 17:58:52 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Miheer Salunke 2016-06-03 15:34:35 UTC
1. Proposed title of this feature request  
    => Have the ability to define a DNS name for an endpoint (only supports IP for now)
     

 
    3. What is the nature and description of the request?  
    => We need a very convenient feature when using OpenShift External Services:

As an OpenShift user, I want to have the ability to define External Services pointing to Endpoints on which I only have the hostname (not only the IP address).

This is very convenient for databases or other services available in AWS, like AWS Relational Databases Systems.

This issue is fixed by [1] in the following PR in k8s upstream but is subject to a lot of discussions[3].

The issue has been closed in favour of other issue more related to naming and "internal services".

There is a very ugly workaround that still exists which rely on deploying an extra HA Proxy to only to the Hostname to IP indirection. [2]

[1] https://github.com/kubernetes/kubernetes/pull/11838
[2] http://www.cloudwerkstatt.com/?p=34846
[3] https://github.com/kubernetes/kubernetes/issues/13748



    4. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?  
=>  Urgent, hot fix will work       

    5. Is the sales team involved in this request and do they have any additional input?  
      Not known  
 
    6. List any affected packages or components.  
=> Kuberenetes
      
    7. Would the customer be able to assist in testing this functionality if implemented?  
    => Yes, they will assist us.

Comment 2 Dan McPherson 2016-06-03 17:58:52 UTC

*** This bug has been marked as a duplicate of bug 1293820 ***


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