Hide Forgot
Document URL: https://docs.openshift.com/container-platform/3.3/admin_guide/tcp_ingress_external_ports.html#admin-guide-unique-external-ips-ingress-traffic Section Number and Name: [New] Configuring an Ingress IP for a Service _on [GCE|AWS|Azure|OpenStack] Describe the issue: We explicitly call out in our docs: > Ingress IPs can only be assigned if the cluster is not running in the cloud. In cloud environments, LoadBalancer-type services configure cloud-specific load balancers. This means that the examples provided in our docs, don't work for/on cloud providers, and due to this limitation there is a perception that the product does not work on such providers. Suggestions for improvement: Because of this, we need to better call out how to deploy such "cloud-specific load balancers" for use as an ingress router on openshift. Additional information:
Tracking this in https://github.com/openshift/openshift-docs/pull/7226 The information already exists in the newer version of the docs. Updated docs to mark the note with required information as important and removed the old note.
Jianwei Can you please take a look.
Verified in GitHub https://github.com/openshift/openshift-docs/pull/7226#issuecomment-359769266
Commits pushed to master at https://github.com/openshift/openshift-docs https://github.com/openshift/openshift-docs/commit/daaf0b54744e4681017244f0f20fdc37a2822b3d fixes for bug 1397521 and minor formatting changes https://github.com/openshift/openshift-docs/commit/5146d5857dee4594d4ece3c6d06f5b4ef4f42b8b Merge pull request #7226 from gaurav-nelson/bug1397521-fixes Bug#1397521 - Ingress Configuration now links to cloud providers example
Updates are live at https://docs.openshift.com/container-platform/3.7/admin_guide/tcp_ingress_external_ports.html#admin-guide-unique-external-ips-ingress-traffic