Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1293820

Summary: [DOCS] Document how to use domain names in Endpoints
Product: OpenShift Container Platform Reporter: Alexander Koksharov <akokshar>
Component: DocumentationAssignee: Gaurav Nelson <gnelson>
Status: CLOSED CURRENTRELEASE QA Contact: zhaozhanqi <zzhao>
Severity: medium Docs Contact: Vikram Goyal <vigoyal>
Priority: medium    
Version: 3.1.0CC: abenaiss, aos-bugs, decarr, erich, jkaur, jokerman, knakayam, mbarrett, michael.voegele, misalunk, mmccomas, pep
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-05-22 00:36:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1267746    

Description Alexander Koksharov 2015-12-23 07:27:21 UTC 
Description of problem:
Problem with integrating external service into openshift. Requirement is to refer this service by domain name while Endpoind in openshift can be created by only providing ip address.

Version-Release number of selected component (if applicable):


How reproducible:
Example in step 2 of https://docs.openshift.com/enterprise/3.0/dev_guide/integrating_external_services.html#external-saas-provider looks like what is required.
{
  "kind": "Endpoints",
  "apiVersion": "v1",
  "metadata": {
    "name": "example-external-service" 
  },
  "subsets": [ 
    "api.mysaas.com:80",
    "api2.mysaas.com:8080"
  ]
}

System cant create such entity as it is against to a specification
https://docs.openshift.com/enterprise/3.0/rest_api/kubernetes_v1.html#v1-endpointsubset

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Josep 'Pep' Turro Mauri 2016-01-22 16:30:15 UTC 
Related upstream discussions:

https://github.com/kubernetes/kubernetes/pull/11838
https://github.com/kubernetes/kubernetes/issues/13748
Comment 4 Dan McPherson 2016-06-03 17:58:52 UTC 
*** Bug 1342591 has been marked as a duplicate of this bug. ***
Comment 10 Josep 'Pep' Turro Mauri 2017-04-24 09:47:22 UTC 
The ExternalName service type that covers this use case was released with OCP 3.5:

https://docs.openshift.com/container-platform/latest/release_notes/ocp_3_5_release_notes.html#ocp-35-ability-to-refer-to-external-endpoints-by-name

However, it seems there are no specific docs about it beyond that mention in the release notes, so I'm moving this to a documentation bug to address that.
Comment 11 Gaurav Nelson 2017-05-09 23:21:44 UTC 
Created a pull request (https://github.com/openshift/openshift-docs/pull/4375) for adding this information in the relevant section.
Comment 12 Gaurav Nelson 2017-05-22 00:36:16 UTC 
Updates are now live at https://docs.openshift.com/container-platform/3.5/dev_guide/integrating_external_services.html