From ffd843ba8f262fca8f93517f636fccec043b50f9 Mon Sep 17 00:00:00 2001 From: Christopher Tauchen Date: Fri, 6 Dec 2024 15:50:53 +0000 Subject: [PATCH] Fixes bad punctuation pattern --- .../networking/configuring/advertise-service-ips.mdx | 6 +++--- calico-cloud/release-notes/index.mdx | 8 ++++---- calico-cloud/visibility/packetcapture.mdx | 2 +- .../networking/configuring/advertise-service-ips.mdx | 6 +++--- .../version-20-1/release-notes/index.mdx | 8 ++++---- .../version-20-1/visibility/packetcapture.mdx | 2 +- .../networking/configuring/advertise-service-ips.mdx | 6 +++--- .../version-20-2/release-notes/index.mdx | 8 ++++---- .../version-20-2/visibility/packetcapture.mdx | 2 +- calico-enterprise/getting-started/bare-metal/about.mdx | 2 +- .../networking/configuring/advertise-service-ips.mdx | 6 +++--- calico-enterprise/visibility/packetcapture.mdx | 2 +- .../version-3.17/getting-started/bare-metal/about.mdx | 2 +- .../networking/configuring/advertise-service-ips.mdx | 6 +++--- .../version-3.17/visibility/packetcapture.mdx | 2 +- .../version-3.18-2/getting-started/bare-metal/about.mdx | 2 +- .../networking/configuring/advertise-service-ips.mdx | 6 +++--- .../version-3.18-2/visibility/packetcapture.mdx | 2 +- .../version-3.19-2/getting-started/bare-metal/about.mdx | 2 +- .../networking/configuring/advertise-service-ips.mdx | 6 +++--- .../version-3.19-2/visibility/packetcapture.mdx | 2 +- .../version-3.20-1/getting-started/bare-metal/about.mdx | 2 +- .../networking/configuring/advertise-service-ips.mdx | 6 +++--- .../version-3.20-1/visibility/packetcapture.mdx | 2 +- .../version-3.20-2/getting-started/bare-metal/about.mdx | 2 +- .../networking/configuring/advertise-service-ips.mdx | 6 +++--- .../version-3.20-2/visibility/packetcapture.mdx | 2 +- calico/getting-started/bare-metal/about.mdx | 2 +- calico/networking/configuring/advertise-service-ips.mdx | 6 +++--- .../version-3.26/getting-started/bare-metal/about.mdx | 2 +- .../networking/configuring/advertise-service-ips.mdx | 6 +++--- .../version-3.27/getting-started/bare-metal/about.mdx | 2 +- .../networking/configuring/advertise-service-ips.mdx | 6 +++--- .../version-3.28/getting-started/bare-metal/about.mdx | 2 +- .../networking/configuring/advertise-service-ips.mdx | 6 +++--- .../version-3.29/getting-started/bare-metal/about.mdx | 2 +- .../networking/configuring/advertise-service-ips.mdx | 6 +++--- 37 files changed, 74 insertions(+), 74 deletions(-) diff --git a/calico-cloud/networking/configuring/advertise-service-ips.mdx b/calico-cloud/networking/configuring/advertise-service-ips.mdx index a0b8b0a654..748840379c 100644 --- a/calico-cloud/networking/configuring/advertise-service-ips.mdx +++ b/calico-cloud/networking/configuring/advertise-service-ips.mdx @@ -116,7 +116,7 @@ If your $[prodname] deployment is configured to peer with BGP routers outside th EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). :::note @@ -179,7 +179,7 @@ You will still need to enable service cluster IP advertisement via BGP configura EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). 1. When configuring a Kubernetes service that you want to be reachable via an external IP, specify that external IP in the service's `externalIPs` field. @@ -219,7 +219,7 @@ The following steps will configure $[prodname] to advertise Service `status.Load EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). Service LoadBalancer address allocation is outside the current scope of $[prodname], but can be implemented with an external controller. You can build your own, or use a third-party implementation like the MetalLB project. diff --git a/calico-cloud/release-notes/index.mdx b/calico-cloud/release-notes/index.mdx index 1352f246ba..5776d06d00 100644 --- a/calico-cloud/release-notes/index.mdx +++ b/calico-cloud/release-notes/index.mdx @@ -714,7 +714,7 @@ Release of Container Threat Detection With Container Threat Detection, you can monitor container activity using eBPF. Enable this feature to receive alerts based on file and process activity for known malicious and suspicious behavior. Alert events can be viewed on the Alerts page in Manager UI. -To get started see, [Container Threat Detection](../threat/container-threat-detection.mdx) +To get started, see [Container Threat Detection](../threat/container-threat-detection.mdx) ## September 26, 2022 @@ -754,7 +754,7 @@ We've made it easier for platform operators to share Image Assurance scan result * Export one row per image or one row per image and CVE. * Export CSV or JSON files. -To get started see, [Image Assurance](../image-assurance). +To get started, see [Image Assurance](../image-assurance). ### Malware detection is GA @@ -765,7 +765,7 @@ Calico Cloud uses eBPF-based monitoring to log file hashes of programs running i If there's a match to known malware from our threat intelligence library, you receive an alert. You can view your alerts on the _Alerts_ page on Manager UI. -To get started see, [Malware Detection](../threat/container-threat-detection.mdx)) +To get started, see [Malware Detection](../threat/container-threat-detection.mdx)) ## July 27, 2022 @@ -849,4 +849,4 @@ The $[prodname] installation process will now require running a `kubectl apply` $[prodname] introduces Image Assurance in tech preview, enabling DevOps and platform teams to scan images in public and private registries, and images that are automatically discovered in connected clusters. Image Assurance provides a runtime view into risk, based on discovered vulnerabilities. It also offers admission controller policies to enforce how vulnerable images are used to create resources within Kubernetes. -To get started see, [Image Assurance](../image-assurance). +To get started, see [Image Assurance](../image-assurance). diff --git a/calico-cloud/visibility/packetcapture.mdx b/calico-cloud/visibility/packetcapture.mdx index bcf17b9511..c73d719379 100644 --- a/calico-cloud/visibility/packetcapture.mdx +++ b/calico-cloud/visibility/packetcapture.mdx @@ -36,7 +36,7 @@ Typically, when you troubleshoot microservices and applications for connectivity 1. Start/schedule a packet capture job in Service Graph (Manager UI) or the CLI. 1. After the capture is finished, download the packet capture files (known as `pcap` files), and import them into your analysis tool (for example, WireShark). -For a simple use case workflow see, [Faster troubleshooting of microservices, containers, and Kubernetes with Dynamic Packet Capture](https://www.tigera.io/blog/faster-troubleshooting-of-microservices-containers-and-kubernetes-with-dynamic-packet-capture/). +For a simple use case workflow, see [Faster troubleshooting of microservices, containers, and Kubernetes with Dynamic Packet Capture](https://www.tigera.io/blog/faster-troubleshooting-of-microservices-containers-and-kubernetes-with-dynamic-packet-capture/). ## Before you begin diff --git a/calico-cloud_versioned_docs/version-20-1/networking/configuring/advertise-service-ips.mdx b/calico-cloud_versioned_docs/version-20-1/networking/configuring/advertise-service-ips.mdx index a0b8b0a654..748840379c 100644 --- a/calico-cloud_versioned_docs/version-20-1/networking/configuring/advertise-service-ips.mdx +++ b/calico-cloud_versioned_docs/version-20-1/networking/configuring/advertise-service-ips.mdx @@ -116,7 +116,7 @@ If your $[prodname] deployment is configured to peer with BGP routers outside th EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). :::note @@ -179,7 +179,7 @@ You will still need to enable service cluster IP advertisement via BGP configura EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). 1. When configuring a Kubernetes service that you want to be reachable via an external IP, specify that external IP in the service's `externalIPs` field. @@ -219,7 +219,7 @@ The following steps will configure $[prodname] to advertise Service `status.Load EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). Service LoadBalancer address allocation is outside the current scope of $[prodname], but can be implemented with an external controller. You can build your own, or use a third-party implementation like the MetalLB project. diff --git a/calico-cloud_versioned_docs/version-20-1/release-notes/index.mdx b/calico-cloud_versioned_docs/version-20-1/release-notes/index.mdx index 3ac8d957de..13acdb3756 100644 --- a/calico-cloud_versioned_docs/version-20-1/release-notes/index.mdx +++ b/calico-cloud_versioned_docs/version-20-1/release-notes/index.mdx @@ -661,7 +661,7 @@ Release of Container Threat Detection With Container Threat Detection, you can monitor container activity using eBPF. Enable this feature to receive alerts based on file and process activity for known malicious and suspicious behavior. Alert events can be viewed on the Alerts page in Manager UI. -To get started see, [Container Threat Detection](../threat/container-threat-detection.mdx) +To get started, see [Container Threat Detection](../threat/container-threat-detection.mdx) ## September 26, 2022 @@ -701,7 +701,7 @@ We've made it easier for platform operators to share Image Assurance scan result * Export one row per image or one row per image and CVE. * Export CSV or JSON files. -To get started see, [Image Assurance](../image-assurance). +To get started, see [Image Assurance](../image-assurance). ### Malware detection is GA @@ -712,7 +712,7 @@ Calico Cloud uses eBPF-based monitoring to log file hashes of programs running i If there's a match to known malware from our threat intelligence library, you receive an alert. You can view your alerts on the _Alerts_ page on Manager UI. -To get started see, [Malware Detection](../threat/container-threat-detection.mdx)) +To get started, see [Malware Detection](../threat/container-threat-detection.mdx)) ## July 27, 2022 @@ -796,4 +796,4 @@ The $[prodname] installation process will now require running a `kubectl apply` $[prodname] introduces Image Assurance in tech preview, enabling DevOps and platform teams to scan images in public and private registries, and images that are automatically discovered in connected clusters. Image Assurance provides a runtime view into risk, based on discovered vulnerabilities. It also offers admission controller policies to enforce how vulnerable images are used to create resources within Kubernetes. -To get started see, [Image Assurance](../image-assurance). +To get started, see [Image Assurance](../image-assurance). diff --git a/calico-cloud_versioned_docs/version-20-1/visibility/packetcapture.mdx b/calico-cloud_versioned_docs/version-20-1/visibility/packetcapture.mdx index bcf17b9511..c73d719379 100644 --- a/calico-cloud_versioned_docs/version-20-1/visibility/packetcapture.mdx +++ b/calico-cloud_versioned_docs/version-20-1/visibility/packetcapture.mdx @@ -36,7 +36,7 @@ Typically, when you troubleshoot microservices and applications for connectivity 1. Start/schedule a packet capture job in Service Graph (Manager UI) or the CLI. 1. After the capture is finished, download the packet capture files (known as `pcap` files), and import them into your analysis tool (for example, WireShark). -For a simple use case workflow see, [Faster troubleshooting of microservices, containers, and Kubernetes with Dynamic Packet Capture](https://www.tigera.io/blog/faster-troubleshooting-of-microservices-containers-and-kubernetes-with-dynamic-packet-capture/). +For a simple use case workflow, see [Faster troubleshooting of microservices, containers, and Kubernetes with Dynamic Packet Capture](https://www.tigera.io/blog/faster-troubleshooting-of-microservices-containers-and-kubernetes-with-dynamic-packet-capture/). ## Before you begin diff --git a/calico-cloud_versioned_docs/version-20-2/networking/configuring/advertise-service-ips.mdx b/calico-cloud_versioned_docs/version-20-2/networking/configuring/advertise-service-ips.mdx index a0b8b0a654..748840379c 100644 --- a/calico-cloud_versioned_docs/version-20-2/networking/configuring/advertise-service-ips.mdx +++ b/calico-cloud_versioned_docs/version-20-2/networking/configuring/advertise-service-ips.mdx @@ -116,7 +116,7 @@ If your $[prodname] deployment is configured to peer with BGP routers outside th EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). :::note @@ -179,7 +179,7 @@ You will still need to enable service cluster IP advertisement via BGP configura EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). 1. When configuring a Kubernetes service that you want to be reachable via an external IP, specify that external IP in the service's `externalIPs` field. @@ -219,7 +219,7 @@ The following steps will configure $[prodname] to advertise Service `status.Load EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). Service LoadBalancer address allocation is outside the current scope of $[prodname], but can be implemented with an external controller. You can build your own, or use a third-party implementation like the MetalLB project. diff --git a/calico-cloud_versioned_docs/version-20-2/release-notes/index.mdx b/calico-cloud_versioned_docs/version-20-2/release-notes/index.mdx index 79847caf44..f2747a7fbc 100644 --- a/calico-cloud_versioned_docs/version-20-2/release-notes/index.mdx +++ b/calico-cloud_versioned_docs/version-20-2/release-notes/index.mdx @@ -710,7 +710,7 @@ Release of Container Threat Detection With Container Threat Detection, you can monitor container activity using eBPF. Enable this feature to receive alerts based on file and process activity for known malicious and suspicious behavior. Alert events can be viewed on the Alerts page in Manager UI. -To get started see, [Container Threat Detection](../threat/container-threat-detection.mdx) +To get started, see [Container Threat Detection](../threat/container-threat-detection.mdx) ## September 26, 2022 @@ -750,7 +750,7 @@ We've made it easier for platform operators to share Image Assurance scan result * Export one row per image or one row per image and CVE. * Export CSV or JSON files. -To get started see, [Image Assurance](../image-assurance). +To get started, see [Image Assurance](../image-assurance). ### Malware detection is GA @@ -761,7 +761,7 @@ Calico Cloud uses eBPF-based monitoring to log file hashes of programs running i If there's a match to known malware from our threat intelligence library, you receive an alert. You can view your alerts on the _Alerts_ page on Manager UI. -To get started see, [Malware Detection](../threat/container-threat-detection.mdx)) +To get started, see [Malware Detection](../threat/container-threat-detection.mdx)) ## July 27, 2022 @@ -845,4 +845,4 @@ The $[prodname] installation process will now require running a `kubectl apply` $[prodname] introduces Image Assurance in tech preview, enabling DevOps and platform teams to scan images in public and private registries, and images that are automatically discovered in connected clusters. Image Assurance provides a runtime view into risk, based on discovered vulnerabilities. It also offers admission controller policies to enforce how vulnerable images are used to create resources within Kubernetes. -To get started see, [Image Assurance](../image-assurance). +To get started, see [Image Assurance](../image-assurance). diff --git a/calico-cloud_versioned_docs/version-20-2/visibility/packetcapture.mdx b/calico-cloud_versioned_docs/version-20-2/visibility/packetcapture.mdx index bcf17b9511..c73d719379 100644 --- a/calico-cloud_versioned_docs/version-20-2/visibility/packetcapture.mdx +++ b/calico-cloud_versioned_docs/version-20-2/visibility/packetcapture.mdx @@ -36,7 +36,7 @@ Typically, when you troubleshoot microservices and applications for connectivity 1. Start/schedule a packet capture job in Service Graph (Manager UI) or the CLI. 1. After the capture is finished, download the packet capture files (known as `pcap` files), and import them into your analysis tool (for example, WireShark). -For a simple use case workflow see, [Faster troubleshooting of microservices, containers, and Kubernetes with Dynamic Packet Capture](https://www.tigera.io/blog/faster-troubleshooting-of-microservices-containers-and-kubernetes-with-dynamic-packet-capture/). +For a simple use case workflow, see [Faster troubleshooting of microservices, containers, and Kubernetes with Dynamic Packet Capture](https://www.tigera.io/blog/faster-troubleshooting-of-microservices-containers-and-kubernetes-with-dynamic-packet-capture/). ## Before you begin diff --git a/calico-enterprise/getting-started/bare-metal/about.mdx b/calico-enterprise/getting-started/bare-metal/about.mdx index 5c4eed5210..7ebcbace70 100644 --- a/calico-enterprise/getting-started/bare-metal/about.mdx +++ b/calico-enterprise/getting-started/bare-metal/about.mdx @@ -24,7 +24,7 @@ In the following diagram, a Kubernetes cluster is running $[prodname] with netwo For non-cluster hosts and VMs, you can secure host interfaces using **host endpoints**. Host endpoints can have labels that work the same as labels on pods/workload endpoints in Kubernetes. The advantage is that you can write network policy rules to apply to both workload endpoints and host endpoints using label selectors; where each selector can refer to the either type (or be a mix of the two). For example, you can easily write a global policy that applies to every host, VM, or pod that is running Calico. -To learn how to restrict traffic to/from hosts and VMs using Calico network policy see, [Protect hosts and VMs](../../network-policy/hosts/protect-hosts.mdx). +To learn how to restrict traffic to/from hosts and VMs using Calico network policy, see [Protect hosts and VMs](../../network-policy/hosts/protect-hosts.mdx). ## Before you begin diff --git a/calico-enterprise/networking/configuring/advertise-service-ips.mdx b/calico-enterprise/networking/configuring/advertise-service-ips.mdx index ad01f3792e..618746530e 100644 --- a/calico-enterprise/networking/configuring/advertise-service-ips.mdx +++ b/calico-enterprise/networking/configuring/advertise-service-ips.mdx @@ -116,7 +116,7 @@ If your $[prodname] deployment is configured to peer with BGP routers outside th EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). :::note @@ -179,7 +179,7 @@ You will still need to enable service cluster IP advertisement via BGP configura EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). 1. When configuring a Kubernetes service that you want to be reachable via an external IP, specify that external IP in the service's `externalIPs` field. @@ -219,7 +219,7 @@ The following steps will configure $[prodname] to advertise Service `status.Load EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). Service LoadBalancer address allocation is outside the current scope of $[prodname], but can be implemented with an external controller. You can build your own, or use a third-party implementation like the MetalLB project. diff --git a/calico-enterprise/visibility/packetcapture.mdx b/calico-enterprise/visibility/packetcapture.mdx index e0e53475dd..6ed187f0d9 100644 --- a/calico-enterprise/visibility/packetcapture.mdx +++ b/calico-enterprise/visibility/packetcapture.mdx @@ -36,7 +36,7 @@ Typically, when you troubleshoot microservices and applications for connectivity 1. Start/schedule a packet capture job in Service Graph (Manager UI) or the CLI. 1. After the capture is finished, download the packet capture files (known as `pcap` files), and import them into your analysis tool (for example, WireShark). -For a simple use case workflow see, [Faster troubleshooting of microservices, containers, and Kubernetes with Dynamic Packet Capture](https://www.tigera.io/blog/faster-troubleshooting-of-microservices-containers-and-kubernetes-with-dynamic-packet-capture/). +For a simple use case workflow, see [Faster troubleshooting of microservices, containers, and Kubernetes with Dynamic Packet Capture](https://www.tigera.io/blog/faster-troubleshooting-of-microservices-containers-and-kubernetes-with-dynamic-packet-capture/). ## Before you begin diff --git a/calico-enterprise_versioned_docs/version-3.17/getting-started/bare-metal/about.mdx b/calico-enterprise_versioned_docs/version-3.17/getting-started/bare-metal/about.mdx index d517de99dc..352cc5afc6 100644 --- a/calico-enterprise_versioned_docs/version-3.17/getting-started/bare-metal/about.mdx +++ b/calico-enterprise_versioned_docs/version-3.17/getting-started/bare-metal/about.mdx @@ -29,7 +29,7 @@ A non-cluster host is a computer that is running an application that is _not par For non-cluster hosts, you can secure host interfaces using **host endpoints**. Host endpoints can have labels, and work the same as labels on pods/workload endpoints. The advantage is that you can write network policy rules to apply to both workload endpoints and host endpoints using label selectors; where each selector can refer to the either type (or be a mix of the two). For example, you can write a cluster-wide policy for non-cluster hosts that is immediately applied to every host. -To learn how to restrict traffic to/from hosts and VMs using $[prodname] network policy see, [Protect hosts](../../network-policy/hosts/protect-hosts.mdx). +To learn how to restrict traffic to/from hosts and VMs using $[prodname] network policy, see [Protect hosts](../../network-policy/hosts/protect-hosts.mdx). ## Before you begin diff --git a/calico-enterprise_versioned_docs/version-3.17/networking/configuring/advertise-service-ips.mdx b/calico-enterprise_versioned_docs/version-3.17/networking/configuring/advertise-service-ips.mdx index ad01f3792e..618746530e 100644 --- a/calico-enterprise_versioned_docs/version-3.17/networking/configuring/advertise-service-ips.mdx +++ b/calico-enterprise_versioned_docs/version-3.17/networking/configuring/advertise-service-ips.mdx @@ -116,7 +116,7 @@ If your $[prodname] deployment is configured to peer with BGP routers outside th EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). :::note @@ -179,7 +179,7 @@ You will still need to enable service cluster IP advertisement via BGP configura EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). 1. When configuring a Kubernetes service that you want to be reachable via an external IP, specify that external IP in the service's `externalIPs` field. @@ -219,7 +219,7 @@ The following steps will configure $[prodname] to advertise Service `status.Load EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). Service LoadBalancer address allocation is outside the current scope of $[prodname], but can be implemented with an external controller. You can build your own, or use a third-party implementation like the MetalLB project. diff --git a/calico-enterprise_versioned_docs/version-3.17/visibility/packetcapture.mdx b/calico-enterprise_versioned_docs/version-3.17/visibility/packetcapture.mdx index 53758de6c4..8f040a1191 100644 --- a/calico-enterprise_versioned_docs/version-3.17/visibility/packetcapture.mdx +++ b/calico-enterprise_versioned_docs/version-3.17/visibility/packetcapture.mdx @@ -36,7 +36,7 @@ Typically, when you troubleshoot microservices and applications for connectivity 1. Start/schedule a packet capture job in Service Graph (Manager UI) or the CLI. 1. After the capture is finished, download the packet capture files (known as `pcap` files), and import them into your analysis tool (for example, WireShark). -For a simple use case workflow see, [Faster troubleshooting of microservices, containers, and Kubernetes with Dynamic Packet Capture](https://www.tigera.io/blog/faster-troubleshooting-of-microservices-containers-and-kubernetes-with-dynamic-packet-capture/). +For a simple use case workflow, see [Faster troubleshooting of microservices, containers, and Kubernetes with Dynamic Packet Capture](https://www.tigera.io/blog/faster-troubleshooting-of-microservices-containers-and-kubernetes-with-dynamic-packet-capture/). ## Before you begin diff --git a/calico-enterprise_versioned_docs/version-3.18-2/getting-started/bare-metal/about.mdx b/calico-enterprise_versioned_docs/version-3.18-2/getting-started/bare-metal/about.mdx index 5e4426931b..9387187423 100644 --- a/calico-enterprise_versioned_docs/version-3.18-2/getting-started/bare-metal/about.mdx +++ b/calico-enterprise_versioned_docs/version-3.18-2/getting-started/bare-metal/about.mdx @@ -29,7 +29,7 @@ A non-cluster host is a computer that is running an application that is _not par For non-cluster hosts, you can secure host interfaces using **host endpoints**. Host endpoints can have labels, and work the same as labels on pods/workload endpoints. The advantage is that you can write network policy rules to apply to both workload endpoints and host endpoints using label selectors; where each selector can refer to the either type (or be a mix of the two). For example, you can write a cluster-wide policy for non-cluster hosts that is immediately applied to every host. -To learn how to restrict traffic to/from hosts and VMs using $[prodname] network policy see, [Protect hosts](../../network-policy/hosts/protect-hosts.mdx). +To learn how to restrict traffic to/from hosts and VMs using $[prodname] network policy, see [Protect hosts](../../network-policy/hosts/protect-hosts.mdx). ## Before you begin diff --git a/calico-enterprise_versioned_docs/version-3.18-2/networking/configuring/advertise-service-ips.mdx b/calico-enterprise_versioned_docs/version-3.18-2/networking/configuring/advertise-service-ips.mdx index ad01f3792e..618746530e 100644 --- a/calico-enterprise_versioned_docs/version-3.18-2/networking/configuring/advertise-service-ips.mdx +++ b/calico-enterprise_versioned_docs/version-3.18-2/networking/configuring/advertise-service-ips.mdx @@ -116,7 +116,7 @@ If your $[prodname] deployment is configured to peer with BGP routers outside th EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). :::note @@ -179,7 +179,7 @@ You will still need to enable service cluster IP advertisement via BGP configura EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). 1. When configuring a Kubernetes service that you want to be reachable via an external IP, specify that external IP in the service's `externalIPs` field. @@ -219,7 +219,7 @@ The following steps will configure $[prodname] to advertise Service `status.Load EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). Service LoadBalancer address allocation is outside the current scope of $[prodname], but can be implemented with an external controller. You can build your own, or use a third-party implementation like the MetalLB project. diff --git a/calico-enterprise_versioned_docs/version-3.18-2/visibility/packetcapture.mdx b/calico-enterprise_versioned_docs/version-3.18-2/visibility/packetcapture.mdx index 53758de6c4..8f040a1191 100644 --- a/calico-enterprise_versioned_docs/version-3.18-2/visibility/packetcapture.mdx +++ b/calico-enterprise_versioned_docs/version-3.18-2/visibility/packetcapture.mdx @@ -36,7 +36,7 @@ Typically, when you troubleshoot microservices and applications for connectivity 1. Start/schedule a packet capture job in Service Graph (Manager UI) or the CLI. 1. After the capture is finished, download the packet capture files (known as `pcap` files), and import them into your analysis tool (for example, WireShark). -For a simple use case workflow see, [Faster troubleshooting of microservices, containers, and Kubernetes with Dynamic Packet Capture](https://www.tigera.io/blog/faster-troubleshooting-of-microservices-containers-and-kubernetes-with-dynamic-packet-capture/). +For a simple use case workflow, see [Faster troubleshooting of microservices, containers, and Kubernetes with Dynamic Packet Capture](https://www.tigera.io/blog/faster-troubleshooting-of-microservices-containers-and-kubernetes-with-dynamic-packet-capture/). ## Before you begin diff --git a/calico-enterprise_versioned_docs/version-3.19-2/getting-started/bare-metal/about.mdx b/calico-enterprise_versioned_docs/version-3.19-2/getting-started/bare-metal/about.mdx index 21aa067921..dcab1b2658 100644 --- a/calico-enterprise_versioned_docs/version-3.19-2/getting-started/bare-metal/about.mdx +++ b/calico-enterprise_versioned_docs/version-3.19-2/getting-started/bare-metal/about.mdx @@ -29,7 +29,7 @@ A non-cluster host is a computer that is running an application that is _not par For non-cluster hosts, you can secure host interfaces using **host endpoints**. Host endpoints can have labels, and work the same as labels on pods/workload endpoints. The advantage is that you can write network policy rules to apply to both workload endpoints and host endpoints using label selectors; where each selector can refer to the either type (or be a mix of the two). For example, you can write a cluster-wide policy for non-cluster hosts that is immediately applied to every host. -To learn how to restrict traffic to/from hosts and VMs using $[prodname] network policy see, [Protect hosts](../../network-policy/hosts/protect-hosts.mdx). +To learn how to restrict traffic to/from hosts and VMs using $[prodname] network policy, see [Protect hosts](../../network-policy/hosts/protect-hosts.mdx). ## Before you begin diff --git a/calico-enterprise_versioned_docs/version-3.19-2/networking/configuring/advertise-service-ips.mdx b/calico-enterprise_versioned_docs/version-3.19-2/networking/configuring/advertise-service-ips.mdx index ad01f3792e..618746530e 100644 --- a/calico-enterprise_versioned_docs/version-3.19-2/networking/configuring/advertise-service-ips.mdx +++ b/calico-enterprise_versioned_docs/version-3.19-2/networking/configuring/advertise-service-ips.mdx @@ -116,7 +116,7 @@ If your $[prodname] deployment is configured to peer with BGP routers outside th EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). :::note @@ -179,7 +179,7 @@ You will still need to enable service cluster IP advertisement via BGP configura EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). 1. When configuring a Kubernetes service that you want to be reachable via an external IP, specify that external IP in the service's `externalIPs` field. @@ -219,7 +219,7 @@ The following steps will configure $[prodname] to advertise Service `status.Load EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). Service LoadBalancer address allocation is outside the current scope of $[prodname], but can be implemented with an external controller. You can build your own, or use a third-party implementation like the MetalLB project. diff --git a/calico-enterprise_versioned_docs/version-3.19-2/visibility/packetcapture.mdx b/calico-enterprise_versioned_docs/version-3.19-2/visibility/packetcapture.mdx index 53758de6c4..8f040a1191 100644 --- a/calico-enterprise_versioned_docs/version-3.19-2/visibility/packetcapture.mdx +++ b/calico-enterprise_versioned_docs/version-3.19-2/visibility/packetcapture.mdx @@ -36,7 +36,7 @@ Typically, when you troubleshoot microservices and applications for connectivity 1. Start/schedule a packet capture job in Service Graph (Manager UI) or the CLI. 1. After the capture is finished, download the packet capture files (known as `pcap` files), and import them into your analysis tool (for example, WireShark). -For a simple use case workflow see, [Faster troubleshooting of microservices, containers, and Kubernetes with Dynamic Packet Capture](https://www.tigera.io/blog/faster-troubleshooting-of-microservices-containers-and-kubernetes-with-dynamic-packet-capture/). +For a simple use case workflow, see [Faster troubleshooting of microservices, containers, and Kubernetes with Dynamic Packet Capture](https://www.tigera.io/blog/faster-troubleshooting-of-microservices-containers-and-kubernetes-with-dynamic-packet-capture/). ## Before you begin diff --git a/calico-enterprise_versioned_docs/version-3.20-1/getting-started/bare-metal/about.mdx b/calico-enterprise_versioned_docs/version-3.20-1/getting-started/bare-metal/about.mdx index aabf2b8521..68a7241124 100644 --- a/calico-enterprise_versioned_docs/version-3.20-1/getting-started/bare-metal/about.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-1/getting-started/bare-metal/about.mdx @@ -29,7 +29,7 @@ A non-cluster host is a computer that is running an application that is _not par For non-cluster hosts, you can secure host interfaces using **host endpoints**. Host endpoints can have labels, and work the same as labels on pods/workload endpoints. The advantage is that you can write network policy rules to apply to both workload endpoints and host endpoints using label selectors; where each selector can refer to the either type (or be a mix of the two). For example, you can write a cluster-wide policy for non-cluster hosts that is immediately applied to every host. -To learn how to restrict traffic to/from hosts and VMs using $[prodname] network policy see, [Protect hosts](../../network-policy/hosts/protect-hosts.mdx). +To learn how to restrict traffic to/from hosts and VMs using $[prodname] network policy, see [Protect hosts](../../network-policy/hosts/protect-hosts.mdx). ## Before you begin diff --git a/calico-enterprise_versioned_docs/version-3.20-1/networking/configuring/advertise-service-ips.mdx b/calico-enterprise_versioned_docs/version-3.20-1/networking/configuring/advertise-service-ips.mdx index ad01f3792e..618746530e 100644 --- a/calico-enterprise_versioned_docs/version-3.20-1/networking/configuring/advertise-service-ips.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-1/networking/configuring/advertise-service-ips.mdx @@ -116,7 +116,7 @@ If your $[prodname] deployment is configured to peer with BGP routers outside th EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). :::note @@ -179,7 +179,7 @@ You will still need to enable service cluster IP advertisement via BGP configura EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). 1. When configuring a Kubernetes service that you want to be reachable via an external IP, specify that external IP in the service's `externalIPs` field. @@ -219,7 +219,7 @@ The following steps will configure $[prodname] to advertise Service `status.Load EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). Service LoadBalancer address allocation is outside the current scope of $[prodname], but can be implemented with an external controller. You can build your own, or use a third-party implementation like the MetalLB project. diff --git a/calico-enterprise_versioned_docs/version-3.20-1/visibility/packetcapture.mdx b/calico-enterprise_versioned_docs/version-3.20-1/visibility/packetcapture.mdx index e0e53475dd..6ed187f0d9 100644 --- a/calico-enterprise_versioned_docs/version-3.20-1/visibility/packetcapture.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-1/visibility/packetcapture.mdx @@ -36,7 +36,7 @@ Typically, when you troubleshoot microservices and applications for connectivity 1. Start/schedule a packet capture job in Service Graph (Manager UI) or the CLI. 1. After the capture is finished, download the packet capture files (known as `pcap` files), and import them into your analysis tool (for example, WireShark). -For a simple use case workflow see, [Faster troubleshooting of microservices, containers, and Kubernetes with Dynamic Packet Capture](https://www.tigera.io/blog/faster-troubleshooting-of-microservices-containers-and-kubernetes-with-dynamic-packet-capture/). +For a simple use case workflow, see [Faster troubleshooting of microservices, containers, and Kubernetes with Dynamic Packet Capture](https://www.tigera.io/blog/faster-troubleshooting-of-microservices-containers-and-kubernetes-with-dynamic-packet-capture/). ## Before you begin diff --git a/calico-enterprise_versioned_docs/version-3.20-2/getting-started/bare-metal/about.mdx b/calico-enterprise_versioned_docs/version-3.20-2/getting-started/bare-metal/about.mdx index 5c4eed5210..7ebcbace70 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/getting-started/bare-metal/about.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/getting-started/bare-metal/about.mdx @@ -24,7 +24,7 @@ In the following diagram, a Kubernetes cluster is running $[prodname] with netwo For non-cluster hosts and VMs, you can secure host interfaces using **host endpoints**. Host endpoints can have labels that work the same as labels on pods/workload endpoints in Kubernetes. The advantage is that you can write network policy rules to apply to both workload endpoints and host endpoints using label selectors; where each selector can refer to the either type (or be a mix of the two). For example, you can easily write a global policy that applies to every host, VM, or pod that is running Calico. -To learn how to restrict traffic to/from hosts and VMs using Calico network policy see, [Protect hosts and VMs](../../network-policy/hosts/protect-hosts.mdx). +To learn how to restrict traffic to/from hosts and VMs using Calico network policy, see [Protect hosts and VMs](../../network-policy/hosts/protect-hosts.mdx). ## Before you begin diff --git a/calico-enterprise_versioned_docs/version-3.20-2/networking/configuring/advertise-service-ips.mdx b/calico-enterprise_versioned_docs/version-3.20-2/networking/configuring/advertise-service-ips.mdx index ad01f3792e..618746530e 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/networking/configuring/advertise-service-ips.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/networking/configuring/advertise-service-ips.mdx @@ -116,7 +116,7 @@ If your $[prodname] deployment is configured to peer with BGP routers outside th EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). :::note @@ -179,7 +179,7 @@ You will still need to enable service cluster IP advertisement via BGP configura EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). 1. When configuring a Kubernetes service that you want to be reachable via an external IP, specify that external IP in the service's `externalIPs` field. @@ -219,7 +219,7 @@ The following steps will configure $[prodname] to advertise Service `status.Load EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). Service LoadBalancer address allocation is outside the current scope of $[prodname], but can be implemented with an external controller. You can build your own, or use a third-party implementation like the MetalLB project. diff --git a/calico-enterprise_versioned_docs/version-3.20-2/visibility/packetcapture.mdx b/calico-enterprise_versioned_docs/version-3.20-2/visibility/packetcapture.mdx index e0e53475dd..6ed187f0d9 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/visibility/packetcapture.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/visibility/packetcapture.mdx @@ -36,7 +36,7 @@ Typically, when you troubleshoot microservices and applications for connectivity 1. Start/schedule a packet capture job in Service Graph (Manager UI) or the CLI. 1. After the capture is finished, download the packet capture files (known as `pcap` files), and import them into your analysis tool (for example, WireShark). -For a simple use case workflow see, [Faster troubleshooting of microservices, containers, and Kubernetes with Dynamic Packet Capture](https://www.tigera.io/blog/faster-troubleshooting-of-microservices-containers-and-kubernetes-with-dynamic-packet-capture/). +For a simple use case workflow, see [Faster troubleshooting of microservices, containers, and Kubernetes with Dynamic Packet Capture](https://www.tigera.io/blog/faster-troubleshooting-of-microservices-containers-and-kubernetes-with-dynamic-packet-capture/). ## Before you begin diff --git a/calico/getting-started/bare-metal/about.mdx b/calico/getting-started/bare-metal/about.mdx index cf8ab53d62..6f91bc16d4 100644 --- a/calico/getting-started/bare-metal/about.mdx +++ b/calico/getting-started/bare-metal/about.mdx @@ -18,7 +18,7 @@ Not all hosts in your environment run pods/workloads. You may have physical mach A **non-cluster host** is a computer that is running an application that is _not part of a Kubernetes cluster_. Using $[prodname] network policy, you can secure these host interfaces using **host endpoints**. Host endpoints can have labels, and work the same as labels on pods/workload endpoints. -The advantage is, you can write network policy rules to apply to both workload endpoints and host endpoints using label selectors; where each selector can refer to the either type (or be a mix of the two). For example, you can write a cluster-wide policy for non-cluster hosts that is immediately applied to every host. To learn how to restrict traffic to/from hosts and VMs using $[prodname] network policy see, [Protect hosts](../../network-policy/hosts/protect-hosts.mdx). +The advantage is, you can write network policy rules to apply to both workload endpoints and host endpoints using label selectors; where each selector can refer to the either type (or be a mix of the two). For example, you can write a cluster-wide policy for non-cluster hosts that is immediately applied to every host. To learn how to restrict traffic to/from hosts and VMs using $[prodname] network policy, see [Protect hosts](../../network-policy/hosts/protect-hosts.mdx). If you are using the etcd3 database, you can also install $[prodname] with networking as described below. diff --git a/calico/networking/configuring/advertise-service-ips.mdx b/calico/networking/configuring/advertise-service-ips.mdx index f5860c256d..58d7693bd6 100644 --- a/calico/networking/configuring/advertise-service-ips.mdx +++ b/calico/networking/configuring/advertise-service-ips.mdx @@ -113,7 +113,7 @@ If your $[prodname] deployment is configured to peer with BGP routers outside th EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). :::note @@ -159,7 +159,7 @@ deprecated CALICO_ADVERTISE_CLUSTER_IPS with BGPConfiguration. EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). ### Advertise service load balancer IP addresses @@ -197,7 +197,7 @@ The following steps will configure $[prodname] to advertise Service `status.Load EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). Service LoadBalancer address allocation is outside the current scope of $[prodname], but can be implemented with an external controller. You can build your own, or use a third-party implementation like the MetalLB project. diff --git a/calico_versioned_docs/version-3.26/getting-started/bare-metal/about.mdx b/calico_versioned_docs/version-3.26/getting-started/bare-metal/about.mdx index cf8ab53d62..6f91bc16d4 100644 --- a/calico_versioned_docs/version-3.26/getting-started/bare-metal/about.mdx +++ b/calico_versioned_docs/version-3.26/getting-started/bare-metal/about.mdx @@ -18,7 +18,7 @@ Not all hosts in your environment run pods/workloads. You may have physical mach A **non-cluster host** is a computer that is running an application that is _not part of a Kubernetes cluster_. Using $[prodname] network policy, you can secure these host interfaces using **host endpoints**. Host endpoints can have labels, and work the same as labels on pods/workload endpoints. -The advantage is, you can write network policy rules to apply to both workload endpoints and host endpoints using label selectors; where each selector can refer to the either type (or be a mix of the two). For example, you can write a cluster-wide policy for non-cluster hosts that is immediately applied to every host. To learn how to restrict traffic to/from hosts and VMs using $[prodname] network policy see, [Protect hosts](../../network-policy/hosts/protect-hosts.mdx). +The advantage is, you can write network policy rules to apply to both workload endpoints and host endpoints using label selectors; where each selector can refer to the either type (or be a mix of the two). For example, you can write a cluster-wide policy for non-cluster hosts that is immediately applied to every host. To learn how to restrict traffic to/from hosts and VMs using $[prodname] network policy, see [Protect hosts](../../network-policy/hosts/protect-hosts.mdx). If you are using the etcd3 database, you can also install $[prodname] with networking as described below. diff --git a/calico_versioned_docs/version-3.26/networking/configuring/advertise-service-ips.mdx b/calico_versioned_docs/version-3.26/networking/configuring/advertise-service-ips.mdx index 8d93b1a5fb..05fe6e6d30 100644 --- a/calico_versioned_docs/version-3.26/networking/configuring/advertise-service-ips.mdx +++ b/calico_versioned_docs/version-3.26/networking/configuring/advertise-service-ips.mdx @@ -113,7 +113,7 @@ If your $[prodname] deployment is configured to peer with BGP routers outside th EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). :::note @@ -159,7 +159,7 @@ deprecated CALICO_ADVERTISE_CLUSTER_IPS with BGPConfiguration. EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). ### Advertise service load balancer IP addresses @@ -197,7 +197,7 @@ The following steps will configure $[prodname] to advertise Service `status.Load EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). Service LoadBalancer address allocation is outside the current scope of $[prodname], but can be implemented with an external controller. You can build your own, or use a third-party implementation like the MetalLB project. diff --git a/calico_versioned_docs/version-3.27/getting-started/bare-metal/about.mdx b/calico_versioned_docs/version-3.27/getting-started/bare-metal/about.mdx index cf8ab53d62..6f91bc16d4 100644 --- a/calico_versioned_docs/version-3.27/getting-started/bare-metal/about.mdx +++ b/calico_versioned_docs/version-3.27/getting-started/bare-metal/about.mdx @@ -18,7 +18,7 @@ Not all hosts in your environment run pods/workloads. You may have physical mach A **non-cluster host** is a computer that is running an application that is _not part of a Kubernetes cluster_. Using $[prodname] network policy, you can secure these host interfaces using **host endpoints**. Host endpoints can have labels, and work the same as labels on pods/workload endpoints. -The advantage is, you can write network policy rules to apply to both workload endpoints and host endpoints using label selectors; where each selector can refer to the either type (or be a mix of the two). For example, you can write a cluster-wide policy for non-cluster hosts that is immediately applied to every host. To learn how to restrict traffic to/from hosts and VMs using $[prodname] network policy see, [Protect hosts](../../network-policy/hosts/protect-hosts.mdx). +The advantage is, you can write network policy rules to apply to both workload endpoints and host endpoints using label selectors; where each selector can refer to the either type (or be a mix of the two). For example, you can write a cluster-wide policy for non-cluster hosts that is immediately applied to every host. To learn how to restrict traffic to/from hosts and VMs using $[prodname] network policy, see [Protect hosts](../../network-policy/hosts/protect-hosts.mdx). If you are using the etcd3 database, you can also install $[prodname] with networking as described below. diff --git a/calico_versioned_docs/version-3.27/networking/configuring/advertise-service-ips.mdx b/calico_versioned_docs/version-3.27/networking/configuring/advertise-service-ips.mdx index f5860c256d..58d7693bd6 100644 --- a/calico_versioned_docs/version-3.27/networking/configuring/advertise-service-ips.mdx +++ b/calico_versioned_docs/version-3.27/networking/configuring/advertise-service-ips.mdx @@ -113,7 +113,7 @@ If your $[prodname] deployment is configured to peer with BGP routers outside th EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). :::note @@ -159,7 +159,7 @@ deprecated CALICO_ADVERTISE_CLUSTER_IPS with BGPConfiguration. EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). ### Advertise service load balancer IP addresses @@ -197,7 +197,7 @@ The following steps will configure $[prodname] to advertise Service `status.Load EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). Service LoadBalancer address allocation is outside the current scope of $[prodname], but can be implemented with an external controller. You can build your own, or use a third-party implementation like the MetalLB project. diff --git a/calico_versioned_docs/version-3.28/getting-started/bare-metal/about.mdx b/calico_versioned_docs/version-3.28/getting-started/bare-metal/about.mdx index cf8ab53d62..6f91bc16d4 100644 --- a/calico_versioned_docs/version-3.28/getting-started/bare-metal/about.mdx +++ b/calico_versioned_docs/version-3.28/getting-started/bare-metal/about.mdx @@ -18,7 +18,7 @@ Not all hosts in your environment run pods/workloads. You may have physical mach A **non-cluster host** is a computer that is running an application that is _not part of a Kubernetes cluster_. Using $[prodname] network policy, you can secure these host interfaces using **host endpoints**. Host endpoints can have labels, and work the same as labels on pods/workload endpoints. -The advantage is, you can write network policy rules to apply to both workload endpoints and host endpoints using label selectors; where each selector can refer to the either type (or be a mix of the two). For example, you can write a cluster-wide policy for non-cluster hosts that is immediately applied to every host. To learn how to restrict traffic to/from hosts and VMs using $[prodname] network policy see, [Protect hosts](../../network-policy/hosts/protect-hosts.mdx). +The advantage is, you can write network policy rules to apply to both workload endpoints and host endpoints using label selectors; where each selector can refer to the either type (or be a mix of the two). For example, you can write a cluster-wide policy for non-cluster hosts that is immediately applied to every host. To learn how to restrict traffic to/from hosts and VMs using $[prodname] network policy, see [Protect hosts](../../network-policy/hosts/protect-hosts.mdx). If you are using the etcd3 database, you can also install $[prodname] with networking as described below. diff --git a/calico_versioned_docs/version-3.28/networking/configuring/advertise-service-ips.mdx b/calico_versioned_docs/version-3.28/networking/configuring/advertise-service-ips.mdx index f5860c256d..58d7693bd6 100644 --- a/calico_versioned_docs/version-3.28/networking/configuring/advertise-service-ips.mdx +++ b/calico_versioned_docs/version-3.28/networking/configuring/advertise-service-ips.mdx @@ -113,7 +113,7 @@ If your $[prodname] deployment is configured to peer with BGP routers outside th EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). :::note @@ -159,7 +159,7 @@ deprecated CALICO_ADVERTISE_CLUSTER_IPS with BGPConfiguration. EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). ### Advertise service load balancer IP addresses @@ -197,7 +197,7 @@ The following steps will configure $[prodname] to advertise Service `status.Load EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). Service LoadBalancer address allocation is outside the current scope of $[prodname], but can be implemented with an external controller. You can build your own, or use a third-party implementation like the MetalLB project. diff --git a/calico_versioned_docs/version-3.29/getting-started/bare-metal/about.mdx b/calico_versioned_docs/version-3.29/getting-started/bare-metal/about.mdx index cf8ab53d62..6f91bc16d4 100644 --- a/calico_versioned_docs/version-3.29/getting-started/bare-metal/about.mdx +++ b/calico_versioned_docs/version-3.29/getting-started/bare-metal/about.mdx @@ -18,7 +18,7 @@ Not all hosts in your environment run pods/workloads. You may have physical mach A **non-cluster host** is a computer that is running an application that is _not part of a Kubernetes cluster_. Using $[prodname] network policy, you can secure these host interfaces using **host endpoints**. Host endpoints can have labels, and work the same as labels on pods/workload endpoints. -The advantage is, you can write network policy rules to apply to both workload endpoints and host endpoints using label selectors; where each selector can refer to the either type (or be a mix of the two). For example, you can write a cluster-wide policy for non-cluster hosts that is immediately applied to every host. To learn how to restrict traffic to/from hosts and VMs using $[prodname] network policy see, [Protect hosts](../../network-policy/hosts/protect-hosts.mdx). +The advantage is, you can write network policy rules to apply to both workload endpoints and host endpoints using label selectors; where each selector can refer to the either type (or be a mix of the two). For example, you can write a cluster-wide policy for non-cluster hosts that is immediately applied to every host. To learn how to restrict traffic to/from hosts and VMs using $[prodname] network policy, see [Protect hosts](../../network-policy/hosts/protect-hosts.mdx). If you are using the etcd3 database, you can also install $[prodname] with networking as described below. diff --git a/calico_versioned_docs/version-3.29/networking/configuring/advertise-service-ips.mdx b/calico_versioned_docs/version-3.29/networking/configuring/advertise-service-ips.mdx index f5860c256d..58d7693bd6 100644 --- a/calico_versioned_docs/version-3.29/networking/configuring/advertise-service-ips.mdx +++ b/calico_versioned_docs/version-3.29/networking/configuring/advertise-service-ips.mdx @@ -113,7 +113,7 @@ If your $[prodname] deployment is configured to peer with BGP routers outside th EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). :::note @@ -159,7 +159,7 @@ deprecated CALICO_ADVERTISE_CLUSTER_IPS with BGPConfiguration. EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). ### Advertise service load balancer IP addresses @@ -197,7 +197,7 @@ The following steps will configure $[prodname] to advertise Service `status.Load EOF ``` - For help see, [BGP configuration resource](../../reference/resources/bgpconfig.mdx). + For help, see [BGP configuration resource](../../reference/resources/bgpconfig.mdx). Service LoadBalancer address allocation is outside the current scope of $[prodname], but can be implemented with an external controller. You can build your own, or use a third-party implementation like the MetalLB project.