Skip to content

Fix missing words in cluster mesh docs #3062

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ctauchen merged 1 commit into from
Oct 7, 2026
Merged

Fix missing words in cluster mesh docs #3062

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion calico-cloud/multicluster/kubeconfig.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ Note: much like intra-cluster routing in $[prodname], cross-cluster routing can

### Generate credentials for cross-cluster resource synchronization
:::tip[mental model]
The basis of cluster mesh is the ability for a cluster connect to a remote cluster and sync data from it. This enables each $[prodname] cluster to have a view into the datastore that includes both local and remote cluster pods.
The basis of cluster mesh is the ability for a cluster to connect to a remote cluster and sync data from it. This enables each $[prodname] cluster to have a view into the datastore that includes both local and remote cluster pods.
:::

In this section, we will create a `kubeconfig` for each cluster. This `kubeconfig` is what other clusters will use to connect to a given cluster and synchronize data from it.
Expand Down
2 changes: 1 addition & 1 deletion calico-cloud/multicluster/overview.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ Utilize $[prodname] to establish cross-cluster connectivity.

At some point in your Kubernetes journey, you may have applications that need to access services and workloads running in another cluster.

By default, pods can only communicate with pods within the same cluster. Additionally, services and network policy only select pods from within the same cluster. $[prodname] can help overcome these barriers by forming a cluster mesh the following features:
By default, pods can only communicate with pods within the same cluster. Additionally, services and network policy only select pods from within the same cluster. $[prodname] can help overcome these barriers by forming a cluster mesh that provides the following features:
- **Federated endpoint identity**

Allow a local Kubernetes cluster to include the workload endpoints (pods) and host endpoints of a remote cluster in the calculation of local network policies applied on each node of the local cluster.
Expand Down
2 changes: 1 addition & 1 deletion calico-cloud_versioned_docs/version-23-2/multicluster/kubeconfig.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ Note: much like intra-cluster routing in $[prodname], cross-cluster routing can

### Generate credentials for cross-cluster resource synchronization
:::tip[mental model]
The basis of cluster mesh is the ability for a cluster connect to a remote cluster and sync data from it. This enables each $[prodname] cluster to have a view into the datastore that includes both local and remote cluster pods.
The basis of cluster mesh is the ability for a cluster to connect to a remote cluster and sync data from it. This enables each $[prodname] cluster to have a view into the datastore that includes both local and remote cluster pods.
:::

In this section, we will create a `kubeconfig` for each cluster. This `kubeconfig` is what other clusters will use to connect to a given cluster and synchronize data from it.
Expand Down
2 changes: 1 addition & 1 deletion calico-cloud_versioned_docs/version-23-2/multicluster/overview.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ Utilize $[prodname] to establish cross-cluster connectivity.

At some point in your Kubernetes journey, you may have applications that need to access services and workloads running in another cluster.

By default, pods can only communicate with pods within the same cluster. Additionally, services and network policy only select pods from within the same cluster. $[prodname] can help overcome these barriers by forming a cluster mesh the following features:
By default, pods can only communicate with pods within the same cluster. Additionally, services and network policy only select pods from within the same cluster. $[prodname] can help overcome these barriers by forming a cluster mesh that provides the following features:
- **Federated endpoint identity**

Allow a local Kubernetes cluster to include the workload endpoints (pods) and host endpoints of a remote cluster in the calculation of local network policies applied on each node of the local cluster.
Expand Down
2 changes: 1 addition & 1 deletion calico-enterprise/multicluster/federation/kubeconfig.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ Note: much like intra-cluster routing in $[prodname], cross-cluster routing can

### Generate credentials for cross-cluster resource synchronization
:::tip[mental model]
The basis of cluster mesh is the ability for a cluster connect to a remote cluster and sync data from it. This enables each $[prodname] cluster to have a view into the datastore that includes both local and remote cluster pods.
The basis of cluster mesh is the ability for a cluster to connect to a remote cluster and sync data from it. This enables each $[prodname] cluster to have a view into the datastore that includes both local and remote cluster pods.
:::

In this section, we will create a `kubeconfig` for each cluster. This `kubeconfig` is what other clusters will use to connect to a given cluster and synchronize data from it.
Expand Down
2 changes: 1 addition & 1 deletion calico-enterprise/multicluster/federation/overview.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ Utilize $[prodname] to establish cross-cluster connectivity.

At some point in your Kubernetes journey, you may have applications that need to access services and workloads running in another cluster.

By default, pods can only communicate with pods within the same cluster. Additionally, services and network policy only select pods from within the same cluster. $[prodname] can help overcome these barriers by forming a cluster mesh the following features:
By default, pods can only communicate with pods within the same cluster. Additionally, services and network policy only select pods from within the same cluster. $[prodname] can help overcome these barriers by forming a cluster mesh that provides the following features:
- **Federated endpoint identity**

Allow a local Kubernetes cluster to include the workload endpoints (pods) and host endpoints of a remote cluster in the calculation of local network policies applied on each node of the local cluster.
Expand Down
2 changes: 1 addition & 1 deletion ...enterprise_versioned_docs/version-3.21-2/multicluster/federation/kubeconfig.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ Note: much like intra-cluster routing in $[prodname], cross-cluster routing can

### Generate credentials for cross-cluster resource synchronization
:::tip[mental model]
The basis of cluster mesh is the ability for a cluster connect to a remote cluster and sync data from it. This enables each $[prodname] cluster to have a view into the datastore that includes both local and remote cluster pods.
The basis of cluster mesh is the ability for a cluster to connect to a remote cluster and sync data from it. This enables each $[prodname] cluster to have a view into the datastore that includes both local and remote cluster pods.
:::

In this section, we will create a `kubeconfig` for each cluster. This `kubeconfig` is what other clusters will use to connect to a given cluster and synchronize data from it.
Expand Down
2 changes: 1 addition & 1 deletion ...o-enterprise_versioned_docs/version-3.21-2/multicluster/federation/overview.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ Utilize $[prodname] to establish cross-cluster connectivity.

At some point in your Kubernetes journey, you may have applications that need to access services and workloads running in another cluster.

By default, pods can only communicate with pods within the same cluster. Additionally, services and network policy only select pods from within the same cluster. $[prodname] can help overcome these barriers by forming a cluster mesh the following features:
By default, pods can only communicate with pods within the same cluster. Additionally, services and network policy only select pods from within the same cluster. $[prodname] can help overcome these barriers by forming a cluster mesh that provides the following features:
- **Federated endpoint identity**

Allow a local Kubernetes cluster to include the workload endpoints (pods) and host endpoints of a remote cluster in the calculation of local network policies applied on each node of the local cluster.
Expand Down
2 changes: 1 addition & 1 deletion ...enterprise_versioned_docs/version-3.22-2/multicluster/federation/kubeconfig.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ Note: much like intra-cluster routing in $[prodname], cross-cluster routing can

### Generate credentials for cross-cluster resource synchronization
:::tip[mental model]
The basis of cluster mesh is the ability for a cluster connect to a remote cluster and sync data from it. This enables each $[prodname] cluster to have a view into the datastore that includes both local and remote cluster pods.
The basis of cluster mesh is the ability for a cluster to connect to a remote cluster and sync data from it. This enables each $[prodname] cluster to have a view into the datastore that includes both local and remote cluster pods.
:::

In this section, we will create a `kubeconfig` for each cluster. This `kubeconfig` is what other clusters will use to connect to a given cluster and synchronize data from it.
Expand Down
2 changes: 1 addition & 1 deletion ...o-enterprise_versioned_docs/version-3.22-2/multicluster/federation/overview.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ Utilize $[prodname] to establish cross-cluster connectivity.

At some point in your Kubernetes journey, you may have applications that need to access services and workloads running in another cluster.

By default, pods can only communicate with pods within the same cluster. Additionally, services and network policy only select pods from within the same cluster. $[prodname] can help overcome these barriers by forming a cluster mesh the following features:
By default, pods can only communicate with pods within the same cluster. Additionally, services and network policy only select pods from within the same cluster. $[prodname] can help overcome these barriers by forming a cluster mesh that provides the following features:
- **Federated endpoint identity**

Allow a local Kubernetes cluster to include the workload endpoints (pods) and host endpoints of a remote cluster in the calculation of local network policies applied on each node of the local cluster.
Expand Down
2 changes: 1 addition & 1 deletion ...enterprise_versioned_docs/version-3.23-2/multicluster/federation/kubeconfig.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ Note: much like intra-cluster routing in $[prodname], cross-cluster routing can

### Generate credentials for cross-cluster resource synchronization
:::tip[mental model]
The basis of cluster mesh is the ability for a cluster connect to a remote cluster and sync data from it. This enables each $[prodname] cluster to have a view into the datastore that includes both local and remote cluster pods.
The basis of cluster mesh is the ability for a cluster to connect to a remote cluster and sync data from it. This enables each $[prodname] cluster to have a view into the datastore that includes both local and remote cluster pods.
:::

