fixing the typo the Object Names and IDs page
Signed-off-by: lhajouji <lhajouji@gmail.com>
This commit is contained in:
parent
93f2deb3ad
commit
cce091a887
|
|
@ -34,7 +34,7 @@ In cases when objects represent a physical entity, like a Node representing a ph
|
||||||
|
|
||||||
The server may generate a name when `generateName` is provided instead of `name` in a resource create request.
|
The server may generate a name when `generateName` is provided instead of `name` in a resource create request.
|
||||||
When `generateName` is used, the provided value is used as a name prefix, which server appends a generated suffix
|
When `generateName` is used, the provided value is used as a name prefix, which server appends a generated suffix
|
||||||
to. Even though the name is generated, it may conflict with existing names resulting in a HTTP 409 resopnse. This
|
to. Even though the name is generated, it may conflict with existing names resulting in a HTTP 409 response. This
|
||||||
became far less likely to happen in Kubernetes v1.31 and later, since the server will make up to 8 attempt to generate a
|
became far less likely to happen in Kubernetes v1.31 and later, since the server will make up to 8 attempt to generate a
|
||||||
unique name before returning a HTTP 409 response.
|
unique name before returning a HTTP 409 response.
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue