List supported protocols for Service#12669
Conversation
|
Deploy preview for kubernetes-io-master-staging ready! Built with commit 2100b0d https://deploy-preview-12669--kubernetes-io-master-staging.netlify.com |
| ## Supported protocols {#protocol-support} | ||
|
|
||
| {{< note >}} | ||
| Layer 7 protocols such as HTTP are handed via the {{< glossary_tooltip term_id="ingress" >}} |
There was a problem hiding this comment.
Is this true for services that need to communicate within the cluster? Services also can handle that right?
There was a problem hiding this comment.
The Service object doesn't (at least in v1.13) set up anything that understands a particular application protocol, and that's what I'm trying to say here.
If you needed to expose a webserver in a way that relies on understanding TLS, or HTTP, then Service is not (yet?) for you. Ingress is your friend.
There was a problem hiding this comment.
If you want to expose something that talks HTTP, and the means of exposure is to publish a TCP port and IPv4 address, the fact it's HTTP isn't important or relevant to Service.
There was a problem hiding this comment.
Maybe it's worth clarifying that you can still expose an HTTP service at the TCP layer?
There was a problem hiding this comment.
Reworded (and meaning changed)
Tidy up protocol support to show that TCP and UDP have support in stable, whereas SCTP support is in alpha. For HTTP, direct users to read up on Ingress instead.
38c97b5 to
2100b0d
Compare
|
|
||
| {{< feature-state for_k8s_version="v1.1" state="stable" >}} | ||
|
|
||
| If your cloud provider supports it (eg, [AWS](https://kubernetes.io/docs/concepts/cluster-administration/cloud-providers/#aws)), |
There was a problem hiding this comment.
nit: only cosmetic but i think you don't need extra space (> 1) after the comma and next word
There was a problem hiding this comment.
I can't see what I'd change to fix this, sorry.
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: zparnold The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Tidy up protocol support to show that TCP and UDP have support in stable, whereas SCTP support is in alpha. For HTTP, direct users to read up on Ingress instead.
Tidy up protocol support to show that TCP and UDP have support in stable, whereas SCTP support is in alpha. For HTTP, direct users to read up on Ingress instead.
Tidy up protocol support to show that TCP and UDP have support in stable, whereas SCTP support is in alpha. For HTTP, direct users to read up on Ingress instead.
Tidy up Service concept to show that TCP and UDP are supported in stable, whereas SCTP support is in alpha.
Place protocol support information in one place on the page.
For HTTP, direct users to read up on Ingress as well.