In this section, we will create a `kubeconfig` for each cluster. This `kubeconfig` is what other clusters will use to connect to a given cluster and synchronize data from it.
Expand Down
2 changes: 1 addition & 1 deletion ...o-enterprise_versioned_docs/version-3.23-2/multicluster/federation/overview.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ Utilize $[prodname] to establish cross-cluster connectivity.

At some point in your Kubernetes journey, you may have applications that need to access services and workloads running in another cluster.

By default, pods can only communicate with pods within the same cluster. Additionally, services and network policy only select pods from within the same cluster. $[prodname] can help overcome these barriers by forming a cluster mesh the following features:
By default, pods can only communicate with pods within the same cluster. Additionally, services and network policy only select pods from within the same cluster. $[prodname] can help overcome these barriers by forming a cluster mesh that provides the following features:
- **Federated endpoint identity**

Allow a local Kubernetes cluster to include the workload endpoints (pods) and host endpoints of a remote cluster in the calculation of local network policies applied on each node of the local cluster.
Expand Down
2 changes: 1 addition & 1 deletion ...enterprise_versioned_docs/version-3.24-1/multicluster/federation/kubeconfig.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ Note: much like intra-cluster routing in $[prodname], cross-cluster routing can

### Generate credentials for cross-cluster resource synchronization
:::tip[mental model]
The basis of cluster mesh is the ability for a cluster connect to a remote cluster and sync data from it. This enables each $[prodname] cluster to have a view into the datastore that includes both local and remote cluster pods.
The basis of cluster mesh is the ability for a cluster to connect to a remote cluster and sync data from it. This enables each $[prodname] cluster to have a view into the datastore that includes both local and remote cluster pods.
:::

In this section, we will create a `kubeconfig` for each cluster. This `kubeconfig` is what other clusters will use to connect to a given cluster and synchronize data from it.
Expand Down
2 changes: 1 addition & 1 deletion ...o-enterprise_versioned_docs/version-3.24-1/multicluster/federation/overview.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ Utilize $[prodname] to establish cross-cluster connectivity.

At some point in your Kubernetes journey, you may have applications that need to access services and workloads running in another cluster.

By default, pods can only communicate with pods within the same cluster. Additionally, services and network policy only select pods from within the same cluster. $[prodname] can help overcome these barriers by forming a cluster mesh the following features:
By default, pods can only communicate with pods within the same cluster. Additionally, services and network policy only select pods from within the same cluster. $[prodname] can help overcome these barriers by forming a cluster mesh that provides the following features:
- **Federated endpoint identity**

Allow a local Kubernetes cluster to include the workload endpoints (pods) and host endpoints of a remote cluster in the calculation of local network policies applied on each node of the local cluster.
Expand Down
2 changes: 1 addition & 1 deletion ...enterprise_versioned_docs/version-3.24-2/multicluster/federation/kubeconfig.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ Note: much like intra-cluster routing in $[prodname], cross-cluster routing can

### Generate credentials for cross-cluster resource synchronization
:::tip[mental model]
The basis of cluster mesh is the ability for a cluster connect to a remote cluster and sync data from it. This enables each $[prodname] cluster to have a view into the datastore that includes both local and remote cluster pods.
The basis of cluster mesh is the ability for a cluster to connect to a remote cluster and sync data from it. This enables each $[prodname] cluster to have a view into the datastore that includes both local and remote cluster pods.
:::

In this section, we will create a `kubeconfig` for each cluster. This `kubeconfig` is what other clusters will use to connect to a given cluster and synchronize data from it.
Expand Down
2 changes: 1 addition & 1 deletion ...o-enterprise_versioned_docs/version-3.24-2/multicluster/federation/overview.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ Utilize $[prodname] to establish cross-cluster connectivity.

At some point in your Kubernetes journey, you may have applications that need to access services and workloads running in another cluster.

By default, pods can only communicate with pods within the same cluster. Additionally, services and network policy only select pods from within the same cluster. $[prodname] can help overcome these barriers by forming a cluster mesh the following features:
By default, pods can only communicate with pods within the same cluster. Additionally, services and network policy only select pods from within the same cluster. $[prodname] can help overcome these barriers by forming a cluster mesh that provides the following features:
- **Federated endpoint identity**

Allow a local Kubernetes cluster to include the workload endpoints (pods) and host endpoints of a remote cluster in the calculation of local network policies applied on each node of the local cluster.
Expand Down
Loading