Hide Forgot
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:
Related upstream discussions: https://github.com/kubernetes/kubernetes/pull/11838 https://github.com/kubernetes/kubernetes/issues/13748
*** Bug 1342591 has been marked as a duplicate of this bug. ***
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.
Created a pull request (https://github.com/openshift/openshift-docs/pull/4375) for adding this information in the relevant section.
Updates are now live at https://docs.openshift.com/container-platform/3.5/dev_guide/integrating_external_services.html