From 91f73900dbebb9019f6b6489940ead7b37240172 Mon Sep 17 00:00:00 2001
From: Rajesh Deshpande <47311048+rajeshdeshpande02@users.noreply.github.com>
Date: Wed, 27 Mar 2019 12:59:52 +0530
Subject: [PATCH] Correcting statement about Service ports (#13337)

* Correcting statement about Service ports

Correcting details about service ports and protocol. Removed statement saying Service supports the single port definition only and added details about multiport definitions.

* Correcting format changes

Correcting format changes as per feedback from reviewer.
---
 content/en/docs/concepts/services-networking/service.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/content/en/docs/concepts/services-networking/service.md b/content/en/docs/concepts/services-networking/service.md
index a6bc859b79..a05343d9da 100644
--- a/content/en/docs/concepts/services-networking/service.md
+++ b/content/en/docs/concepts/services-networking/service.md
@@ -84,8 +84,9 @@ number that pods expose in the next version of your backend software, without
 breaking clients.
 
 `TCP` is the default protocol for services, and you can also use any other
-[supported protocol](#protocol-support). At the moment, you can only set a
-single `port` and `protocol` for a Service.
+[supported protocol](#protocol-support). As many Services need to expose more than
+one port, Kubernetes supports multiple port definitions on a `Service` object.
+Each port definition can have the same or a different `protocol`.
 
 ### Services without selectors