From 021843aa079c08f1b62ec1858857efdee0ec16f9 Mon Sep 17 00:00:00 2001 From: Yetkin Timocin Date: Wed, 6 May 2026 14:37:28 -0700 Subject: [PATCH] docs: batch one-line typo and syntax fixes - affinities.md: use DoesNotExist (the correct LabelSelector operator) in place of NotExists in prose, matching the YAML example below. - crp.md: PickN affinity example, preference is a single struct, not a slice; remove leading dash and quote the label value. - kind.md: cleanup deletes configmap kf-cm (the name created earlier), not app. - on-prem.md: define MEMBER_CLUSTER_CONTEXT before first use in the Confirm-the-placement section, mirroring HUB_CLUSTER_CONTEXT. Closes #103 Closes #102 Closes #98 Closes #95 Signed-off-by: Yetkin Timocin --- content/en/docs/getting-started/kind.md | 2 +- content/en/docs/getting-started/on-prem.md | 3 +++ content/en/docs/how-tos/affinities.md | 4 ++-- content/en/docs/how-tos/crp.md | 6 +++--- 4 files changed, 9 insertions(+), 6 deletions(-) diff --git a/content/en/docs/getting-started/kind.md b/content/en/docs/getting-started/kind.md index c215eb03..e4b60df2 100644 --- a/content/en/docs/getting-started/kind.md +++ b/content/en/docs/getting-started/kind.md @@ -288,7 +288,7 @@ To remove all the resources you just created, run the commands below: kubectl delete crp sample-crp kubectl delete ns kubefleet-sample -kubectl delete configmap app -n kubefleet-sample +kubectl delete configmap kf-cm -n kubefleet-sample ``` To uninstall KubeFleet components on the clusters, run the commands below: diff --git a/content/en/docs/getting-started/on-prem.md b/content/en/docs/getting-started/on-prem.md index 2ff1cb62..56af04ea 100644 --- a/content/en/docs/getting-started/on-prem.md +++ b/content/en/docs/getting-started/on-prem.md @@ -189,6 +189,9 @@ the completion. Now, log into the member clusters to confirm that the placement has been completed. ```sh +# Replace YOUR-MEMBER-CLUSTER-CONTEXT with the name of the kubeconfig context for one of +# the member clusters you joined above. +export MEMBER_CLUSTER_CONTEXT=YOUR-MEMBER-CLUSTER-CONTEXT kubectl config use-context $MEMBER_CLUSTER_CONTEXT kubectl get ns kubectl get configmap -n work diff --git a/content/en/docs/how-tos/affinities.md b/content/en/docs/how-tos/affinities.md index 883b89e8..0b157aa4 100644 --- a/content/en/docs/how-tos/affinities.md +++ b/content/en/docs/how-tos/affinities.md @@ -80,9 +80,9 @@ includes: * `In`: the cluster must have a label key with one of the listed values. * `NotIn`: the cluster must have a label key that is not associated with any of the listed values. * `Exists`: the cluster must have the label key present; any value is acceptable. - * `NotExists`: the cluster must not have the label key. + * `DoesNotExist`: the cluster must not have the label key. - If you plan to use `Exists` and/or `NotExists`, you must leave the list of values empty. + If you plan to use `Exists` and/or `DoesNotExist`, you must leave the list of values empty. Below is an example of `matchExpressions` affinity term using the `In` operator: diff --git a/content/en/docs/how-tos/crp.md b/content/en/docs/how-tos/crp.md index 9ba80c89..205eec20 100644 --- a/content/en/docs/how-tos/crp.md +++ b/content/en/docs/how-tos/crp.md @@ -266,9 +266,9 @@ spec: preferredDuringSchedulingIgnoredDuringExecution: - weight: 20 preference: - - labelSelector: - matchLabels: - critical-level: 1 + labelSelector: + matchLabels: + critical-level: "1" ``` The `ClusterResourcePlacement` object above will pick first clusters with the `critical-level=1`