kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Fix service name requirement

pull/29114/head
Qiming Teng 2021-07-25 19:57:50 +08:00
parent 2ab22a83ce
commit 26748e36b0
2 changed files with 14 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
content/en/docs/concepts/overview/working-with-objects/names.md
View File

@ -28,7 +28,7 @@ For non-unique user-provided attributes, Kubernetes provides [labels](/docs/conc
In cases when objects represent a physical entity, like a Node representing a physical host, when the host is re-created under the same name without deleting and re-creating the Node, Kubernetes treats the new host as the old one, which may lead to inconsistencies. In cases when objects represent a physical entity, like a Node representing a physical host, when the host is re-created under the same name without deleting and re-creating the Node, Kubernetes treats the new host as the old one, which may lead to inconsistencies.
{{< /note >}} {{< /note >}}
Below are three types of commonly used name constraints for resources. Below are four types of commonly used name constraints for resources.
### DNS Subdomain Names ### DNS Subdomain Names
@ -41,7 +41,7 @@ This means the name must:
- start with an alphanumeric character - start with an alphanumeric character
- end with an alphanumeric character - end with an alphanumeric character
### DNS Label Names ### RFC 1123 Label Names {#dns-label-names}
Some resource types require their names to follow the DNS Some resource types require their names to follow the DNS
label standard as defined in [RFC 1123](https://tools.ietf.org/html/rfc1123). label standard as defined in [RFC 1123](https://tools.ietf.org/html/rfc1123).
@ -52,6 +52,17 @@ This means the name must:
- start with an alphanumeric character - start with an alphanumeric character
- end with an alphanumeric character - end with an alphanumeric character
### RFC 1035 Label Names
Some resource types require their names to follow the DNS
label standard as defined in [RFC 1035](https://tools.ietf.org/html/rfc1035).
This means the name must:
- contain at most 63 characters
- contain only lowercase alphanumeric characters or '-'
- start with an alphabetic character
- end with an alphanumeric character
### Path Segment Names ### Path Segment Names
Some resource types require their names to be able to be safely encoded as a Some resource types require their names to be able to be safely encoded as a

2
content/en/docs/concepts/services-networking/service.md
View File

@ -72,7 +72,7 @@ A Service in Kubernetes is a REST object, similar to a Pod. Like all of the
REST objects, you can `POST` a Service definition to the API server to create REST objects, you can `POST` a Service definition to the API server to create
a new instance. a new instance.
The name of a Service object must be a valid The name of a Service object must be a valid
[DNS label name](/docs/concepts/overview/working-with-objects/names#dns-label-names). [RFC 1035 label name](/docs/concepts/overview/working-with-objects/names#rfc-1035-label-names).
For example, suppose you have a set of Pods where each listens on TCP port 9376 For example, suppose you have a set of Pods where each listens on TCP port 9376
and contains a label `app=MyApp`: and contains a label `app=MyApp`: