From 10fabcdb139212644468f4be6e988c5ed67847ee Mon Sep 17 00:00:00 2001 From: Joe Betz Date: Mon, 2 Dec 2019 12:49:11 -0800 Subject: [PATCH] Clarify equality rules --- content/en/docs/reference/using-api/api-concepts.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/reference/using-api/api-concepts.md b/content/en/docs/reference/using-api/api-concepts.md index 09542cc15ab16..ec046c7a090a6 100644 --- a/content/en/docs/reference/using-api/api-concepts.md +++ b/content/en/docs/reference/using-api/api-concepts.md @@ -620,7 +620,7 @@ should have the same flag setting. ## Resource Versions -Resource versions are strings that identify the server's internal version of an object. Resource versions can used by clients to determine when objects have changed, or to express data consistency requirements when getting, listing and watching resources. Resource versions must be treated as opaque by clients and passed unmodified back to the server. For example, clients must not assume resource versions are numeric, and must not compare two resource versions for greater-than or less-than relationships. +Resource versions are strings that identify the server's internal version of an object. Resource versions can be used by clients to determine when objects have changed, or to express data consistency requirements when getting, listing and watching resources. Resource versions must be treated as opaque by clients and passed unmodified back to the server. For example, clients must not assume resource versions are numeric, and may only compare two resource version for equality (i.e. must not compare resource versions for greater-than or less-than relationships). ### ResourceVersion in metadata