From 93d742a0ee3be7548715a8d19f27b83f11731684 Mon Sep 17 00:00:00 2001 From: Ryan Zhang Date: Tue, 22 Oct 2024 19:09:20 -0700 Subject: [PATCH] fix typo --- ...t.kubernetes-fleet.io_clusterresourcestagedupdateruns.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/config/crd/bases/placement.kubernetes-fleet.io_clusterresourcestagedupdateruns.yaml b/config/crd/bases/placement.kubernetes-fleet.io_clusterresourcestagedupdateruns.yaml index 8cff4e978..051e57a40 100644 --- a/config/crd/bases/placement.kubernetes-fleet.io_clusterresourcestagedupdateruns.yaml +++ b/config/crd/bases/placement.kubernetes-fleet.io_clusterresourcestagedupdateruns.yaml @@ -237,7 +237,7 @@ spec: Note that this strategy requires that Fleet keep the last applied configuration in the - annoation of an applied resource. If the object gets so large that apply ops can no longer + annotation of an applied resource. If the object gets so large that apply ops can no longer be executed, Fleet will switch to server-side apply. @@ -257,7 +257,7 @@ spec: * ReportDiff: Fleet will compare the desired state of a resource as kept in the hub cluster - with its current state (if appliable) on the member cluster side, and report any + with its current state (if applicable) on the member cluster side, and report any differences. No actual apply ops would be executed, and resources will be left alone as they are on the member clusters.