Exposing Services Externally Using Ingress in Kubernetes

7th chunk of `content/en/blog/_posts/2017-07-00-How-Watson-Health-Cloud-Deploys.md`

d65e9abd7f300b14bd277ab144833b1bf1d7a890f4cad41000000001000004d8

![](https://lh3.googleusercontent.com/Fat60VoOQ6CBxHgAdva9Xwcu1X4coZFlld1eS7ZrB4MbTR9HbwyuXgQ6CncXxeZ_mWqWzpTatB7bOB199QCcCaY8905yAqzMO0-Rx4NNnYj94uXHEy_dwLbLVFQJvQTu8cGW8HSz)



Exposing services with Ingress:



[Ingress controllers](/docs/concepts/services-networking/ingress/#ingress-controllers) are reverse proxies that expose services outside cluster through URLs. They act as an external HTTP load balancer that uses a unique public entry point to route requests to the application.



To expose our services to outside the cluster, we used Ingress. In IBM Cloud Kubernetes Service, if we create a paid cluster, an Ingress controller is automatically installed for us to use. We were able to access services through Ingress by creating a YAML resource file that specifies the service path.


- Post questions (or answer questions) on [Stack Overflow](http://stackoverflow.com/questions/tagged/kubernetes)
- Join the community portal for advocates on [K8sPort](http://k8sport.org/)
- Follow us on Twitter [@Kubernetesio](https://twitter.com/kubernetesio) for latest updates
- Connect with the community on [Slack](http://slack.k8s.io/)
- Get involved with the Kubernetes project on [GitHub](https://github.com/kubernetes/kubernetes)

Title: Exposing Services Externally Using Ingress in Kubernetes

Summary

The document explains how Ingress controllers are used as reverse proxies to expose Kubernetes services outside the cluster via URLs. In IBM Cloud Kubernetes Service, a paid cluster automatically installs an Ingress controller. Services can be accessed through Ingress by creating a YAML resource file that specifies the service path. It also provides links to various community resources for Kubernetes, including Stack Overflow, K8sPort, Twitter, Slack, and GitHub.