MTU is the most recently observed value for pod network MTU. This may be an explicitly -configured value, or based on Calico’s native auto-detetion. +configured value, or based on Calico’s native auto-detection.
diff --git a/calico-cloud_versioned_docs/version-19-1/reference/installation/_api.mdx b/calico-cloud_versioned_docs/version-19-1/reference/installation/_api.mdx index eefffd5f38..845567a6ca 100644 --- a/calico-cloud_versioned_docs/version-19-1/reference/installation/_api.mdx +++ b/calico-cloud_versioned_docs/version-19-1/reference/installation/_api.mdx @@ -10078,7 +10078,7 @@ int32MTU is the most recently observed value for pod network MTU. This may be an explicitly -configured value, or based on Calico’s native auto-detetion. +configured value, or based on Calico’s native auto-detection.
diff --git a/calico-enterprise/reference/installation/_api.mdx b/calico-enterprise/reference/installation/_api.mdx index eefffd5f38..845567a6ca 100644 --- a/calico-enterprise/reference/installation/_api.mdx +++ b/calico-enterprise/reference/installation/_api.mdx @@ -10078,7 +10078,7 @@ int32MTU is the most recently observed value for pod network MTU. This may be an explicitly -configured value, or based on Calico’s native auto-detetion. +configured value, or based on Calico’s native auto-detection.
diff --git a/calico-enterprise_versioned_docs/version-3.16/reference/installation/_api.mdx b/calico-enterprise_versioned_docs/version-3.16/reference/installation/_api.mdx index 45031d13a1..823d0cbd24 100644 --- a/calico-enterprise_versioned_docs/version-3.16/reference/installation/_api.mdx +++ b/calico-enterprise_versioned_docs/version-3.16/reference/installation/_api.mdx @@ -8512,7 +8512,7 @@ int32MTU is the most recently observed value for pod network MTU. This may be an explicitly -configured value, or based on Calico’s native auto-detetion. +configured value, or based on Calico’s native auto-detection.
diff --git a/calico-enterprise_versioned_docs/version-3.17/reference/installation/_api.mdx b/calico-enterprise_versioned_docs/version-3.17/reference/installation/_api.mdx index 5871c5c14b..a00dd18e8d 100644 --- a/calico-enterprise_versioned_docs/version-3.17/reference/installation/_api.mdx +++ b/calico-enterprise_versioned_docs/version-3.17/reference/installation/_api.mdx @@ -9908,7 +9908,7 @@ int32MTU is the most recently observed value for pod network MTU. This may be an explicitly -configured value, or based on Calico’s native auto-detetion. +configured value, or based on Calico’s native auto-detection.
diff --git a/calico-enterprise_versioned_docs/version-3.18-2/reference/installation/_api.mdx b/calico-enterprise_versioned_docs/version-3.18-2/reference/installation/_api.mdx index 11bfe96cd2..c8ded3a8e5 100644 --- a/calico-enterprise_versioned_docs/version-3.18-2/reference/installation/_api.mdx +++ b/calico-enterprise_versioned_docs/version-3.18-2/reference/installation/_api.mdx @@ -10022,7 +10022,7 @@ int32MTU is the most recently observed value for pod network MTU. This may be an explicitly -configured value, or based on Calico’s native auto-detetion. +configured value, or based on Calico’s native auto-detection.
diff --git a/calico-enterprise_versioned_docs/version-3.18/reference/installation/_api.mdx b/calico-enterprise_versioned_docs/version-3.18/reference/installation/_api.mdx index aec96ca68a..859f292551 100644 --- a/calico-enterprise_versioned_docs/version-3.18/reference/installation/_api.mdx +++ b/calico-enterprise_versioned_docs/version-3.18/reference/installation/_api.mdx @@ -9231,7 +9231,7 @@ int32MTU is the most recently observed value for pod network MTU. This may be an explicitly -configured value, or based on Calico’s native auto-detetion. +configured value, or based on Calico’s native auto-detection.
diff --git a/calico-enterprise_versioned_docs/version-3.19-1/reference/installation/_api.mdx b/calico-enterprise_versioned_docs/version-3.19-1/reference/installation/_api.mdx index 172efe8ec7..5f9f766394 100644 --- a/calico-enterprise_versioned_docs/version-3.19-1/reference/installation/_api.mdx +++ b/calico-enterprise_versioned_docs/version-3.19-1/reference/installation/_api.mdx @@ -10342,7 +10342,7 @@ int32MTU is the most recently observed value for pod network MTU. This may be an explicitly -configured value, or based on Calico’s native auto-detetion. +configured value, or based on Calico’s native auto-detection.
diff --git a/calico/reference/installation/_api.mdx b/calico/reference/installation/_api.mdx index 5930c66358..b721f4f63c 100644 --- a/calico/reference/installation/_api.mdx +++ b/calico/reference/installation/_api.mdx @@ -7281,7 +7281,7 @@ int32MTU is the most recently observed value for pod network MTU. This may be an explicitly -configured value, or based on Calico’s native auto-detetion. +configured value, or based on Calico’s native auto-detection.
diff --git a/calico_versioned_docs/version-3.25/reference/installation/_api.mdx b/calico_versioned_docs/version-3.25/reference/installation/_api.mdx index c1f4d2fc75..3608da4916 100644 --- a/calico_versioned_docs/version-3.25/reference/installation/_api.mdx +++ b/calico_versioned_docs/version-3.25/reference/installation/_api.mdx @@ -5788,7 +5788,7 @@ int32MTU is the most recently observed value for pod network MTU. This may be an explicitly -configured value, or based on Calico’s native auto-detetion. +configured value, or based on Calico’s native auto-detection.
diff --git a/calico_versioned_docs/version-3.26/reference/installation/_api.mdx b/calico_versioned_docs/version-3.26/reference/installation/_api.mdx index 5754835c6e..dbc92e0066 100644 --- a/calico_versioned_docs/version-3.26/reference/installation/_api.mdx +++ b/calico_versioned_docs/version-3.26/reference/installation/_api.mdx @@ -6507,7 +6507,7 @@ int32MTU is the most recently observed value for pod network MTU. This may be an explicitly -configured value, or based on Calico’s native auto-detetion. +configured value, or based on Calico’s native auto-detection.
diff --git a/calico_versioned_docs/version-3.27/reference/installation/_api.mdx b/calico_versioned_docs/version-3.27/reference/installation/_api.mdx index 5930c66358..b721f4f63c 100644 --- a/calico_versioned_docs/version-3.27/reference/installation/_api.mdx +++ b/calico_versioned_docs/version-3.27/reference/installation/_api.mdx @@ -7281,7 +7281,7 @@ int32MTU is the most recently observed value for pod network MTU. This may be an explicitly -configured value, or based on Calico’s native auto-detetion. +configured value, or based on Calico’s native auto-detection.
From 9de95168f5a07550591921220f345937ebd73eed Mon Sep 17 00:00:00 2001 From: Josh Soref <2119212+jsoref@users.noreply.github.com> Date: Wed, 15 Nov 2023 18:51:48 -0500 Subject: [PATCH 14/55] whitespace: detection Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> --- calico-cloud/get-started/connect/operator-checklist.mdx | 2 +- .../version-19-1/get-started/connect/operator-checklist.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/calico-cloud/get-started/connect/operator-checklist.mdx b/calico-cloud/get-started/connect/operator-checklist.mdx index 7ac55c68bb..b1e1111a14 100644 --- a/calico-cloud/get-started/connect/operator-checklist.mdx +++ b/calico-cloud/get-started/connect/operator-checklist.mdx @@ -404,7 +404,7 @@ kubectl get tigerastatus | 2 | calico | TRUE | FALSE | FALSE | 11m | | 3 | cloud-core | TRUE | FALSE | FALSE | 11m | | 4 | compliance | TRUE | FALSE | FALSE | 9m39s | -| 5 | intrusion-detection | TRUE | FALSE | FALSE | 9m49s | +| 5 | intrusion-detection | TRUE | FALSE | FALSE | 9m49s | | 6 | log-collector | TRUE | FALSE | FALSE | 9m29s | | 7 | management-cluster-connection | TRUE | FALSE | FALSE | 9m54s | | 8 | monitor | TRUE | FALSE | FALSE | 11m | diff --git a/calico-cloud_versioned_docs/version-19-1/get-started/connect/operator-checklist.mdx b/calico-cloud_versioned_docs/version-19-1/get-started/connect/operator-checklist.mdx index 7ac55c68bb..b1e1111a14 100644 --- a/calico-cloud_versioned_docs/version-19-1/get-started/connect/operator-checklist.mdx +++ b/calico-cloud_versioned_docs/version-19-1/get-started/connect/operator-checklist.mdx @@ -404,7 +404,7 @@ kubectl get tigerastatus | 2 | calico | TRUE | FALSE | FALSE | 11m | | 3 | cloud-core | TRUE | FALSE | FALSE | 11m | | 4 | compliance | TRUE | FALSE | FALSE | 9m39s | -| 5 | intrusion-detection | TRUE | FALSE | FALSE | 9m49s | +| 5 | intrusion-detection | TRUE | FALSE | FALSE | 9m49s | | 6 | log-collector | TRUE | FALSE | FALSE | 9m29s | | 7 | management-cluster-connection | TRUE | FALSE | FALSE | 9m54s | | 8 | monitor | TRUE | FALSE | FALSE | 11m | From 22e14efbd0d6dc1d562714f6713a5129d37df0a6 Mon Sep 17 00:00:00 2001 From: Josh Soref <2119212+jsoref@users.noreply.github.com> Date: Wed, 15 Nov 2023 18:52:33 -0500 Subject: [PATCH 15/55] spelling: docusaurus Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> --- scripts/cc-next-preview-config.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/scripts/cc-next-preview-config.sh b/scripts/cc-next-preview-config.sh index 0da3b6411e..6ba8678b5f 100644 --- a/scripts/cc-next-preview-config.sh +++ b/scripts/cc-next-preview-config.sh @@ -1,7 +1,7 @@ #!/bin/bash -# This script makes changes to docusuarus.config.js. -# These changes make Docusuarus publish only version Next for each product doc set. +# This script makes changes to docusaurus.config.js. +# These changes make Docusaurus publish only version Next for each product doc set. sed -i "s/onBrokenLinks: 'throw'/onBrokenLinks: 'warn'/" docusaurus.config.js sed -i "s/onBrokenMarkdownLinks: 'throw'/onBrokenMarkdownLinks: 'warn'/" docusaurus.config.js From d1ea3fb9007789ec3314feeba5f0d9981b7721b2 Mon Sep 17 00:00:00 2001 From: Josh Soref <2119212+jsoref@users.noreply.github.com> Date: Thu, 21 Mar 2024 00:18:32 -0400 Subject: [PATCH 16/55] spelling: drop Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> --- calico-cloud/operations/monitor/metrics/recommended-metrics.mdx | 2 +- .../operations/monitor/metrics/recommended-metrics.mdx | 2 +- .../operations/monitor/metrics/recommended-metrics.mdx | 2 +- .../operations/monitor/metrics/recommended-metrics.mdx | 2 +- .../operations/monitor/metrics/recommended-metrics.mdx | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/calico-cloud/operations/monitor/metrics/recommended-metrics.mdx b/calico-cloud/operations/monitor/metrics/recommended-metrics.mdx index dbbe334843..2c2cd169cb 100644 --- a/calico-cloud/operations/monitor/metrics/recommended-metrics.mdx +++ b/calico-cloud/operations/monitor/metrics/recommended-metrics.mdx @@ -459,7 +459,7 @@ The following policy metrics are a separate endpoint exposed by Felix that are u | Metric |felix_logs_dropped
|
| Example value | felix_logs_dropped\{endpoint="metrics-port", instance="10.0.1.20:9091", job="felix-metrics-svc", namespace="calico-system", pod="calico-node-qzpkt", service="felix-metrics-svc"\} 0
|
| Explanation | The number of logs Felix has dropped. Note that this metric does not count flow-logs; it counts logs to stdout. |
-| Threshold value recommendation | Occasional drops are normal. Investigate if frop counters rapidily rise. |
+| Threshold value recommendation | Occasional drops are normal. Investigate if drop counters rapidily rise. |
| Threshold breach symptoms | Felix will drop logs if it cannot keep up with writing them out. These are ordinary code logs, not flow logs. Calico-node may be under resource constraints. |
| Threshold breach recommendations | Check CPU usage on calico-nodes and Kubernetes nodes. Increase resources if needed, and rollout restart calico-node(s) if needed. |
| Priority level | Optional. |
diff --git a/calico-cloud_versioned_docs/version-19-1/operations/monitor/metrics/recommended-metrics.mdx b/calico-cloud_versioned_docs/version-19-1/operations/monitor/metrics/recommended-metrics.mdx
index dbbe334843..2c2cd169cb 100644
--- a/calico-cloud_versioned_docs/version-19-1/operations/monitor/metrics/recommended-metrics.mdx
+++ b/calico-cloud_versioned_docs/version-19-1/operations/monitor/metrics/recommended-metrics.mdx
@@ -459,7 +459,7 @@ The following policy metrics are a separate endpoint exposed by Felix that are u
| Metric | felix_logs_dropped
|
| Example value | felix_logs_dropped\{endpoint="metrics-port", instance="10.0.1.20:9091", job="felix-metrics-svc", namespace="calico-system", pod="calico-node-qzpkt", service="felix-metrics-svc"\} 0
|
| Explanation | The number of logs Felix has dropped. Note that this metric does not count flow-logs; it counts logs to stdout. |
-| Threshold value recommendation | Occasional drops are normal. Investigate if frop counters rapidily rise. |
+| Threshold value recommendation | Occasional drops are normal. Investigate if drop counters rapidily rise. |
| Threshold breach symptoms | Felix will drop logs if it cannot keep up with writing them out. These are ordinary code logs, not flow logs. Calico-node may be under resource constraints. |
| Threshold breach recommendations | Check CPU usage on calico-nodes and Kubernetes nodes. Increase resources if needed, and rollout restart calico-node(s) if needed. |
| Priority level | Optional. |
diff --git a/calico-enterprise/operations/monitor/metrics/recommended-metrics.mdx b/calico-enterprise/operations/monitor/metrics/recommended-metrics.mdx
index 64a2713820..706a67b246 100644
--- a/calico-enterprise/operations/monitor/metrics/recommended-metrics.mdx
+++ b/calico-enterprise/operations/monitor/metrics/recommended-metrics.mdx
@@ -459,7 +459,7 @@ The following policy metrics are a separate endpoint exposed by Felix that are u
| Metric | felix_logs_dropped
|
| Example value | felix_logs_dropped\{endpoint="metrics-port", instance="10.0.1.20:9091", job="felix-metrics-svc", namespace="calico-system", pod="calico-node-qzpkt", service="felix-metrics-svc"\} 0
|
| Explanation | The number of logs Felix has dropped. Note that this metric does not count flow-logs; it counts logs to stdout. |
-| Threshold value recommendation | Occasional drops are normal. Investigate if frop counters rapidily rise. |
+| Threshold value recommendation | Occasional drops are normal. Investigate if drop counters rapidily rise. |
| Threshold breach symptoms | Felix will drop logs if it cannot keep up with writing them out. These are ordinary code logs, not flow logs. Calico-node may be under resource constraints. |
| Threshold breach recommendations | Check CPU usage on calico-nodes and Kubernetes nodes. Increase resources if needed, and rollout restart calico-node(s) if needed. |
| Priority level | Optional. |
diff --git a/calico-enterprise_versioned_docs/version-3.18-2/operations/monitor/metrics/recommended-metrics.mdx b/calico-enterprise_versioned_docs/version-3.18-2/operations/monitor/metrics/recommended-metrics.mdx
index 64a2713820..706a67b246 100644
--- a/calico-enterprise_versioned_docs/version-3.18-2/operations/monitor/metrics/recommended-metrics.mdx
+++ b/calico-enterprise_versioned_docs/version-3.18-2/operations/monitor/metrics/recommended-metrics.mdx
@@ -459,7 +459,7 @@ The following policy metrics are a separate endpoint exposed by Felix that are u
| Metric | felix_logs_dropped
|
| Example value | felix_logs_dropped\{endpoint="metrics-port", instance="10.0.1.20:9091", job="felix-metrics-svc", namespace="calico-system", pod="calico-node-qzpkt", service="felix-metrics-svc"\} 0
|
| Explanation | The number of logs Felix has dropped. Note that this metric does not count flow-logs; it counts logs to stdout. |
-| Threshold value recommendation | Occasional drops are normal. Investigate if frop counters rapidily rise. |
+| Threshold value recommendation | Occasional drops are normal. Investigate if drop counters rapidily rise. |
| Threshold breach symptoms | Felix will drop logs if it cannot keep up with writing them out. These are ordinary code logs, not flow logs. Calico-node may be under resource constraints. |
| Threshold breach recommendations | Check CPU usage on calico-nodes and Kubernetes nodes. Increase resources if needed, and rollout restart calico-node(s) if needed. |
| Priority level | Optional. |
diff --git a/calico-enterprise_versioned_docs/version-3.19-1/operations/monitor/metrics/recommended-metrics.mdx b/calico-enterprise_versioned_docs/version-3.19-1/operations/monitor/metrics/recommended-metrics.mdx
index 64a2713820..706a67b246 100644
--- a/calico-enterprise_versioned_docs/version-3.19-1/operations/monitor/metrics/recommended-metrics.mdx
+++ b/calico-enterprise_versioned_docs/version-3.19-1/operations/monitor/metrics/recommended-metrics.mdx
@@ -459,7 +459,7 @@ The following policy metrics are a separate endpoint exposed by Felix that are u
| Metric | felix_logs_dropped
|
| Example value | felix_logs_dropped\{endpoint="metrics-port", instance="10.0.1.20:9091", job="felix-metrics-svc", namespace="calico-system", pod="calico-node-qzpkt", service="felix-metrics-svc"\} 0
|
| Explanation | The number of logs Felix has dropped. Note that this metric does not count flow-logs; it counts logs to stdout. |
-| Threshold value recommendation | Occasional drops are normal. Investigate if frop counters rapidily rise. |
+| Threshold value recommendation | Occasional drops are normal. Investigate if drop counters rapidily rise. |
| Threshold breach symptoms | Felix will drop logs if it cannot keep up with writing them out. These are ordinary code logs, not flow logs. Calico-node may be under resource constraints. |
| Threshold breach recommendations | Check CPU usage on calico-nodes and Kubernetes nodes. Increase resources if needed, and rollout restart calico-node(s) if needed. |
| Priority level | Optional. |
From a99b27b2a5851911f3e371190de92b803dd49fef Mon Sep 17 00:00:00 2001
From: Josh Soref <2119212+jsoref@users.noreply.github.com>
Date: Wed, 15 Nov 2023 18:54:20 -0500
Subject: [PATCH 17/55] spelling: enterprise
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
---
.../FeatureTableComparison/index.tsx | 2 +-
.../data/featureTableComparisonInfo.ts | 92 +++++++++----------
2 files changed, 47 insertions(+), 47 deletions(-)
diff --git a/src/___new___/components/FeatureTableComparison/index.tsx b/src/___new___/components/FeatureTableComparison/index.tsx
index ecef5ab7a9..6bb515b08f 100644
--- a/src/___new___/components/FeatureTableComparison/index.tsx
+++ b/src/___new___/components/FeatureTableComparison/index.tsx
@@ -75,7 +75,7 @@ const ProductComparison: React.FCWebApplicationFirewall controls whether or not ModSecurity enforcement is enabled for the cluster. -When enabled, Services may opt-in to having ingress traffic examed by ModSecurity. +When enabled, Services may opt-in to having ingress traffic examined by ModSecurity.
@@ -4352,7 +4352,7 @@ WAFStatusTypeWebApplicationFirewall controls whether or not ModSecurity enforcement is enabled for the cluster. -When enabled, Services may opt-in to having ingress traffic examed by ModSecurity. +When enabled, Services may opt-in to having ingress traffic examined by ModSecurity.
diff --git a/calico-cloud_versioned_docs/version-19-1/reference/installation/_api.mdx b/calico-cloud_versioned_docs/version-19-1/reference/installation/_api.mdx index 845567a6ca..588b7b9267 100644 --- a/calico-cloud_versioned_docs/version-19-1/reference/installation/_api.mdx +++ b/calico-cloud_versioned_docs/version-19-1/reference/installation/_api.mdx @@ -488,7 +488,7 @@ WAFStatusTypeWebApplicationFirewall controls whether or not ModSecurity enforcement is enabled for the cluster. -When enabled, Services may opt-in to having ingress traffic examed by ModSecurity. +When enabled, Services may opt-in to having ingress traffic examined by ModSecurity.
@@ -4352,7 +4352,7 @@ WAFStatusTypeWebApplicationFirewall controls whether or not ModSecurity enforcement is enabled for the cluster. -When enabled, Services may opt-in to having ingress traffic examed by ModSecurity. +When enabled, Services may opt-in to having ingress traffic examined by ModSecurity.
diff --git a/calico-enterprise/reference/installation/_api.mdx b/calico-enterprise/reference/installation/_api.mdx index 845567a6ca..588b7b9267 100644 --- a/calico-enterprise/reference/installation/_api.mdx +++ b/calico-enterprise/reference/installation/_api.mdx @@ -488,7 +488,7 @@ WAFStatusTypeWebApplicationFirewall controls whether or not ModSecurity enforcement is enabled for the cluster. -When enabled, Services may opt-in to having ingress traffic examed by ModSecurity. +When enabled, Services may opt-in to having ingress traffic examined by ModSecurity.
@@ -4352,7 +4352,7 @@ WAFStatusTypeWebApplicationFirewall controls whether or not ModSecurity enforcement is enabled for the cluster. -When enabled, Services may opt-in to having ingress traffic examed by ModSecurity. +When enabled, Services may opt-in to having ingress traffic examined by ModSecurity.
diff --git a/calico-enterprise_versioned_docs/version-3.16/reference/installation/_api.mdx b/calico-enterprise_versioned_docs/version-3.16/reference/installation/_api.mdx index 823d0cbd24..f32caa2678 100644 --- a/calico-enterprise_versioned_docs/version-3.16/reference/installation/_api.mdx +++ b/calico-enterprise_versioned_docs/version-3.16/reference/installation/_api.mdx @@ -484,7 +484,7 @@ WAFStatusTypeWebApplicationFirewall controls whether or not ModSecurity enforcement is enabled for the cluster. -When enabled, Services may opt-in to having ingress traffic examed by ModSecurity. +When enabled, Services may opt-in to having ingress traffic examined by ModSecurity.
@@ -3944,7 +3944,7 @@ WAFStatusTypeWebApplicationFirewall controls whether or not ModSecurity enforcement is enabled for the cluster. -When enabled, Services may opt-in to having ingress traffic examed by ModSecurity. +When enabled, Services may opt-in to having ingress traffic examined by ModSecurity.
diff --git a/calico-enterprise_versioned_docs/version-3.17/reference/installation/_api.mdx b/calico-enterprise_versioned_docs/version-3.17/reference/installation/_api.mdx index a00dd18e8d..97a2c18168 100644 --- a/calico-enterprise_versioned_docs/version-3.17/reference/installation/_api.mdx +++ b/calico-enterprise_versioned_docs/version-3.17/reference/installation/_api.mdx @@ -486,7 +486,7 @@ WAFStatusTypeWebApplicationFirewall controls whether or not ModSecurity enforcement is enabled for the cluster. -When enabled, Services may opt-in to having ingress traffic examed by ModSecurity. +When enabled, Services may opt-in to having ingress traffic examined by ModSecurity.
@@ -4098,7 +4098,7 @@ WAFStatusTypeWebApplicationFirewall controls whether or not ModSecurity enforcement is enabled for the cluster. -When enabled, Services may opt-in to having ingress traffic examed by ModSecurity. +When enabled, Services may opt-in to having ingress traffic examined by ModSecurity.
diff --git a/calico-enterprise_versioned_docs/version-3.18-2/reference/installation/_api.mdx b/calico-enterprise_versioned_docs/version-3.18-2/reference/installation/_api.mdx index c8ded3a8e5..d40eec901d 100644 --- a/calico-enterprise_versioned_docs/version-3.18-2/reference/installation/_api.mdx +++ b/calico-enterprise_versioned_docs/version-3.18-2/reference/installation/_api.mdx @@ -488,7 +488,7 @@ WAFStatusTypeWebApplicationFirewall controls whether or not ModSecurity enforcement is enabled for the cluster. -When enabled, Services may opt-in to having ingress traffic examed by ModSecurity. +When enabled, Services may opt-in to having ingress traffic examined by ModSecurity.
@@ -4296,7 +4296,7 @@ WAFStatusTypeWebApplicationFirewall controls whether or not ModSecurity enforcement is enabled for the cluster. -When enabled, Services may opt-in to having ingress traffic examed by ModSecurity. +When enabled, Services may opt-in to having ingress traffic examined by ModSecurity.
diff --git a/calico-enterprise_versioned_docs/version-3.18/reference/installation/_api.mdx b/calico-enterprise_versioned_docs/version-3.18/reference/installation/_api.mdx index 859f292551..345efaca6e 100644 --- a/calico-enterprise_versioned_docs/version-3.18/reference/installation/_api.mdx +++ b/calico-enterprise_versioned_docs/version-3.18/reference/installation/_api.mdx @@ -486,7 +486,7 @@ WAFStatusTypeWebApplicationFirewall controls whether or not ModSecurity enforcement is enabled for the cluster. -When enabled, Services may opt-in to having ingress traffic examed by ModSecurity. +When enabled, Services may opt-in to having ingress traffic examined by ModSecurity.
@@ -4098,7 +4098,7 @@ WAFStatusTypeWebApplicationFirewall controls whether or not ModSecurity enforcement is enabled for the cluster. -When enabled, Services may opt-in to having ingress traffic examed by ModSecurity. +When enabled, Services may opt-in to having ingress traffic examined by ModSecurity.
diff --git a/calico-enterprise_versioned_docs/version-3.19-1/reference/installation/_api.mdx b/calico-enterprise_versioned_docs/version-3.19-1/reference/installation/_api.mdx index 5f9f766394..1eaf58a183 100644 --- a/calico-enterprise_versioned_docs/version-3.19-1/reference/installation/_api.mdx +++ b/calico-enterprise_versioned_docs/version-3.19-1/reference/installation/_api.mdx @@ -488,7 +488,7 @@ WAFStatusTypeWebApplicationFirewall controls whether or not ModSecurity enforcement is enabled for the cluster. -When enabled, Services may opt-in to having ingress traffic examed by ModSecurity. +When enabled, Services may opt-in to having ingress traffic examined by ModSecurity.
@@ -4371,7 +4371,7 @@ WAFStatusTypeWebApplicationFirewall controls whether or not ModSecurity enforcement is enabled for the cluster. -When enabled, Services may opt-in to having ingress traffic examed by ModSecurity. +When enabled, Services may opt-in to having ingress traffic examined by ModSecurity.
diff --git a/calico/reference/installation/_api.mdx b/calico/reference/installation/_api.mdx index b721f4f63c..ba97dbe44c 100644 --- a/calico/reference/installation/_api.mdx +++ b/calico/reference/installation/_api.mdx @@ -234,7 +234,7 @@ WAFStatusTypeWebApplicationFirewall controls whether or not ModSecurity enforcement is enabled for the cluster. -When enabled, Services may opt-in to having ingress traffic examed by ModSecurity. +When enabled, Services may opt-in to having ingress traffic examined by ModSecurity.
@@ -2485,7 +2485,7 @@ WAFStatusTypeWebApplicationFirewall controls whether or not ModSecurity enforcement is enabled for the cluster. -When enabled, Services may opt-in to having ingress traffic examed by ModSecurity. +When enabled, Services may opt-in to having ingress traffic examined by ModSecurity.
diff --git a/calico_versioned_docs/version-3.25/reference/installation/_api.mdx b/calico_versioned_docs/version-3.25/reference/installation/_api.mdx index 3608da4916..e4e01c1b6f 100644 --- a/calico_versioned_docs/version-3.25/reference/installation/_api.mdx +++ b/calico_versioned_docs/version-3.25/reference/installation/_api.mdx @@ -230,7 +230,7 @@ WAFStatusTypeWebApplicationFirewall controls whether or not ModSecurity enforcement is enabled for the cluster. -When enabled, Services may opt-in to having ingress traffic examed by ModSecurity. +When enabled, Services may opt-in to having ingress traffic examined by ModSecurity.
@@ -2150,7 +2150,7 @@ WAFStatusTypeWebApplicationFirewall controls whether or not ModSecurity enforcement is enabled for the cluster. -When enabled, Services may opt-in to having ingress traffic examed by ModSecurity. +When enabled, Services may opt-in to having ingress traffic examined by ModSecurity.
diff --git a/calico_versioned_docs/version-3.26/reference/installation/_api.mdx b/calico_versioned_docs/version-3.26/reference/installation/_api.mdx index dbc92e0066..166f647706 100644 --- a/calico_versioned_docs/version-3.26/reference/installation/_api.mdx +++ b/calico_versioned_docs/version-3.26/reference/installation/_api.mdx @@ -232,7 +232,7 @@ WAFStatusTypeWebApplicationFirewall controls whether or not ModSecurity enforcement is enabled for the cluster. -When enabled, Services may opt-in to having ingress traffic examed by ModSecurity. +When enabled, Services may opt-in to having ingress traffic examined by ModSecurity.
@@ -2304,7 +2304,7 @@ WAFStatusTypeWebApplicationFirewall controls whether or not ModSecurity enforcement is enabled for the cluster. -When enabled, Services may opt-in to having ingress traffic examed by ModSecurity. +When enabled, Services may opt-in to having ingress traffic examined by ModSecurity.
diff --git a/calico_versioned_docs/version-3.27/reference/installation/_api.mdx b/calico_versioned_docs/version-3.27/reference/installation/_api.mdx index b721f4f63c..ba97dbe44c 100644 --- a/calico_versioned_docs/version-3.27/reference/installation/_api.mdx +++ b/calico_versioned_docs/version-3.27/reference/installation/_api.mdx @@ -234,7 +234,7 @@ WAFStatusTypeWebApplicationFirewall controls whether or not ModSecurity enforcement is enabled for the cluster. -When enabled, Services may opt-in to having ingress traffic examed by ModSecurity. +When enabled, Services may opt-in to having ingress traffic examined by ModSecurity.
@@ -2485,7 +2485,7 @@ WAFStatusTypeWebApplicationFirewall controls whether or not ModSecurity enforcement is enabled for the cluster. -When enabled, Services may opt-in to having ingress traffic examed by ModSecurity. +When enabled, Services may opt-in to having ingress traffic examined by ModSecurity.
From 1112e96ae941e18324c92ffc4a4f160c2b855bb2 Mon Sep 17 00:00:00 2001 From: Josh Soref <2119212+jsoref@users.noreply.github.com> Date: Wed, 15 Nov 2023 18:55:41 -0500 Subject: [PATCH 20/55] spelling: explicitly Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> --- src/forks/image-size/dist/types.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/forks/image-size/dist/types.js b/src/forks/image-size/dist/types.js index f7cac0492c..3adafac009 100644 --- a/src/forks/image-size/dist/types.js +++ b/src/forks/image-size/dist/types.js @@ -1,7 +1,7 @@ "use strict"; Object.defineProperty(exports, "__esModule", { value: true }); exports.typeHandlers = void 0; -// load all available handlers explicitely for browserify support +// load all available handlers explicitly for browserify support const bmp_1 = require("./types/bmp"); const cur_1 = require("./types/cur"); const dds_1 = require("./types/dds"); From 8c7d2e9cc295be56e31bc3d0c5280ba079795b5b Mon Sep 17 00:00:00 2001 From: Josh Soref <2119212+jsoref@users.noreply.github.com> Date: Wed, 15 Nov 2023 18:35:10 -0500 Subject: [PATCH 21/55] spelling: github Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> --- calico-cloud/image-assurance/scanners/pipeline-scanner.mdx | 2 +- .../image-assurance/scanners/pipeline-scanner.mdx | 2 +- calico/about/training-resources.mdx | 4 ++-- calico/getting-started/kubernetes/vpp/getting-started.mdx | 2 +- calico/operations/troubleshoot/vpp.mdx | 2 +- calico/training/index.mdx | 2 +- .../getting-started/kubernetes/vpp/getting-started.mdx | 2 +- .../version-3.25/operations/troubleshoot/vpp.mdx | 2 +- calico_versioned_docs/version-3.25/training/index.mdx | 2 +- .../version-3.26/about/training-resources.mdx | 4 ++-- .../getting-started/kubernetes/vpp/getting-started.mdx | 2 +- .../version-3.26/operations/troubleshoot/vpp.mdx | 2 +- calico_versioned_docs/version-3.26/training/index.mdx | 2 +- .../version-3.27/about/training-resources.mdx | 2 +- .../getting-started/kubernetes/vpp/getting-started.mdx | 2 +- .../version-3.27/operations/troubleshoot/vpp.mdx | 2 +- calico_versioned_docs/version-3.27/training/index.mdx | 2 +- 17 files changed, 19 insertions(+), 19 deletions(-) diff --git a/calico-cloud/image-assurance/scanners/pipeline-scanner.mdx b/calico-cloud/image-assurance/scanners/pipeline-scanner.mdx index b2e86433df..2ca5d47cb2 100644 --- a/calico-cloud/image-assurance/scanners/pipeline-scanner.mdx +++ b/calico-cloud/image-assurance/scanners/pipeline-scanner.mdx @@ -77,7 +77,7 @@ You must download and set the executable flag each time you get a new version of ``` ### Integrate the scanner into your build pipeline -You can include the CLI scanner in your CI/CD pipelines (for example, Jenkins, Github actions). Ensure the following: +You can include the CLI scanner in your CI/CD pipelines (for example, Jenkins, GitHub actions). Ensure the following: - Download the CLI scanner binary onto your CI runner - If you are running an ephemeral environment in the pipeline, include the download, and update the executable steps in your pipeline to download the scanner on every execution diff --git a/calico-cloud_versioned_docs/version-19-1/image-assurance/scanners/pipeline-scanner.mdx b/calico-cloud_versioned_docs/version-19-1/image-assurance/scanners/pipeline-scanner.mdx index b2e86433df..2ca5d47cb2 100644 --- a/calico-cloud_versioned_docs/version-19-1/image-assurance/scanners/pipeline-scanner.mdx +++ b/calico-cloud_versioned_docs/version-19-1/image-assurance/scanners/pipeline-scanner.mdx @@ -77,7 +77,7 @@ You must download and set the executable flag each time you get a new version of ``` ### Integrate the scanner into your build pipeline -You can include the CLI scanner in your CI/CD pipelines (for example, Jenkins, Github actions). Ensure the following: +You can include the CLI scanner in your CI/CD pipelines (for example, Jenkins, GitHub actions). Ensure the following: - Download the CLI scanner binary onto your CI runner - If you are running an ephemeral environment in the pipeline, include the download, and update the executable steps in your pipeline to download the scanner on every execution diff --git a/calico/about/training-resources.mdx b/calico/about/training-resources.mdx index 031eddfe53..8b5e3c11e9 100644 --- a/calico/about/training-resources.mdx +++ b/calico/about/training-resources.mdx @@ -12,5 +12,5 @@ description: Links to Calico resources for onboarding and training. | Workshops | [Workshops and events](https://www.tigera.io/events/) | | Videos, datasheets | [Videos, case studies, datasheets, etc.](https://www.tigera.io/resources/) | | Blog | [Technical blog](https://www.tigera.io/blog/?_sft_post_tag=project-calico) | -| Stay connected | • [Github](https://github.com/projectcalico/calico)rate(process_cpu_seconds_total\{30s\}) \* 100
|
| Example value | \{endpoint="metrics-port", instance="10.0.1.20:9091", job="felix-metrics-svc", namespace="calico-system", pod="calico-node-qzpkt", service="felix-metrics-svc"\}3.1197504199664072
|
| Explanation | CPU in use by calico-node represented as a percentage of a core. |
-| Threshold value recommendation | A spike at startup is normal. It is recommended to first achieve a baseline and then monitor for any unexpected increases from this baseline. Investigage if maintained CPU usage goes above 90%. |
+| Threshold value recommendation | A spike at startup is normal. It is recommended to first achieve a baseline and then monitor for any unexpected increases from this baseline. Investigate if maintained CPU usage goes above 90%. |
| Threshold breach symptoms | Unexpected maintained CPU usage could cause Felix to fall behind and could cause delays to policy updates. |
| Threshold breach recommendations | Check CPU usage on Kubernetes nodes. Increase resources if needed, rollout restart calico-node(s) if needed. |
| Priority level | Recommended. |
diff --git a/calico-cloud_versioned_docs/version-19-1/operations/monitor/metrics/recommended-metrics.mdx b/calico-cloud_versioned_docs/version-19-1/operations/monitor/metrics/recommended-metrics.mdx
index 2c2cd169cb..df9937efcc 100644
--- a/calico-cloud_versioned_docs/version-19-1/operations/monitor/metrics/recommended-metrics.mdx
+++ b/calico-cloud_versioned_docs/version-19-1/operations/monitor/metrics/recommended-metrics.mdx
@@ -352,7 +352,7 @@ The following policy metrics are a separate endpoint exposed by Felix that are u
| Metric | rate(process_cpu_seconds_total\{30s\}) \* 100
|
| Example value | \{endpoint="metrics-port", instance="10.0.1.20:9091", job="felix-metrics-svc", namespace="calico-system", pod="calico-node-qzpkt", service="felix-metrics-svc"\}3.1197504199664072
|
| Explanation | CPU in use by calico-node represented as a percentage of a core. |
-| Threshold value recommendation | A spike at startup is normal. It is recommended to first achieve a baseline and then monitor for any unexpected increases from this baseline. Investigage if maintained CPU usage goes above 90%. |
+| Threshold value recommendation | A spike at startup is normal. It is recommended to first achieve a baseline and then monitor for any unexpected increases from this baseline. Investigate if maintained CPU usage goes above 90%. |
| Threshold breach symptoms | Unexpected maintained CPU usage could cause Felix to fall behind and could cause delays to policy updates. |
| Threshold breach recommendations | Check CPU usage on Kubernetes nodes. Increase resources if needed, rollout restart calico-node(s) if needed. |
| Priority level | Recommended. |
diff --git a/calico-enterprise/operations/monitor/metrics/recommended-metrics.mdx b/calico-enterprise/operations/monitor/metrics/recommended-metrics.mdx
index 706a67b246..2a93f36cbc 100644
--- a/calico-enterprise/operations/monitor/metrics/recommended-metrics.mdx
+++ b/calico-enterprise/operations/monitor/metrics/recommended-metrics.mdx
@@ -352,7 +352,7 @@ The following policy metrics are a separate endpoint exposed by Felix that are u
| Metric | rate(process_cpu_seconds_total\{30s\}) \* 100
|
| Example value | \{endpoint="metrics-port", instance="10.0.1.20:9091", job="felix-metrics-svc", namespace="calico-system", pod="calico-node-qzpkt", service="felix-metrics-svc"\}3.1197504199664072
|
| Explanation | CPU in use by calico-node represented as a percentage of a core. |
-| Threshold value recommendation | A spike at startup is normal. It is recommended to first achieve a baseline and then monitor for any unexpected increases from this baseline. Investigage if maintained CPU usage goes above 90%. |
+| Threshold value recommendation | A spike at startup is normal. It is recommended to first achieve a baseline and then monitor for any unexpected increases from this baseline. Investigate if maintained CPU usage goes above 90%. |
| Threshold breach symptoms | Unexpected maintained CPU usage could cause Felix to fall behind and could cause delays to policy updates. |
| Threshold breach recommendations | Check CPU usage on Kubernetes nodes. Increase resources if needed, rollout restart calico-node(s) if needed. |
| Priority level | Recommended. |
diff --git a/calico-enterprise_versioned_docs/version-3.18-2/operations/monitor/metrics/recommended-metrics.mdx b/calico-enterprise_versioned_docs/version-3.18-2/operations/monitor/metrics/recommended-metrics.mdx
index 706a67b246..2a93f36cbc 100644
--- a/calico-enterprise_versioned_docs/version-3.18-2/operations/monitor/metrics/recommended-metrics.mdx
+++ b/calico-enterprise_versioned_docs/version-3.18-2/operations/monitor/metrics/recommended-metrics.mdx
@@ -352,7 +352,7 @@ The following policy metrics are a separate endpoint exposed by Felix that are u
| Metric | rate(process_cpu_seconds_total\{30s\}) \* 100
|
| Example value | \{endpoint="metrics-port", instance="10.0.1.20:9091", job="felix-metrics-svc", namespace="calico-system", pod="calico-node-qzpkt", service="felix-metrics-svc"\}3.1197504199664072
|
| Explanation | CPU in use by calico-node represented as a percentage of a core. |
-| Threshold value recommendation | A spike at startup is normal. It is recommended to first achieve a baseline and then monitor for any unexpected increases from this baseline. Investigage if maintained CPU usage goes above 90%. |
+| Threshold value recommendation | A spike at startup is normal. It is recommended to first achieve a baseline and then monitor for any unexpected increases from this baseline. Investigate if maintained CPU usage goes above 90%. |
| Threshold breach symptoms | Unexpected maintained CPU usage could cause Felix to fall behind and could cause delays to policy updates. |
| Threshold breach recommendations | Check CPU usage on Kubernetes nodes. Increase resources if needed, rollout restart calico-node(s) if needed. |
| Priority level | Recommended. |
diff --git a/calico-enterprise_versioned_docs/version-3.19-1/operations/monitor/metrics/recommended-metrics.mdx b/calico-enterprise_versioned_docs/version-3.19-1/operations/monitor/metrics/recommended-metrics.mdx
index 706a67b246..2a93f36cbc 100644
--- a/calico-enterprise_versioned_docs/version-3.19-1/operations/monitor/metrics/recommended-metrics.mdx
+++ b/calico-enterprise_versioned_docs/version-3.19-1/operations/monitor/metrics/recommended-metrics.mdx
@@ -352,7 +352,7 @@ The following policy metrics are a separate endpoint exposed by Felix that are u
| Metric | rate(process_cpu_seconds_total\{30s\}) \* 100
|
| Example value | \{endpoint="metrics-port", instance="10.0.1.20:9091", job="felix-metrics-svc", namespace="calico-system", pod="calico-node-qzpkt", service="felix-metrics-svc"\}3.1197504199664072
|
| Explanation | CPU in use by calico-node represented as a percentage of a core. |
-| Threshold value recommendation | A spike at startup is normal. It is recommended to first achieve a baseline and then monitor for any unexpected increases from this baseline. Investigage if maintained CPU usage goes above 90%. |
+| Threshold value recommendation | A spike at startup is normal. It is recommended to first achieve a baseline and then monitor for any unexpected increases from this baseline. Investigate if maintained CPU usage goes above 90%. |
| Threshold breach symptoms | Unexpected maintained CPU usage could cause Felix to fall behind and could cause delays to policy updates. |
| Threshold breach recommendations | Check CPU usage on Kubernetes nodes. Increase resources if needed, rollout restart calico-node(s) if needed. |
| Priority level | Recommended. |
From 4530d2133d0b66cf7e92019331b8d4ebafad1ab5 Mon Sep 17 00:00:00 2001
From: Josh Soref <2119212+jsoref@users.noreply.github.com>
Date: Thu, 21 Mar 2024 00:19:26 -0400
Subject: [PATCH 28/55] spelling: is disconnected
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
---
calico-cloud/operations/monitor/metrics/recommended-metrics.mdx | 2 +-
.../operations/monitor/metrics/recommended-metrics.mdx | 2 +-
.../operations/monitor/metrics/recommended-metrics.mdx | 2 +-
.../operations/monitor/metrics/recommended-metrics.mdx | 2 +-
.../operations/monitor/metrics/recommended-metrics.mdx | 2 +-
5 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/calico-cloud/operations/monitor/metrics/recommended-metrics.mdx b/calico-cloud/operations/monitor/metrics/recommended-metrics.mdx
index df9937efcc..2387a1b2e4 100644
--- a/calico-cloud/operations/monitor/metrics/recommended-metrics.mdx
+++ b/calico-cloud/operations/monitor/metrics/recommended-metrics.mdx
@@ -261,7 +261,7 @@ The following metrics are applicable only if you have implemented [Cluster mesh]
| Example value | \{instance="10.0.1.20:9093"\} NaN
|
| Explanation | The median time to stream the initial datastore snapshot to each client. It is useful to know the time it takes for a client to receive the data when it connects; it does not include time to process the data. |
| Threshold value recommendation | Investigate if this value is moving towards 10s of seconds. |
-| Threshold breach symptoms | High values of this metric could indicate that newly-started clients are taking a long time to get the latest snapshot of the datastore, increasing the window of time where networking/policy updates are not being applied to the dataplane during a restart/upgrade. Typha has a write timeout for writing the snapshot; if a client cannot receive the snapshot within that timeout, it isdisconnected. Clients falling behind on information and updates contained in the datastore (for example, {{prodname}} network policy object may not be current). |
+| Threshold breach symptoms | High values of this metric could indicate that newly-started clients are taking a long time to get the latest snapshot of the datastore, increasing the window of time where networking/policy updates are not being applied to the dataplane during a restart/upgrade. Typha has a write timeout for writing the snapshot; if a client cannot receive the snapshot within that timeout, it is disconnected. Clients falling behind on information and updates contained in the datastore (for example, {{prodname}} network policy object may not be current). |
| Threshold breach recommendations | Check Typha and calico-node logs and resource usage. Check for network congestion. Investigate why a particular calico-node is slow; it is likely on an overloaded node with insufficient CPU). |
| Priority level | Optional. |
diff --git a/calico-cloud_versioned_docs/version-19-1/operations/monitor/metrics/recommended-metrics.mdx b/calico-cloud_versioned_docs/version-19-1/operations/monitor/metrics/recommended-metrics.mdx
index df9937efcc..2387a1b2e4 100644
--- a/calico-cloud_versioned_docs/version-19-1/operations/monitor/metrics/recommended-metrics.mdx
+++ b/calico-cloud_versioned_docs/version-19-1/operations/monitor/metrics/recommended-metrics.mdx
@@ -261,7 +261,7 @@ The following metrics are applicable only if you have implemented [Cluster mesh]
| Example value | \{instance="10.0.1.20:9093"\} NaN
|
| Explanation | The median time to stream the initial datastore snapshot to each client. It is useful to know the time it takes for a client to receive the data when it connects; it does not include time to process the data. |
| Threshold value recommendation | Investigate if this value is moving towards 10s of seconds. |
-| Threshold breach symptoms | High values of this metric could indicate that newly-started clients are taking a long time to get the latest snapshot of the datastore, increasing the window of time where networking/policy updates are not being applied to the dataplane during a restart/upgrade. Typha has a write timeout for writing the snapshot; if a client cannot receive the snapshot within that timeout, it isdisconnected. Clients falling behind on information and updates contained in the datastore (for example, {{prodname}} network policy object may not be current). |
+| Threshold breach symptoms | High values of this metric could indicate that newly-started clients are taking a long time to get the latest snapshot of the datastore, increasing the window of time where networking/policy updates are not being applied to the dataplane during a restart/upgrade. Typha has a write timeout for writing the snapshot; if a client cannot receive the snapshot within that timeout, it is disconnected. Clients falling behind on information and updates contained in the datastore (for example, {{prodname}} network policy object may not be current). |
| Threshold breach recommendations | Check Typha and calico-node logs and resource usage. Check for network congestion. Investigate why a particular calico-node is slow; it is likely on an overloaded node with insufficient CPU). |
| Priority level | Optional. |
diff --git a/calico-enterprise/operations/monitor/metrics/recommended-metrics.mdx b/calico-enterprise/operations/monitor/metrics/recommended-metrics.mdx
index 2a93f36cbc..3d6686721d 100644
--- a/calico-enterprise/operations/monitor/metrics/recommended-metrics.mdx
+++ b/calico-enterprise/operations/monitor/metrics/recommended-metrics.mdx
@@ -261,7 +261,7 @@ The following metrics are applicable only if you have implemented [Cluster mesh]
| Example value | \{instance="10.0.1.20:9093"\} NaN
|
| Explanation | The median time to stream the initial datastore snapshot to each client. It is useful to know the time it takes for a client to receive the data when it connects; it does not include time to process the data. |
| Threshold value recommendation | Investigate if this value is moving towards 10s of seconds. |
-| Threshold breach symptoms | High values of this metric could indicate that newly-started clients are taking a long time to get the latest snapshot of the datastore, increasing the window of time where networking/policy updates are not being applied to the dataplane during a restart/upgrade. Typha has a write timeout for writing the snapshot; if a client cannot receive the snapshot within that timeout, it isdisconnected. Clients falling behind on information and updates contained in the datastore (for example, {{prodname}} network policy object may not be current). |
+| Threshold breach symptoms | High values of this metric could indicate that newly-started clients are taking a long time to get the latest snapshot of the datastore, increasing the window of time where networking/policy updates are not being applied to the dataplane during a restart/upgrade. Typha has a write timeout for writing the snapshot; if a client cannot receive the snapshot within that timeout, it is disconnected. Clients falling behind on information and updates contained in the datastore (for example, {{prodname}} network policy object may not be current). |
| Threshold breach recommendations | Check Typha and calico-node logs and resource usage. Check for network congestion. Investigate why a particular calico-node is slow; it is likely on an overloaded node with insufficient CPU). |
| Priority level | Optional. |
diff --git a/calico-enterprise_versioned_docs/version-3.18-2/operations/monitor/metrics/recommended-metrics.mdx b/calico-enterprise_versioned_docs/version-3.18-2/operations/monitor/metrics/recommended-metrics.mdx
index 2a93f36cbc..3d6686721d 100644
--- a/calico-enterprise_versioned_docs/version-3.18-2/operations/monitor/metrics/recommended-metrics.mdx
+++ b/calico-enterprise_versioned_docs/version-3.18-2/operations/monitor/metrics/recommended-metrics.mdx
@@ -261,7 +261,7 @@ The following metrics are applicable only if you have implemented [Cluster mesh]
| Example value | \{instance="10.0.1.20:9093"\} NaN
|
| Explanation | The median time to stream the initial datastore snapshot to each client. It is useful to know the time it takes for a client to receive the data when it connects; it does not include time to process the data. |
| Threshold value recommendation | Investigate if this value is moving towards 10s of seconds. |
-| Threshold breach symptoms | High values of this metric could indicate that newly-started clients are taking a long time to get the latest snapshot of the datastore, increasing the window of time where networking/policy updates are not being applied to the dataplane during a restart/upgrade. Typha has a write timeout for writing the snapshot; if a client cannot receive the snapshot within that timeout, it isdisconnected. Clients falling behind on information and updates contained in the datastore (for example, {{prodname}} network policy object may not be current). |
+| Threshold breach symptoms | High values of this metric could indicate that newly-started clients are taking a long time to get the latest snapshot of the datastore, increasing the window of time where networking/policy updates are not being applied to the dataplane during a restart/upgrade. Typha has a write timeout for writing the snapshot; if a client cannot receive the snapshot within that timeout, it is disconnected. Clients falling behind on information and updates contained in the datastore (for example, {{prodname}} network policy object may not be current). |
| Threshold breach recommendations | Check Typha and calico-node logs and resource usage. Check for network congestion. Investigate why a particular calico-node is slow; it is likely on an overloaded node with insufficient CPU). |
| Priority level | Optional. |
diff --git a/calico-enterprise_versioned_docs/version-3.19-1/operations/monitor/metrics/recommended-metrics.mdx b/calico-enterprise_versioned_docs/version-3.19-1/operations/monitor/metrics/recommended-metrics.mdx
index 2a93f36cbc..3d6686721d 100644
--- a/calico-enterprise_versioned_docs/version-3.19-1/operations/monitor/metrics/recommended-metrics.mdx
+++ b/calico-enterprise_versioned_docs/version-3.19-1/operations/monitor/metrics/recommended-metrics.mdx
@@ -261,7 +261,7 @@ The following metrics are applicable only if you have implemented [Cluster mesh]
| Example value | \{instance="10.0.1.20:9093"\} NaN
|
| Explanation | The median time to stream the initial datastore snapshot to each client. It is useful to know the time it takes for a client to receive the data when it connects; it does not include time to process the data. |
| Threshold value recommendation | Investigate if this value is moving towards 10s of seconds. |
-| Threshold breach symptoms | High values of this metric could indicate that newly-started clients are taking a long time to get the latest snapshot of the datastore, increasing the window of time where networking/policy updates are not being applied to the dataplane during a restart/upgrade. Typha has a write timeout for writing the snapshot; if a client cannot receive the snapshot within that timeout, it isdisconnected. Clients falling behind on information and updates contained in the datastore (for example, {{prodname}} network policy object may not be current). |
+| Threshold breach symptoms | High values of this metric could indicate that newly-started clients are taking a long time to get the latest snapshot of the datastore, increasing the window of time where networking/policy updates are not being applied to the dataplane during a restart/upgrade. Typha has a write timeout for writing the snapshot; if a client cannot receive the snapshot within that timeout, it is disconnected. Clients falling behind on information and updates contained in the datastore (for example, {{prodname}} network policy object may not be current). |
| Threshold breach recommendations | Check Typha and calico-node logs and resource usage. Check for network congestion. Investigate why a particular calico-node is slow; it is likely on an overloaded node with insufficient CPU). |
| Priority level | Optional. |
From f563bb72ede5119658d8e4dc1135252352b06f5a Mon Sep 17 00:00:00 2001
From: Josh Soref <2119212+jsoref@users.noreply.github.com>
Date: Wed, 20 Mar 2024 23:59:17 -0400
Subject: [PATCH 29/55] spelling: its
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
---
.../reference/architecture/design/l2-interconnect-fabric.mdx | 2 +-
.../reference/architecture/design/l2-interconnect-fabric.mdx | 2 +-
calico-enterprise/getting-started/install-on-clusters/aws.mdx | 2 +-
.../reference/architecture/design/l2-interconnect-fabric.mdx | 2 +-
.../version-3.16/getting-started/install-on-clusters/aws.mdx | 2 +-
.../reference/architecture/design/l2-interconnect-fabric.mdx | 2 +-
.../version-3.17/getting-started/install-on-clusters/aws.mdx | 2 +-
.../reference/architecture/design/l2-interconnect-fabric.mdx | 2 +-
.../version-3.18-2/getting-started/install-on-clusters/aws.mdx | 2 +-
.../reference/architecture/design/l2-interconnect-fabric.mdx | 2 +-
.../version-3.18/getting-started/install-on-clusters/aws.mdx | 2 +-
.../reference/architecture/design/l2-interconnect-fabric.mdx | 2 +-
.../version-3.19-1/getting-started/install-on-clusters/aws.mdx | 2 +-
.../reference/architecture/design/l2-interconnect-fabric.mdx | 2 +-
calico/reference/architecture/design/l2-interconnect-fabric.mdx | 2 +-
.../reference/architecture/design/l2-interconnect-fabric.mdx | 2 +-
.../reference/architecture/design/l2-interconnect-fabric.mdx | 2 +-
.../reference/architecture/design/l2-interconnect-fabric.mdx | 2 +-
18 files changed, 18 insertions(+), 18 deletions(-)
diff --git a/calico-cloud/reference/architecture/design/l2-interconnect-fabric.mdx b/calico-cloud/reference/architecture/design/l2-interconnect-fabric.mdx
index 259f1f7038..76199c2efa 100644
--- a/calico-cloud/reference/architecture/design/l2-interconnect-fabric.mdx
+++ b/calico-cloud/reference/architecture/design/l2-interconnect-fabric.mdx
@@ -186,7 +186,7 @@ Each plane would constitute an IP network, so the blue plane would be
orange and red planes would be 2001:db8:3000::/36 and 2001:db8:4000::/36
respectively. [^3]
-Each IP network (plane) requires it's own BGP route reflectors. Those
+Each IP network (plane) requires its own BGP route reflectors. Those
route reflectors need to be peered with each other within the plane, but
the route reflectors in each plane do not need to be peered with one
another. Therefore, a fabric of four planes would have four route
diff --git a/calico-cloud_versioned_docs/version-19-1/reference/architecture/design/l2-interconnect-fabric.mdx b/calico-cloud_versioned_docs/version-19-1/reference/architecture/design/l2-interconnect-fabric.mdx
index 259f1f7038..76199c2efa 100644
--- a/calico-cloud_versioned_docs/version-19-1/reference/architecture/design/l2-interconnect-fabric.mdx
+++ b/calico-cloud_versioned_docs/version-19-1/reference/architecture/design/l2-interconnect-fabric.mdx
@@ -186,7 +186,7 @@ Each plane would constitute an IP network, so the blue plane would be
orange and red planes would be 2001:db8:3000::/36 and 2001:db8:4000::/36
respectively. [^3]
-Each IP network (plane) requires it's own BGP route reflectors. Those
+Each IP network (plane) requires its own BGP route reflectors. Those
route reflectors need to be peered with each other within the plane, but
the route reflectors in each plane do not need to be peered with one
another. Therefore, a fabric of four planes would have four route
diff --git a/calico-enterprise/getting-started/install-on-clusters/aws.mdx b/calico-enterprise/getting-started/install-on-clusters/aws.mdx
index 15d5633700..09f4d051ac 100644
--- a/calico-enterprise/getting-started/install-on-clusters/aws.mdx
+++ b/calico-enterprise/getting-started/install-on-clusters/aws.mdx
@@ -86,7 +86,7 @@ To use kOps to create a cluster with {{prodname}} networking and network policy:
:::
-1. The provisioned kOps cluster will assign it's own set of pod network CIDR in the kube-proxy instance different than the one {{prodname}} expects. To set the cluster cidr for the kube-proxy to match the one expected by {{prodname}} edit the cluster config `kops edit cluster hostNetwork:true
in their pod spec. See the Kuberentes API{' '}
+ hostNetwork:true
in their pod spec. See the Kubernetes API{' '}
pod spec
{' '}
diff --git a/calico-enterprise/reference/resources/securityeventwebhook.mdx b/calico-enterprise/reference/resources/securityeventwebhook.mdx
index bd28ce1d9f..0b4f928f60 100644
--- a/calico-enterprise/reference/resources/securityeventwebhook.mdx
+++ b/calico-enterprise/reference/resources/securityeventwebhook.mdx
@@ -76,7 +76,7 @@ The value must conform to the following rules:
| ------------ | -------------------------------------------------------------------------- | --------------------------------------------------------------------------- | ----------------------------------- |
| name | Configuration variable name. | string | yes |
| value | Direct value for the variable. | string | yes if `valueFrom` is not specifed |
-| valueFrom | Value defined either in a Kubernetes ConfigMap or in a Kubernetesa Secret. | [SecurityEventWebhookConfigVarSource](#securityeventwebhookconfigvarsource) | yes if `value` is not specified |
+| valueFrom | Value defined either in a Kubernetes ConfigMap or in a Kubernetes Secret. | [SecurityEventWebhookConfigVarSource](#securityeventwebhookconfigvarsource) | yes if `value` is not specified |
### SecurityEventWebhookConfigVarSource
diff --git a/calico-enterprise_versioned_docs/version-3.16/_includes/components/InstallEKS.js b/calico-enterprise_versioned_docs/version-3.16/_includes/components/InstallEKS.js
index d11476cd30..9316d91501 100644
--- a/calico-enterprise_versioned_docs/version-3.16/_includes/components/InstallEKS.js
+++ b/calico-enterprise_versioned_docs/version-3.16/_includes/components/InstallEKS.js
@@ -143,7 +143,7 @@ spec:
plane nodes will not be able to initiate network connections to {prodname} pods. (This is a general limitation
of EKS's custom networking support, not specific to {prodname}.) As a workaround, trusted pods that require
control plane nodes to connect to them, such as those implementing admission controller webhooks, can include{' '}
- hostNetwork:true
in their pod spec. See the Kuberentes API{' '}
+ hostNetwork:true
in their pod spec. See the Kubernetes API{' '}
pod spec
{' '}
diff --git a/calico-enterprise_versioned_docs/version-3.17/_includes/components/InstallEKS.js b/calico-enterprise_versioned_docs/version-3.17/_includes/components/InstallEKS.js
index 6f7ec74e0a..fd7ba4ecb6 100644
--- a/calico-enterprise_versioned_docs/version-3.17/_includes/components/InstallEKS.js
+++ b/calico-enterprise_versioned_docs/version-3.17/_includes/components/InstallEKS.js
@@ -138,7 +138,7 @@ spec:
plane nodes will not be able to initiate network connections to {prodname} pods. (This is a general limitation
of EKS's custom networking support, not specific to {prodname}.) As a workaround, trusted pods that require
control plane nodes to connect to them, such as those implementing admission controller webhooks, can include{' '}
- hostNetwork:true
in their pod spec. See the Kuberentes API{' '}
+ hostNetwork:true
in their pod spec. See the Kubernetes API{' '}
pod spec
{' '}
diff --git a/calico-enterprise_versioned_docs/version-3.18-2/_includes/components-temp/InstallEKS-temp.js b/calico-enterprise_versioned_docs/version-3.18-2/_includes/components-temp/InstallEKS-temp.js
index c0dd9ab9d4..06e7b8e470 100644
--- a/calico-enterprise_versioned_docs/version-3.18-2/_includes/components-temp/InstallEKS-temp.js
+++ b/calico-enterprise_versioned_docs/version-3.18-2/_includes/components-temp/InstallEKS-temp.js
@@ -138,7 +138,7 @@ spec:
plane nodes will not be able to initiate network connections to {prodname} pods. (This is a general limitation
of EKS's custom networking support, not specific to {prodname}.) As a workaround, trusted pods that require
control plane nodes to connect to them, such as those implementing admission controller webhooks, can include{' '}
- hostNetwork:true
in their pod spec. See the Kuberentes API{' '}
+ hostNetwork:true
in their pod spec. See the Kubernetes API{' '}
pod spec
{' '}
diff --git a/calico-enterprise_versioned_docs/version-3.18-2/_includes/components/InstallEKS.js b/calico-enterprise_versioned_docs/version-3.18-2/_includes/components/InstallEKS.js
index 6f7ec74e0a..fd7ba4ecb6 100644
--- a/calico-enterprise_versioned_docs/version-3.18-2/_includes/components/InstallEKS.js
+++ b/calico-enterprise_versioned_docs/version-3.18-2/_includes/components/InstallEKS.js
@@ -138,7 +138,7 @@ spec:
plane nodes will not be able to initiate network connections to {prodname} pods. (This is a general limitation
of EKS's custom networking support, not specific to {prodname}.) As a workaround, trusted pods that require
control plane nodes to connect to them, such as those implementing admission controller webhooks, can include{' '}
- hostNetwork:true
in their pod spec. See the Kuberentes API{' '}
+ hostNetwork:true
in their pod spec. See the Kubernetes API{' '}
pod spec
{' '}
diff --git a/calico-enterprise_versioned_docs/version-3.18/_includes/components/InstallEKS.js b/calico-enterprise_versioned_docs/version-3.18/_includes/components/InstallEKS.js
index 6f7ec74e0a..fd7ba4ecb6 100644
--- a/calico-enterprise_versioned_docs/version-3.18/_includes/components/InstallEKS.js
+++ b/calico-enterprise_versioned_docs/version-3.18/_includes/components/InstallEKS.js
@@ -138,7 +138,7 @@ spec:
plane nodes will not be able to initiate network connections to {prodname} pods. (This is a general limitation
of EKS's custom networking support, not specific to {prodname}.) As a workaround, trusted pods that require
control plane nodes to connect to them, such as those implementing admission controller webhooks, can include{' '}
- hostNetwork:true
in their pod spec. See the Kuberentes API{' '}
+ hostNetwork:true
in their pod spec. See the Kubernetes API{' '}
pod spec
{' '}
diff --git a/calico-enterprise_versioned_docs/version-3.19-1/_includes/components-temp/InstallEKS-temp.js b/calico-enterprise_versioned_docs/version-3.19-1/_includes/components-temp/InstallEKS-temp.js
index c0dd9ab9d4..06e7b8e470 100644
--- a/calico-enterprise_versioned_docs/version-3.19-1/_includes/components-temp/InstallEKS-temp.js
+++ b/calico-enterprise_versioned_docs/version-3.19-1/_includes/components-temp/InstallEKS-temp.js
@@ -138,7 +138,7 @@ spec:
plane nodes will not be able to initiate network connections to {prodname} pods. (This is a general limitation
of EKS's custom networking support, not specific to {prodname}.) As a workaround, trusted pods that require
control plane nodes to connect to them, such as those implementing admission controller webhooks, can include{' '}
- hostNetwork:true
in their pod spec. See the Kuberentes API{' '}
+ hostNetwork:true
in their pod spec. See the Kubernetes API{' '}
pod spec
{' '}
diff --git a/calico-enterprise_versioned_docs/version-3.19-1/_includes/components/InstallEKS.js b/calico-enterprise_versioned_docs/version-3.19-1/_includes/components/InstallEKS.js
index 6f7ec74e0a..fd7ba4ecb6 100644
--- a/calico-enterprise_versioned_docs/version-3.19-1/_includes/components/InstallEKS.js
+++ b/calico-enterprise_versioned_docs/version-3.19-1/_includes/components/InstallEKS.js
@@ -138,7 +138,7 @@ spec:
plane nodes will not be able to initiate network connections to {prodname} pods. (This is a general limitation
of EKS's custom networking support, not specific to {prodname}.) As a workaround, trusted pods that require
control plane nodes to connect to them, such as those implementing admission controller webhooks, can include{' '}
- hostNetwork:true
in their pod spec. See the Kuberentes API{' '}
+ hostNetwork:true
in their pod spec. See the Kubernetes API{' '}
pod spec
{' '}
diff --git a/calico-enterprise_versioned_docs/version-3.19-1/reference/resources/securityeventwebhook.mdx b/calico-enterprise_versioned_docs/version-3.19-1/reference/resources/securityeventwebhook.mdx
index bd28ce1d9f..0b4f928f60 100644
--- a/calico-enterprise_versioned_docs/version-3.19-1/reference/resources/securityeventwebhook.mdx
+++ b/calico-enterprise_versioned_docs/version-3.19-1/reference/resources/securityeventwebhook.mdx
@@ -76,7 +76,7 @@ The value must conform to the following rules:
| ------------ | -------------------------------------------------------------------------- | --------------------------------------------------------------------------- | ----------------------------------- |
| name | Configuration variable name. | string | yes |
| value | Direct value for the variable. | string | yes if `valueFrom` is not specifed |
-| valueFrom | Value defined either in a Kubernetes ConfigMap or in a Kubernetesa Secret. | [SecurityEventWebhookConfigVarSource](#securityeventwebhookconfigvarsource) | yes if `value` is not specified |
+| valueFrom | Value defined either in a Kubernetes ConfigMap or in a Kubernetes Secret. | [SecurityEventWebhookConfigVarSource](#securityeventwebhookconfigvarsource) | yes if `value` is not specified |
### SecurityEventWebhookConfigVarSource
From 16ba6315fb07d3ef806d216ce04ccae36b8ff648 Mon Sep 17 00:00:00 2001
From: Josh Soref <2119212+jsoref@users.noreply.github.com>
Date: Wed, 15 Nov 2023 22:43:34 -0500
Subject: [PATCH 31/55] spelling: loadbalancer
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
---
.../reference/component-resources/node/felix/configuration.mdx | 2 +-
.../reference/component-resources/node/felix/configuration.mdx | 2 +-
.../reference/component-resources/node/felix/configuration.mdx | 2 +-
.../reference/component-resources/node/felix/configuration.mdx | 2 +-
.../reference/component-resources/node/felix/configuration.mdx | 2 +-
calico/reference/felix/configuration.mdx | 2 +-
.../version-3.26/reference/felix/configuration.mdx | 2 +-
7 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/calico-enterprise/reference/component-resources/node/felix/configuration.mdx b/calico-enterprise/reference/component-resources/node/felix/configuration.mdx
index 6bd0d70c53..dd8a1d9b8d 100644
--- a/calico-enterprise/reference/component-resources/node/felix/configuration.mdx
+++ b/calico-enterprise/reference/component-resources/node/felix/configuration.mdx
@@ -105,7 +105,7 @@ The full list of parameters which can be set is as follows.
#### Feature Gates
-* `BPFConnectTimeLoadBalancingWorkaround` - Use when connect-time loadblalancer (CTLB) is turned off or if you want to turn it off for UDP only. When CTLB is turned off, host networked processes cannot always reach services. This workaround makes sure that they can. When CTLB is turned on, UDP clients may get stuck sending traffic to endpoint that does not exist anymore. So CTLB needs to be turned off sometimes.
+* `BPFConnectTimeLoadBalancingWorkaround` - Use when connect-time loadbalancer (CTLB) is turned off or if you want to turn it off for UDP only. When CTLB is turned off, host networked processes cannot always reach services. This workaround makes sure that they can. When CTLB is turned on, UDP clients may get stuck sending traffic to endpoint that does not exist anymore. So CTLB needs to be turned off sometimes.
* `enabled` - when CTLB is turned off make sure that services are always accessible.
* `udp` - turns off CTLB for UDP only and makes sure that services are always accessible. Preferred setting to make sure that DNS works.
diff --git a/calico-enterprise_versioned_docs/version-3.17/reference/component-resources/node/felix/configuration.mdx b/calico-enterprise_versioned_docs/version-3.17/reference/component-resources/node/felix/configuration.mdx
index c884f37a03..5837683fa8 100644
--- a/calico-enterprise_versioned_docs/version-3.17/reference/component-resources/node/felix/configuration.mdx
+++ b/calico-enterprise_versioned_docs/version-3.17/reference/component-resources/node/felix/configuration.mdx
@@ -104,7 +104,7 @@ The full list of parameters which can be set is as follows.
#### Feature Gates
-* `BPFConnectTimeLoadBalancingWorkaround` - Use when connect-time loadblalancer (CTLB) is turned off or if you want to turn it off for UDP only. When CTLB is turned off, host networked processes cannot always reach services. This workaround makes sure that they can. When CTLB is turned on, UDP clients may get stuck sending traffic to endpoint that does not exist anymore. So CTLB needs to be turned off sometimes.
+* `BPFConnectTimeLoadBalancingWorkaround` - Use when connect-time loadbalancer (CTLB) is turned off or if you want to turn it off for UDP only. When CTLB is turned off, host networked processes cannot always reach services. This workaround makes sure that they can. When CTLB is turned on, UDP clients may get stuck sending traffic to endpoint that does not exist anymore. So CTLB needs to be turned off sometimes.
* `enabled` - when CTLB is turned off make sure that services are always accessible.
* `udp` - turns off CTLB for UDP only and makes sure that services are always accessible. Preferred setting to make sure that DNS works.
diff --git a/calico-enterprise_versioned_docs/version-3.18-2/reference/component-resources/node/felix/configuration.mdx b/calico-enterprise_versioned_docs/version-3.18-2/reference/component-resources/node/felix/configuration.mdx
index e0e121f8da..c24ba1e047 100644
--- a/calico-enterprise_versioned_docs/version-3.18-2/reference/component-resources/node/felix/configuration.mdx
+++ b/calico-enterprise_versioned_docs/version-3.18-2/reference/component-resources/node/felix/configuration.mdx
@@ -104,7 +104,7 @@ The full list of parameters which can be set is as follows.
#### Feature Gates
-* `BPFConnectTimeLoadBalancingWorkaround` - Use when connect-time loadblalancer (CTLB) is turned off or if you want to turn it off for UDP only. When CTLB is turned off, host networked processes cannot always reach services. This workaround makes sure that they can. When CTLB is turned on, UDP clients may get stuck sending traffic to endpoint that does not exist anymore. So CTLB needs to be turned off sometimes.
+* `BPFConnectTimeLoadBalancingWorkaround` - Use when connect-time loadbalancer (CTLB) is turned off or if you want to turn it off for UDP only. When CTLB is turned off, host networked processes cannot always reach services. This workaround makes sure that they can. When CTLB is turned on, UDP clients may get stuck sending traffic to endpoint that does not exist anymore. So CTLB needs to be turned off sometimes.
* `enabled` - when CTLB is turned off make sure that services are always accessible.
* `udp` - turns off CTLB for UDP only and makes sure that services are always accessible. Preferred setting to make sure that DNS works.
diff --git a/calico-enterprise_versioned_docs/version-3.18/reference/component-resources/node/felix/configuration.mdx b/calico-enterprise_versioned_docs/version-3.18/reference/component-resources/node/felix/configuration.mdx
index e0e121f8da..c24ba1e047 100644
--- a/calico-enterprise_versioned_docs/version-3.18/reference/component-resources/node/felix/configuration.mdx
+++ b/calico-enterprise_versioned_docs/version-3.18/reference/component-resources/node/felix/configuration.mdx
@@ -104,7 +104,7 @@ The full list of parameters which can be set is as follows.
#### Feature Gates
-* `BPFConnectTimeLoadBalancingWorkaround` - Use when connect-time loadblalancer (CTLB) is turned off or if you want to turn it off for UDP only. When CTLB is turned off, host networked processes cannot always reach services. This workaround makes sure that they can. When CTLB is turned on, UDP clients may get stuck sending traffic to endpoint that does not exist anymore. So CTLB needs to be turned off sometimes.
+* `BPFConnectTimeLoadBalancingWorkaround` - Use when connect-time loadbalancer (CTLB) is turned off or if you want to turn it off for UDP only. When CTLB is turned off, host networked processes cannot always reach services. This workaround makes sure that they can. When CTLB is turned on, UDP clients may get stuck sending traffic to endpoint that does not exist anymore. So CTLB needs to be turned off sometimes.
* `enabled` - when CTLB is turned off make sure that services are always accessible.
* `udp` - turns off CTLB for UDP only and makes sure that services are always accessible. Preferred setting to make sure that DNS works.
diff --git a/calico-enterprise_versioned_docs/version-3.19-1/reference/component-resources/node/felix/configuration.mdx b/calico-enterprise_versioned_docs/version-3.19-1/reference/component-resources/node/felix/configuration.mdx
index e0e121f8da..c24ba1e047 100644
--- a/calico-enterprise_versioned_docs/version-3.19-1/reference/component-resources/node/felix/configuration.mdx
+++ b/calico-enterprise_versioned_docs/version-3.19-1/reference/component-resources/node/felix/configuration.mdx
@@ -104,7 +104,7 @@ The full list of parameters which can be set is as follows.
#### Feature Gates
-* `BPFConnectTimeLoadBalancingWorkaround` - Use when connect-time loadblalancer (CTLB) is turned off or if you want to turn it off for UDP only. When CTLB is turned off, host networked processes cannot always reach services. This workaround makes sure that they can. When CTLB is turned on, UDP clients may get stuck sending traffic to endpoint that does not exist anymore. So CTLB needs to be turned off sometimes.
+* `BPFConnectTimeLoadBalancingWorkaround` - Use when connect-time loadbalancer (CTLB) is turned off or if you want to turn it off for UDP only. When CTLB is turned off, host networked processes cannot always reach services. This workaround makes sure that they can. When CTLB is turned on, UDP clients may get stuck sending traffic to endpoint that does not exist anymore. So CTLB needs to be turned off sometimes.
* `enabled` - when CTLB is turned off make sure that services are always accessible.
* `udp` - turns off CTLB for UDP only and makes sure that services are always accessible. Preferred setting to make sure that DNS works.
diff --git a/calico/reference/felix/configuration.mdx b/calico/reference/felix/configuration.mdx
index 5345bac41e..64c0760178 100644
--- a/calico/reference/felix/configuration.mdx
+++ b/calico/reference/felix/configuration.mdx
@@ -104,7 +104,7 @@ The full list of parameters which can be set is as follows.
#### Feature Gates
-* `BPFConnectTimeLoadBalancingWorkaround` - Use when connect-time loadblalancer (CTLB) is turned off or if you want to turn it off for UDP only. When CTLB is turned off, host networked processes cannot always reach services. This workaround makes sure that they can. When CTLB is turned on, UDP clients may get stuck sending traffic to endpoint that does not exist anymore. So CTLB needs to be turned off sometimes.
+* `BPFConnectTimeLoadBalancingWorkaround` - Use when connect-time loadbalancer (CTLB) is turned off or if you want to turn it off for UDP only. When CTLB is turned off, host networked processes cannot always reach services. This workaround makes sure that they can. When CTLB is turned on, UDP clients may get stuck sending traffic to endpoint that does not exist anymore. So CTLB needs to be turned off sometimes.
* `enabled` - when CTLB is turned off make sure that services are always accessible.
* `udp` - turns off CTLB for UDP only and makes sure that services are always accessible. Preferred setting to make sure that DNS works.
diff --git a/calico_versioned_docs/version-3.26/reference/felix/configuration.mdx b/calico_versioned_docs/version-3.26/reference/felix/configuration.mdx
index 00d01366d1..1831e45564 100644
--- a/calico_versioned_docs/version-3.26/reference/felix/configuration.mdx
+++ b/calico_versioned_docs/version-3.26/reference/felix/configuration.mdx
@@ -103,7 +103,7 @@ The full list of parameters which can be set is as follows.
#### Feature Gates
-* `BPFConnectTimeLoadBalancingWorkaround` - Use when connect-time loadblalancer (CTLB) is turned off or if you want to turn it off for UDP only. When CTLB is turned off, host networked processes cannot always reach services. This workaround makes sure that they can. When CTLB is turned on, UDP clients may get stuck sending traffic to endpoint that does not exist anymore. So CTLB needs to be turned off sometimes.
+* `BPFConnectTimeLoadBalancingWorkaround` - Use when connect-time loadbalancer (CTLB) is turned off or if you want to turn it off for UDP only. When CTLB is turned off, host networked processes cannot always reach services. This workaround makes sure that they can. When CTLB is turned on, UDP clients may get stuck sending traffic to endpoint that does not exist anymore. So CTLB needs to be turned off sometimes.
* `enabled` - when CTLB is turned off make sure that services are always accessible.
* `udp` - turns off CTLB for UDP only and makes sure that services are always accessible. Preferred setting to make sure that DNS works.
From 93d87fee49917d9d99369f23b97ff7c73620e470 Mon Sep 17 00:00:00 2001
From: Josh Soref <2119212+jsoref@users.noreply.github.com>
Date: Wed, 15 Nov 2023 18:37:00 -0500
Subject: [PATCH 32/55] spelling: macos
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
---
calico-cloud/image-assurance/scanners/pipeline-scanner.mdx | 2 +-
.../version-19-1/image-assurance/scanners/pipeline-scanner.mdx | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/calico-cloud/image-assurance/scanners/pipeline-scanner.mdx b/calico-cloud/image-assurance/scanners/pipeline-scanner.mdx
index 2ca5d47cb2..17d83bc9f8 100644
--- a/calico-cloud/image-assurance/scanners/pipeline-scanner.mdx
+++ b/calico-cloud/image-assurance/scanners/pipeline-scanner.mdx
@@ -52,7 +52,7 @@ If you change the name of above heading, open a ticket to update the hardcoded C
curl -Lo tigera-scanner {{clouddownloadbase}}/tigera-scanner/{{cloudversion}}/image-assurance-scanner-cli-linux-amd64
```
- **MacOS**
+ **macOS**
```shell
curl -Lo tigera-scanner {{clouddownloadbase}}/tigera-scanner/{{cloudversion}}/image-assurance-scanner-cli-darwin-amd64
diff --git a/calico-cloud_versioned_docs/version-19-1/image-assurance/scanners/pipeline-scanner.mdx b/calico-cloud_versioned_docs/version-19-1/image-assurance/scanners/pipeline-scanner.mdx
index 2ca5d47cb2..17d83bc9f8 100644
--- a/calico-cloud_versioned_docs/version-19-1/image-assurance/scanners/pipeline-scanner.mdx
+++ b/calico-cloud_versioned_docs/version-19-1/image-assurance/scanners/pipeline-scanner.mdx
@@ -52,7 +52,7 @@ If you change the name of above heading, open a ticket to update the hardcoded C
curl -Lo tigera-scanner {{clouddownloadbase}}/tigera-scanner/{{cloudversion}}/image-assurance-scanner-cli-linux-amd64
```
- **MacOS**
+ **macOS**
```shell
curl -Lo tigera-scanner {{clouddownloadbase}}/tigera-scanner/{{cloudversion}}/image-assurance-scanner-cli-darwin-amd64
From 697b10af27a3a59f23f6c820138d13e23aebda24 Mon Sep 17 00:00:00 2001
From: Josh Soref <2119212+jsoref@users.noreply.github.com>
Date: Wed, 15 Nov 2023 22:46:34 -0500
Subject: [PATCH 33/55] spelling: maintenance
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
---
calico-cloud/network-policy/hosts/host-forwarded-traffic.mdx | 2 +-
.../network-policy/hosts/host-forwarded-traffic.mdx | 2 +-
.../network-policy/hosts/host-forwarded-traffic.mdx | 2 +-
.../network-policy/hosts/host-forwarded-traffic.mdx | 2 +-
.../network-policy/hosts/host-forwarded-traffic.mdx | 2 +-
.../network-policy/hosts/host-forwarded-traffic.mdx | 2 +-
.../network-policy/hosts/host-forwarded-traffic.mdx | 2 +-
.../network-policy/hosts/host-forwarded-traffic.mdx | 2 +-
calico/network-policy/hosts/host-forwarded-traffic.mdx | 2 +-
.../network-policy/hosts/host-forwarded-traffic.mdx | 2 +-
.../network-policy/hosts/host-forwarded-traffic.mdx | 2 +-
.../network-policy/hosts/host-forwarded-traffic.mdx | 2 +-
12 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/calico-cloud/network-policy/hosts/host-forwarded-traffic.mdx b/calico-cloud/network-policy/hosts/host-forwarded-traffic.mdx
index 2a8858b279..3e26ac8422 100644
--- a/calico-cloud/network-policy/hosts/host-forwarded-traffic.mdx
+++ b/calico-cloud/network-policy/hosts/host-forwarded-traffic.mdx
@@ -110,7 +110,7 @@ spec:
- 22
```
-Save this as allow-ssh-maintenace.yaml.
+Save this as allow-ssh-maintenance.yaml.
Apply the policy to the cluster:
diff --git a/calico-cloud_versioned_docs/version-19-1/network-policy/hosts/host-forwarded-traffic.mdx b/calico-cloud_versioned_docs/version-19-1/network-policy/hosts/host-forwarded-traffic.mdx
index 2a8858b279..3e26ac8422 100644
--- a/calico-cloud_versioned_docs/version-19-1/network-policy/hosts/host-forwarded-traffic.mdx
+++ b/calico-cloud_versioned_docs/version-19-1/network-policy/hosts/host-forwarded-traffic.mdx
@@ -110,7 +110,7 @@ spec:
- 22
```
-Save this as allow-ssh-maintenace.yaml.
+Save this as allow-ssh-maintenance.yaml.
Apply the policy to the cluster:
diff --git a/calico-enterprise/network-policy/hosts/host-forwarded-traffic.mdx b/calico-enterprise/network-policy/hosts/host-forwarded-traffic.mdx
index ae65428f74..edef086c7f 100644
--- a/calico-enterprise/network-policy/hosts/host-forwarded-traffic.mdx
+++ b/calico-enterprise/network-policy/hosts/host-forwarded-traffic.mdx
@@ -110,7 +110,7 @@ spec:
- 22
```
-Save this as allow-ssh-maintenace.yaml.
+Save this as allow-ssh-maintenance.yaml.
Apply the policy to the cluster:
diff --git a/calico-enterprise_versioned_docs/version-3.16/network-policy/hosts/host-forwarded-traffic.mdx b/calico-enterprise_versioned_docs/version-3.16/network-policy/hosts/host-forwarded-traffic.mdx
index c20a8a998c..c5191cc65d 100644
--- a/calico-enterprise_versioned_docs/version-3.16/network-policy/hosts/host-forwarded-traffic.mdx
+++ b/calico-enterprise_versioned_docs/version-3.16/network-policy/hosts/host-forwarded-traffic.mdx
@@ -110,7 +110,7 @@ spec:
- 22
```
-Save this as allow-ssh-maintenace.yaml.
+Save this as allow-ssh-maintenance.yaml.
Apply the policy to the cluster:
diff --git a/calico-enterprise_versioned_docs/version-3.17/network-policy/hosts/host-forwarded-traffic.mdx b/calico-enterprise_versioned_docs/version-3.17/network-policy/hosts/host-forwarded-traffic.mdx
index ae65428f74..edef086c7f 100644
--- a/calico-enterprise_versioned_docs/version-3.17/network-policy/hosts/host-forwarded-traffic.mdx
+++ b/calico-enterprise_versioned_docs/version-3.17/network-policy/hosts/host-forwarded-traffic.mdx
@@ -110,7 +110,7 @@ spec:
- 22
```
-Save this as allow-ssh-maintenace.yaml.
+Save this as allow-ssh-maintenance.yaml.
Apply the policy to the cluster:
diff --git a/calico-enterprise_versioned_docs/version-3.18-2/network-policy/hosts/host-forwarded-traffic.mdx b/calico-enterprise_versioned_docs/version-3.18-2/network-policy/hosts/host-forwarded-traffic.mdx
index ae65428f74..edef086c7f 100644
--- a/calico-enterprise_versioned_docs/version-3.18-2/network-policy/hosts/host-forwarded-traffic.mdx
+++ b/calico-enterprise_versioned_docs/version-3.18-2/network-policy/hosts/host-forwarded-traffic.mdx
@@ -110,7 +110,7 @@ spec:
- 22
```
-Save this as allow-ssh-maintenace.yaml.
+Save this as allow-ssh-maintenance.yaml.
Apply the policy to the cluster:
diff --git a/calico-enterprise_versioned_docs/version-3.18/network-policy/hosts/host-forwarded-traffic.mdx b/calico-enterprise_versioned_docs/version-3.18/network-policy/hosts/host-forwarded-traffic.mdx
index ae65428f74..edef086c7f 100644
--- a/calico-enterprise_versioned_docs/version-3.18/network-policy/hosts/host-forwarded-traffic.mdx
+++ b/calico-enterprise_versioned_docs/version-3.18/network-policy/hosts/host-forwarded-traffic.mdx
@@ -110,7 +110,7 @@ spec:
- 22
```
-Save this as allow-ssh-maintenace.yaml.
+Save this as allow-ssh-maintenance.yaml.
Apply the policy to the cluster:
diff --git a/calico-enterprise_versioned_docs/version-3.19-1/network-policy/hosts/host-forwarded-traffic.mdx b/calico-enterprise_versioned_docs/version-3.19-1/network-policy/hosts/host-forwarded-traffic.mdx
index ae65428f74..edef086c7f 100644
--- a/calico-enterprise_versioned_docs/version-3.19-1/network-policy/hosts/host-forwarded-traffic.mdx
+++ b/calico-enterprise_versioned_docs/version-3.19-1/network-policy/hosts/host-forwarded-traffic.mdx
@@ -110,7 +110,7 @@ spec:
- 22
```
-Save this as allow-ssh-maintenace.yaml.
+Save this as allow-ssh-maintenance.yaml.
Apply the policy to the cluster:
diff --git a/calico/network-policy/hosts/host-forwarded-traffic.mdx b/calico/network-policy/hosts/host-forwarded-traffic.mdx
index 75e9b7399f..c3ae605d3e 100644
--- a/calico/network-policy/hosts/host-forwarded-traffic.mdx
+++ b/calico/network-policy/hosts/host-forwarded-traffic.mdx
@@ -110,7 +110,7 @@ spec:
- 22
```
-Save this as allow-ssh-maintenace.yaml.
+Save this as allow-ssh-maintenance.yaml.
Apply the policy to the cluster:
diff --git a/calico_versioned_docs/version-3.25/network-policy/hosts/host-forwarded-traffic.mdx b/calico_versioned_docs/version-3.25/network-policy/hosts/host-forwarded-traffic.mdx
index 6d3721402a..6fffb89a07 100644
--- a/calico_versioned_docs/version-3.25/network-policy/hosts/host-forwarded-traffic.mdx
+++ b/calico_versioned_docs/version-3.25/network-policy/hosts/host-forwarded-traffic.mdx
@@ -110,7 +110,7 @@ spec:
- 22
```
-Save this as allow-ssh-maintenace.yaml.
+Save this as allow-ssh-maintenance.yaml.
Apply the policy to the cluster:
diff --git a/calico_versioned_docs/version-3.26/network-policy/hosts/host-forwarded-traffic.mdx b/calico_versioned_docs/version-3.26/network-policy/hosts/host-forwarded-traffic.mdx
index 75e9b7399f..c3ae605d3e 100644
--- a/calico_versioned_docs/version-3.26/network-policy/hosts/host-forwarded-traffic.mdx
+++ b/calico_versioned_docs/version-3.26/network-policy/hosts/host-forwarded-traffic.mdx
@@ -110,7 +110,7 @@ spec:
- 22
```
-Save this as allow-ssh-maintenace.yaml.
+Save this as allow-ssh-maintenance.yaml.
Apply the policy to the cluster:
diff --git a/calico_versioned_docs/version-3.27/network-policy/hosts/host-forwarded-traffic.mdx b/calico_versioned_docs/version-3.27/network-policy/hosts/host-forwarded-traffic.mdx
index 75e9b7399f..c3ae605d3e 100644
--- a/calico_versioned_docs/version-3.27/network-policy/hosts/host-forwarded-traffic.mdx
+++ b/calico_versioned_docs/version-3.27/network-policy/hosts/host-forwarded-traffic.mdx
@@ -110,7 +110,7 @@ spec:
- 22
```
-Save this as allow-ssh-maintenace.yaml.
+Save this as allow-ssh-maintenance.yaml.
Apply the policy to the cluster:
From db2cad146fec9c56e2aec62471624b01ebbf6d6c Mon Sep 17 00:00:00 2001
From: Josh Soref <2119212+jsoref@users.noreply.github.com>
Date: Wed, 15 Nov 2023 22:48:41 -0500
Subject: [PATCH 34/55] spelling: nelljerram
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
---
.../_includes/release-notes/_v3.14.0-pre-release-notes.mdx | 2 +-
calico-cloud/_includes/release-notes/_v3.16.0-release-notes.mdx | 2 +-
calico-cloud/_includes/release-notes/_v3.16.1-release-notes.mdx | 2 +-
.../_includes/release-notes/_v3.14.0-pre-release-notes.mdx | 2 +-
.../_includes/release-notes/_v3.16.0-release-notes.mdx | 2 +-
.../_includes/release-notes/_v3.16.1-release-notes.mdx | 2 +-
6 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/calico-cloud/_includes/release-notes/_v3.14.0-pre-release-notes.mdx b/calico-cloud/_includes/release-notes/_v3.14.0-pre-release-notes.mdx
index ff8c910e9b..2bb2ad04e1 100644
--- a/calico-cloud/_includes/release-notes/_v3.14.0-pre-release-notes.mdx
+++ b/calico-cloud/_includes/release-notes/_v3.14.0-pre-release-notes.mdx
@@ -19,7 +19,7 @@
- In BPF dataplane mode, Felix now handles single-block IPAM pools. Previously single-block pools resulted in a collision when programming the dataplane routes. [felix #2245](https://github.com/projectcalico/felix/pull/2245) (@fasaxc)
- None required [felix #2233](https://github.com/projectcalico/felix/pull/2233) (@tomastigera)
- None required [felix #2232](https://github.com/projectcalico/felix/pull/2232) (@tomastigera)
-- [Openstack] Allow DHCP from the workload, on kernels where rp_filter doesn't already [felix #2231](https://github.com/projectcalico/felix/pull/2231) (@neiljerram)
+- [Openstack] Allow DHCP from the workload, on kernels where rp_filter doesn't already [felix #2231](https://github.com/projectcalico/felix/pull/2231) (@nelljerram)
- all-interfaces host endpoints now supports normal network policy in addition to pre-dnat policy [felix #2228](https://github.com/projectcalico/felix/pull/2228) (@lmm)
- Add FelixConfiguration option for setting route information source [libcalico-go #1222](https://github.com/projectcalico/libcalico-go/pull/1222) (@caseydavenport)
- Added Wireguard configuration. [libcalico-go #1215](https://github.com/projectcalico/libcalico-go/pull/1215) (@realgaurav)
diff --git a/calico-cloud/_includes/release-notes/_v3.16.0-release-notes.mdx b/calico-cloud/_includes/release-notes/_v3.16.0-release-notes.mdx
index 1a6fa9627c..788cbfb1e7 100644
--- a/calico-cloud/_includes/release-notes/_v3.16.0-release-notes.mdx
+++ b/calico-cloud/_includes/release-notes/_v3.16.0-release-notes.mdx
@@ -46,7 +46,7 @@ Calico now supports BGP communities! Check out the BGP configuration resource [r
- In BPF mode, Felix now rate-limits stale BPF map cleanup to save CPU. [felix #2428](https://github.com/projectcalico/felix/pull/2428) (@fasaxc)
- In BPF mode, Felix now detects BPF support on Red Hat kernels with backports as well as generic kernels. [felix #2409](https://github.com/projectcalico/felix/pull/2409) (@sridhartigera)
- In BPF mode, Felix now uses a more efficient algorithm to resync the Kubernetes services with the dataplane. This speeds up the initial sync (especially with large numbers of services). [felix #2401](https://github.com/projectcalico/felix/pull/2401) (@tomastigera)
-- eBPF dataplane support for encryption via Wireguard [felix #2389](https://github.com/projectcalico/felix/pull/2389) (@neiljerram)
+- eBPF dataplane support for encryption via Wireguard [felix #2389](https://github.com/projectcalico/felix/pull/2389) (@nelljerram)
- Reject connections to services with no backends [felix #2380](https://github.com/projectcalico/felix/pull/2380) (@sridhartigera)
- Implementation to handle setting source-destination-check for AWS EC2 instances. [felix #2381](https://github.com/projectcalico/felix/pull/2381) (@realgaurav)
- In BPF mode, Felix now applies policy updates without reapplying the BPF programs; this gives a performance boost and closes a window where traffic was not policed. [felix #2363](https://github.com/projectcalico/felix/pull/2363) (@fasaxc)
diff --git a/calico-cloud/_includes/release-notes/_v3.16.1-release-notes.mdx b/calico-cloud/_includes/release-notes/_v3.16.1-release-notes.mdx
index 4ceb8c19e6..5ab00e3744 100644
--- a/calico-cloud/_includes/release-notes/_v3.16.1-release-notes.mdx
+++ b/calico-cloud/_includes/release-notes/_v3.16.1-release-notes.mdx
@@ -3,7 +3,7 @@
### Bug fixes
- Fix population of etcd certificates in CNI config [cni-plugin #949](https://github.com/projectcalico/cni-plugin/pull/949) (@caseydavenport)
-- Resolves an issue on nodes whose Kubernetes node name does not exactly match the system hostname [cni-plugin #943](https://github.com/projectcalico/cni-plugin/pull/943) (@neiljerram)
+- Resolves an issue on nodes whose Kubernetes node name does not exactly match the system hostname [cni-plugin #943](https://github.com/projectcalico/cni-plugin/pull/943) (@nelljerram)
- Fix flannel migration issues when running on Rancher [kube-controllers #506](https://github.com/projectcalico/kube-controllers/pull/506) (@songjiang)
- Fix `kubectl exec` format for migration controller [kube-controllers #504](https://github.com/projectcalico/kube-controllers/pull/504) (@songjiang)
- Fix flannel migration for clusters with multiple control plane nodes. [kube-controllers #503](https://github.com/projectcalico/kube-controllers/pull/503) (@caseydavenport)
diff --git a/calico-cloud_versioned_docs/version-19-1/_includes/release-notes/_v3.14.0-pre-release-notes.mdx b/calico-cloud_versioned_docs/version-19-1/_includes/release-notes/_v3.14.0-pre-release-notes.mdx
index ff8c910e9b..2bb2ad04e1 100644
--- a/calico-cloud_versioned_docs/version-19-1/_includes/release-notes/_v3.14.0-pre-release-notes.mdx
+++ b/calico-cloud_versioned_docs/version-19-1/_includes/release-notes/_v3.14.0-pre-release-notes.mdx
@@ -19,7 +19,7 @@
- In BPF dataplane mode, Felix now handles single-block IPAM pools. Previously single-block pools resulted in a collision when programming the dataplane routes. [felix #2245](https://github.com/projectcalico/felix/pull/2245) (@fasaxc)
- None required [felix #2233](https://github.com/projectcalico/felix/pull/2233) (@tomastigera)
- None required [felix #2232](https://github.com/projectcalico/felix/pull/2232) (@tomastigera)
-- [Openstack] Allow DHCP from the workload, on kernels where rp_filter doesn't already [felix #2231](https://github.com/projectcalico/felix/pull/2231) (@neiljerram)
+- [Openstack] Allow DHCP from the workload, on kernels where rp_filter doesn't already [felix #2231](https://github.com/projectcalico/felix/pull/2231) (@nelljerram)
- all-interfaces host endpoints now supports normal network policy in addition to pre-dnat policy [felix #2228](https://github.com/projectcalico/felix/pull/2228) (@lmm)
- Add FelixConfiguration option for setting route information source [libcalico-go #1222](https://github.com/projectcalico/libcalico-go/pull/1222) (@caseydavenport)
- Added Wireguard configuration. [libcalico-go #1215](https://github.com/projectcalico/libcalico-go/pull/1215) (@realgaurav)
diff --git a/calico-cloud_versioned_docs/version-19-1/_includes/release-notes/_v3.16.0-release-notes.mdx b/calico-cloud_versioned_docs/version-19-1/_includes/release-notes/_v3.16.0-release-notes.mdx
index 1a6fa9627c..788cbfb1e7 100644
--- a/calico-cloud_versioned_docs/version-19-1/_includes/release-notes/_v3.16.0-release-notes.mdx
+++ b/calico-cloud_versioned_docs/version-19-1/_includes/release-notes/_v3.16.0-release-notes.mdx
@@ -46,7 +46,7 @@ Calico now supports BGP communities! Check out the BGP configuration resource [r
- In BPF mode, Felix now rate-limits stale BPF map cleanup to save CPU. [felix #2428](https://github.com/projectcalico/felix/pull/2428) (@fasaxc)
- In BPF mode, Felix now detects BPF support on Red Hat kernels with backports as well as generic kernels. [felix #2409](https://github.com/projectcalico/felix/pull/2409) (@sridhartigera)
- In BPF mode, Felix now uses a more efficient algorithm to resync the Kubernetes services with the dataplane. This speeds up the initial sync (especially with large numbers of services). [felix #2401](https://github.com/projectcalico/felix/pull/2401) (@tomastigera)
-- eBPF dataplane support for encryption via Wireguard [felix #2389](https://github.com/projectcalico/felix/pull/2389) (@neiljerram)
+- eBPF dataplane support for encryption via Wireguard [felix #2389](https://github.com/projectcalico/felix/pull/2389) (@nelljerram)
- Reject connections to services with no backends [felix #2380](https://github.com/projectcalico/felix/pull/2380) (@sridhartigera)
- Implementation to handle setting source-destination-check for AWS EC2 instances. [felix #2381](https://github.com/projectcalico/felix/pull/2381) (@realgaurav)
- In BPF mode, Felix now applies policy updates without reapplying the BPF programs; this gives a performance boost and closes a window where traffic was not policed. [felix #2363](https://github.com/projectcalico/felix/pull/2363) (@fasaxc)
diff --git a/calico-cloud_versioned_docs/version-19-1/_includes/release-notes/_v3.16.1-release-notes.mdx b/calico-cloud_versioned_docs/version-19-1/_includes/release-notes/_v3.16.1-release-notes.mdx
index 4ceb8c19e6..5ab00e3744 100644
--- a/calico-cloud_versioned_docs/version-19-1/_includes/release-notes/_v3.16.1-release-notes.mdx
+++ b/calico-cloud_versioned_docs/version-19-1/_includes/release-notes/_v3.16.1-release-notes.mdx
@@ -3,7 +3,7 @@
### Bug fixes
- Fix population of etcd certificates in CNI config [cni-plugin #949](https://github.com/projectcalico/cni-plugin/pull/949) (@caseydavenport)
-- Resolves an issue on nodes whose Kubernetes node name does not exactly match the system hostname [cni-plugin #943](https://github.com/projectcalico/cni-plugin/pull/943) (@neiljerram)
+- Resolves an issue on nodes whose Kubernetes node name does not exactly match the system hostname [cni-plugin #943](https://github.com/projectcalico/cni-plugin/pull/943) (@nelljerram)
- Fix flannel migration issues when running on Rancher [kube-controllers #506](https://github.com/projectcalico/kube-controllers/pull/506) (@songjiang)
- Fix `kubectl exec` format for migration controller [kube-controllers #504](https://github.com/projectcalico/kube-controllers/pull/504) (@songjiang)
- Fix flannel migration for clusters with multiple control plane nodes. [kube-controllers #503](https://github.com/projectcalico/kube-controllers/pull/503) (@caseydavenport)
From 44bf37095dc3e00b052574a9b5d87e1a4bc267a7 Mon Sep 17 00:00:00 2001
From: Josh Soref <2119212+jsoref@users.noreply.github.com>
Date: Wed, 15 Nov 2023 18:36:46 -0500
Subject: [PATCH 35/55] spelling: nonexistent
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
---
.../_includes/release-notes/_v3.14.0-pre-release-notes.mdx | 2 +-
.../_includes/release-notes/_v3.14.0-pre-release-notes.mdx | 2 +-
calico-enterprise/network-policy/hosts/protect-hosts.mdx | 4 ++--
.../version-3.16/network-policy/hosts/protect-hosts.mdx | 4 ++--
.../version-3.17/network-policy/hosts/protect-hosts.mdx | 4 ++--
.../version-3.18-2/network-policy/hosts/protect-hosts.mdx | 4 ++--
.../version-3.18/network-policy/hosts/protect-hosts.mdx | 4 ++--
.../version-3.19-1/network-policy/hosts/protect-hosts.mdx | 4 ++--
calico/network-policy/hosts/protect-hosts.mdx | 4 ++--
.../version-3.25/network-policy/hosts/protect-hosts.mdx | 4 ++--
.../version-3.26/network-policy/hosts/protect-hosts.mdx | 4 ++--
.../version-3.27/network-policy/hosts/protect-hosts.mdx | 4 ++--
12 files changed, 22 insertions(+), 22 deletions(-)
diff --git a/calico-cloud/_includes/release-notes/_v3.14.0-pre-release-notes.mdx b/calico-cloud/_includes/release-notes/_v3.14.0-pre-release-notes.mdx
index 2bb2ad04e1..d5f07cd8a1 100644
--- a/calico-cloud/_includes/release-notes/_v3.14.0-pre-release-notes.mdx
+++ b/calico-cloud/_includes/release-notes/_v3.14.0-pre-release-notes.mdx
@@ -34,7 +34,7 @@
- auto host endpoints have a default allow profile [kube-controllers #470](https://github.com/projectcalico/kube-controllers/pull/470) (@lmm)
- Fix IPAM garbage collection in etcd mode on clusters where node name does not match Kubernetes node name. [kube-controllers #467](https://github.com/projectcalico/kube-controllers/pull/467) (@caseydavenport)
- Use KubeControllersConfiguration resource for config [kube-controllers #464](https://github.com/projectcalico/kube-controllers/pull/464) (@spikecurtis)
-- Fix kube-controllers attempting to clean up non-existent node resources [kube-controllers #461](https://github.com/projectcalico/kube-controllers/pull/461) (@fcuello-fudo)
+- Fix kube-controllers attempting to clean up nonexistent node resources [kube-controllers #461](https://github.com/projectcalico/kube-controllers/pull/461) (@fcuello-fudo)
- kube-controllers can now automatically provision host endpoints for nodes in the cluster [kube-controllers #458](https://github.com/projectcalico/kube-controllers/pull/458) (@lmm)
- Kubernetes network tutorials updated for v1.18. [calico #3447](https://github.com/projectcalico/calico/pull/3447) (@tmjd)
- With OpenShift install time resources can be created. This means Calico resources can be created before the Calico components are started. [calico #3338](https://github.com/projectcalico/calico/pull/3338) (@tmjd)
diff --git a/calico-cloud_versioned_docs/version-19-1/_includes/release-notes/_v3.14.0-pre-release-notes.mdx b/calico-cloud_versioned_docs/version-19-1/_includes/release-notes/_v3.14.0-pre-release-notes.mdx
index 2bb2ad04e1..d5f07cd8a1 100644
--- a/calico-cloud_versioned_docs/version-19-1/_includes/release-notes/_v3.14.0-pre-release-notes.mdx
+++ b/calico-cloud_versioned_docs/version-19-1/_includes/release-notes/_v3.14.0-pre-release-notes.mdx
@@ -34,7 +34,7 @@
- auto host endpoints have a default allow profile [kube-controllers #470](https://github.com/projectcalico/kube-controllers/pull/470) (@lmm)
- Fix IPAM garbage collection in etcd mode on clusters where node name does not match Kubernetes node name. [kube-controllers #467](https://github.com/projectcalico/kube-controllers/pull/467) (@caseydavenport)
- Use KubeControllersConfiguration resource for config [kube-controllers #464](https://github.com/projectcalico/kube-controllers/pull/464) (@spikecurtis)
-- Fix kube-controllers attempting to clean up non-existent node resources [kube-controllers #461](https://github.com/projectcalico/kube-controllers/pull/461) (@fcuello-fudo)
+- Fix kube-controllers attempting to clean up nonexistent node resources [kube-controllers #461](https://github.com/projectcalico/kube-controllers/pull/461) (@fcuello-fudo)
- kube-controllers can now automatically provision host endpoints for nodes in the cluster [kube-controllers #458](https://github.com/projectcalico/kube-controllers/pull/458) (@lmm)
- Kubernetes network tutorials updated for v1.18. [calico #3447](https://github.com/projectcalico/calico/pull/3447) (@tmjd)
- With OpenShift install time resources can be created. This means Calico resources can be created before the Calico components are started. [calico #3338](https://github.com/projectcalico/calico/pull/3338) (@tmjd)
diff --git a/calico-enterprise/network-policy/hosts/protect-hosts.mdx b/calico-enterprise/network-policy/hosts/protect-hosts.mdx
index 8aab3e501f..c4d4031a54 100644
--- a/calico-enterprise/network-policy/hosts/protect-hosts.mdx
+++ b/calico-enterprise/network-policy/hosts/protect-hosts.mdx
@@ -24,7 +24,7 @@ Each host has one or more network interfaces that it uses to communicate externa
### Failsafe rules
-It is easy to inadvertently cut all host connectivity because of non-existent or misconfigured network policy. To avoid this, {{prodname}} provides failsafe rules with default/configurable ports that are open on all host endpoints.
+It is easy to inadvertently cut all host connectivity because of nonexistent or misconfigured network policy. To avoid this, {{prodname}} provides failsafe rules with default/configurable ports that are open on all host endpoints.
### Default behavior of workload to host traffic
@@ -58,7 +58,7 @@ If you are already running {{prodname}} for Kubernetes, you are good to go. If y
### Avoid accidentally cutting all host connectivity
-To avoid inadvertently cutting all host connectivity because of non-existent or misconfigured network policy, {{prodname}} uses failsafe rules that open specific ports and CIDRs on all host endpoints.
+To avoid inadvertently cutting all host connectivity because of nonexistent or misconfigured network policy, {{prodname}} uses failsafe rules that open specific ports and CIDRs on all host endpoints.
Review the following table to determine if the defaults work for your implementation. If not, change the default ports using the parameters, **FailsafeInboundHostPorts** and **FailsafeOutboundHostPorts** in [Configuring Felix](../../reference/component-resources/node/felix/configuration.mdx#environment-variables).
diff --git a/calico-enterprise_versioned_docs/version-3.16/network-policy/hosts/protect-hosts.mdx b/calico-enterprise_versioned_docs/version-3.16/network-policy/hosts/protect-hosts.mdx
index 8aab3e501f..c4d4031a54 100644
--- a/calico-enterprise_versioned_docs/version-3.16/network-policy/hosts/protect-hosts.mdx
+++ b/calico-enterprise_versioned_docs/version-3.16/network-policy/hosts/protect-hosts.mdx
@@ -24,7 +24,7 @@ Each host has one or more network interfaces that it uses to communicate externa
### Failsafe rules
-It is easy to inadvertently cut all host connectivity because of non-existent or misconfigured network policy. To avoid this, {{prodname}} provides failsafe rules with default/configurable ports that are open on all host endpoints.
+It is easy to inadvertently cut all host connectivity because of nonexistent or misconfigured network policy. To avoid this, {{prodname}} provides failsafe rules with default/configurable ports that are open on all host endpoints.
### Default behavior of workload to host traffic
@@ -58,7 +58,7 @@ If you are already running {{prodname}} for Kubernetes, you are good to go. If y
### Avoid accidentally cutting all host connectivity
-To avoid inadvertently cutting all host connectivity because of non-existent or misconfigured network policy, {{prodname}} uses failsafe rules that open specific ports and CIDRs on all host endpoints.
+To avoid inadvertently cutting all host connectivity because of nonexistent or misconfigured network policy, {{prodname}} uses failsafe rules that open specific ports and CIDRs on all host endpoints.
Review the following table to determine if the defaults work for your implementation. If not, change the default ports using the parameters, **FailsafeInboundHostPorts** and **FailsafeOutboundHostPorts** in [Configuring Felix](../../reference/component-resources/node/felix/configuration.mdx#environment-variables).
diff --git a/calico-enterprise_versioned_docs/version-3.17/network-policy/hosts/protect-hosts.mdx b/calico-enterprise_versioned_docs/version-3.17/network-policy/hosts/protect-hosts.mdx
index 8aab3e501f..c4d4031a54 100644
--- a/calico-enterprise_versioned_docs/version-3.17/network-policy/hosts/protect-hosts.mdx
+++ b/calico-enterprise_versioned_docs/version-3.17/network-policy/hosts/protect-hosts.mdx
@@ -24,7 +24,7 @@ Each host has one or more network interfaces that it uses to communicate externa
### Failsafe rules
-It is easy to inadvertently cut all host connectivity because of non-existent or misconfigured network policy. To avoid this, {{prodname}} provides failsafe rules with default/configurable ports that are open on all host endpoints.
+It is easy to inadvertently cut all host connectivity because of nonexistent or misconfigured network policy. To avoid this, {{prodname}} provides failsafe rules with default/configurable ports that are open on all host endpoints.
### Default behavior of workload to host traffic
@@ -58,7 +58,7 @@ If you are already running {{prodname}} for Kubernetes, you are good to go. If y
### Avoid accidentally cutting all host connectivity
-To avoid inadvertently cutting all host connectivity because of non-existent or misconfigured network policy, {{prodname}} uses failsafe rules that open specific ports and CIDRs on all host endpoints.
+To avoid inadvertently cutting all host connectivity because of nonexistent or misconfigured network policy, {{prodname}} uses failsafe rules that open specific ports and CIDRs on all host endpoints.
Review the following table to determine if the defaults work for your implementation. If not, change the default ports using the parameters, **FailsafeInboundHostPorts** and **FailsafeOutboundHostPorts** in [Configuring Felix](../../reference/component-resources/node/felix/configuration.mdx#environment-variables).
diff --git a/calico-enterprise_versioned_docs/version-3.18-2/network-policy/hosts/protect-hosts.mdx b/calico-enterprise_versioned_docs/version-3.18-2/network-policy/hosts/protect-hosts.mdx
index 8aab3e501f..c4d4031a54 100644
--- a/calico-enterprise_versioned_docs/version-3.18-2/network-policy/hosts/protect-hosts.mdx
+++ b/calico-enterprise_versioned_docs/version-3.18-2/network-policy/hosts/protect-hosts.mdx
@@ -24,7 +24,7 @@ Each host has one or more network interfaces that it uses to communicate externa
### Failsafe rules
-It is easy to inadvertently cut all host connectivity because of non-existent or misconfigured network policy. To avoid this, {{prodname}} provides failsafe rules with default/configurable ports that are open on all host endpoints.
+It is easy to inadvertently cut all host connectivity because of nonexistent or misconfigured network policy. To avoid this, {{prodname}} provides failsafe rules with default/configurable ports that are open on all host endpoints.
### Default behavior of workload to host traffic
@@ -58,7 +58,7 @@ If you are already running {{prodname}} for Kubernetes, you are good to go. If y
### Avoid accidentally cutting all host connectivity
-To avoid inadvertently cutting all host connectivity because of non-existent or misconfigured network policy, {{prodname}} uses failsafe rules that open specific ports and CIDRs on all host endpoints.
+To avoid inadvertently cutting all host connectivity because of nonexistent or misconfigured network policy, {{prodname}} uses failsafe rules that open specific ports and CIDRs on all host endpoints.
Review the following table to determine if the defaults work for your implementation. If not, change the default ports using the parameters, **FailsafeInboundHostPorts** and **FailsafeOutboundHostPorts** in [Configuring Felix](../../reference/component-resources/node/felix/configuration.mdx#environment-variables).
diff --git a/calico-enterprise_versioned_docs/version-3.18/network-policy/hosts/protect-hosts.mdx b/calico-enterprise_versioned_docs/version-3.18/network-policy/hosts/protect-hosts.mdx
index 8aab3e501f..c4d4031a54 100644
--- a/calico-enterprise_versioned_docs/version-3.18/network-policy/hosts/protect-hosts.mdx
+++ b/calico-enterprise_versioned_docs/version-3.18/network-policy/hosts/protect-hosts.mdx
@@ -24,7 +24,7 @@ Each host has one or more network interfaces that it uses to communicate externa
### Failsafe rules
-It is easy to inadvertently cut all host connectivity because of non-existent or misconfigured network policy. To avoid this, {{prodname}} provides failsafe rules with default/configurable ports that are open on all host endpoints.
+It is easy to inadvertently cut all host connectivity because of nonexistent or misconfigured network policy. To avoid this, {{prodname}} provides failsafe rules with default/configurable ports that are open on all host endpoints.
### Default behavior of workload to host traffic
@@ -58,7 +58,7 @@ If you are already running {{prodname}} for Kubernetes, you are good to go. If y
### Avoid accidentally cutting all host connectivity
-To avoid inadvertently cutting all host connectivity because of non-existent or misconfigured network policy, {{prodname}} uses failsafe rules that open specific ports and CIDRs on all host endpoints.
+To avoid inadvertently cutting all host connectivity because of nonexistent or misconfigured network policy, {{prodname}} uses failsafe rules that open specific ports and CIDRs on all host endpoints.
Review the following table to determine if the defaults work for your implementation. If not, change the default ports using the parameters, **FailsafeInboundHostPorts** and **FailsafeOutboundHostPorts** in [Configuring Felix](../../reference/component-resources/node/felix/configuration.mdx#environment-variables).
diff --git a/calico-enterprise_versioned_docs/version-3.19-1/network-policy/hosts/protect-hosts.mdx b/calico-enterprise_versioned_docs/version-3.19-1/network-policy/hosts/protect-hosts.mdx
index 8aab3e501f..c4d4031a54 100644
--- a/calico-enterprise_versioned_docs/version-3.19-1/network-policy/hosts/protect-hosts.mdx
+++ b/calico-enterprise_versioned_docs/version-3.19-1/network-policy/hosts/protect-hosts.mdx
@@ -24,7 +24,7 @@ Each host has one or more network interfaces that it uses to communicate externa
### Failsafe rules
-It is easy to inadvertently cut all host connectivity because of non-existent or misconfigured network policy. To avoid this, {{prodname}} provides failsafe rules with default/configurable ports that are open on all host endpoints.
+It is easy to inadvertently cut all host connectivity because of nonexistent or misconfigured network policy. To avoid this, {{prodname}} provides failsafe rules with default/configurable ports that are open on all host endpoints.
### Default behavior of workload to host traffic
@@ -58,7 +58,7 @@ If you are already running {{prodname}} for Kubernetes, you are good to go. If y
### Avoid accidentally cutting all host connectivity
-To avoid inadvertently cutting all host connectivity because of non-existent or misconfigured network policy, {{prodname}} uses failsafe rules that open specific ports and CIDRs on all host endpoints.
+To avoid inadvertently cutting all host connectivity because of nonexistent or misconfigured network policy, {{prodname}} uses failsafe rules that open specific ports and CIDRs on all host endpoints.
Review the following table to determine if the defaults work for your implementation. If not, change the default ports using the parameters, **FailsafeInboundHostPorts** and **FailsafeOutboundHostPorts** in [Configuring Felix](../../reference/component-resources/node/felix/configuration.mdx#environment-variables).
diff --git a/calico/network-policy/hosts/protect-hosts.mdx b/calico/network-policy/hosts/protect-hosts.mdx
index efd0ab3b6b..b4673b68fe 100644
--- a/calico/network-policy/hosts/protect-hosts.mdx
+++ b/calico/network-policy/hosts/protect-hosts.mdx
@@ -24,7 +24,7 @@ Each host has one or more network interfaces that it uses to communicate externa
### Failsafe rules
-It is easy to inadvertently cut all host connectivity because of non-existent or misconfigured network policy. To avoid this, {{prodname}} provides failsafe rules with default/configurable ports that are open on all host endpoints.
+It is easy to inadvertently cut all host connectivity because of nonexistent or misconfigured network policy. To avoid this, {{prodname}} provides failsafe rules with default/configurable ports that are open on all host endpoints.
### Default behavior of workload to host traffic
@@ -58,7 +58,7 @@ If you are already running {{prodname}} for Kubernetes, you are good to go. If y
### Avoid accidentally cutting all host connectivity
-To avoid inadvertently cutting all host connectivity because of non-existent or misconfigured network policy, {{prodname}} uses failsafe rules that open specific ports and CIDRs on all host endpoints.
+To avoid inadvertently cutting all host connectivity because of nonexistent or misconfigured network policy, {{prodname}} uses failsafe rules that open specific ports and CIDRs on all host endpoints.
Review the following table to determine if the defaults work for your implementation. If not, change the default ports using the parameters, **FailsafeInboundHostPorts** and **FailsafeOutboundHostPorts** in [Configuring Felix](../../reference/felix/configuration.mdx#environment-variables).
diff --git a/calico_versioned_docs/version-3.25/network-policy/hosts/protect-hosts.mdx b/calico_versioned_docs/version-3.25/network-policy/hosts/protect-hosts.mdx
index efd0ab3b6b..b4673b68fe 100644
--- a/calico_versioned_docs/version-3.25/network-policy/hosts/protect-hosts.mdx
+++ b/calico_versioned_docs/version-3.25/network-policy/hosts/protect-hosts.mdx
@@ -24,7 +24,7 @@ Each host has one or more network interfaces that it uses to communicate externa
### Failsafe rules
-It is easy to inadvertently cut all host connectivity because of non-existent or misconfigured network policy. To avoid this, {{prodname}} provides failsafe rules with default/configurable ports that are open on all host endpoints.
+It is easy to inadvertently cut all host connectivity because of nonexistent or misconfigured network policy. To avoid this, {{prodname}} provides failsafe rules with default/configurable ports that are open on all host endpoints.
### Default behavior of workload to host traffic
@@ -58,7 +58,7 @@ If you are already running {{prodname}} for Kubernetes, you are good to go. If y
### Avoid accidentally cutting all host connectivity
-To avoid inadvertently cutting all host connectivity because of non-existent or misconfigured network policy, {{prodname}} uses failsafe rules that open specific ports and CIDRs on all host endpoints.
+To avoid inadvertently cutting all host connectivity because of nonexistent or misconfigured network policy, {{prodname}} uses failsafe rules that open specific ports and CIDRs on all host endpoints.
Review the following table to determine if the defaults work for your implementation. If not, change the default ports using the parameters, **FailsafeInboundHostPorts** and **FailsafeOutboundHostPorts** in [Configuring Felix](../../reference/felix/configuration.mdx#environment-variables).
diff --git a/calico_versioned_docs/version-3.26/network-policy/hosts/protect-hosts.mdx b/calico_versioned_docs/version-3.26/network-policy/hosts/protect-hosts.mdx
index efd0ab3b6b..b4673b68fe 100644
--- a/calico_versioned_docs/version-3.26/network-policy/hosts/protect-hosts.mdx
+++ b/calico_versioned_docs/version-3.26/network-policy/hosts/protect-hosts.mdx
@@ -24,7 +24,7 @@ Each host has one or more network interfaces that it uses to communicate externa
### Failsafe rules
-It is easy to inadvertently cut all host connectivity because of non-existent or misconfigured network policy. To avoid this, {{prodname}} provides failsafe rules with default/configurable ports that are open on all host endpoints.
+It is easy to inadvertently cut all host connectivity because of nonexistent or misconfigured network policy. To avoid this, {{prodname}} provides failsafe rules with default/configurable ports that are open on all host endpoints.
### Default behavior of workload to host traffic
@@ -58,7 +58,7 @@ If you are already running {{prodname}} for Kubernetes, you are good to go. If y
### Avoid accidentally cutting all host connectivity
-To avoid inadvertently cutting all host connectivity because of non-existent or misconfigured network policy, {{prodname}} uses failsafe rules that open specific ports and CIDRs on all host endpoints.
+To avoid inadvertently cutting all host connectivity because of nonexistent or misconfigured network policy, {{prodname}} uses failsafe rules that open specific ports and CIDRs on all host endpoints.
Review the following table to determine if the defaults work for your implementation. If not, change the default ports using the parameters, **FailsafeInboundHostPorts** and **FailsafeOutboundHostPorts** in [Configuring Felix](../../reference/felix/configuration.mdx#environment-variables).
diff --git a/calico_versioned_docs/version-3.27/network-policy/hosts/protect-hosts.mdx b/calico_versioned_docs/version-3.27/network-policy/hosts/protect-hosts.mdx
index efd0ab3b6b..b4673b68fe 100644
--- a/calico_versioned_docs/version-3.27/network-policy/hosts/protect-hosts.mdx
+++ b/calico_versioned_docs/version-3.27/network-policy/hosts/protect-hosts.mdx
@@ -24,7 +24,7 @@ Each host has one or more network interfaces that it uses to communicate externa
### Failsafe rules
-It is easy to inadvertently cut all host connectivity because of non-existent or misconfigured network policy. To avoid this, {{prodname}} provides failsafe rules with default/configurable ports that are open on all host endpoints.
+It is easy to inadvertently cut all host connectivity because of nonexistent or misconfigured network policy. To avoid this, {{prodname}} provides failsafe rules with default/configurable ports that are open on all host endpoints.
### Default behavior of workload to host traffic
@@ -58,7 +58,7 @@ If you are already running {{prodname}} for Kubernetes, you are good to go. If y
### Avoid accidentally cutting all host connectivity
-To avoid inadvertently cutting all host connectivity because of non-existent or misconfigured network policy, {{prodname}} uses failsafe rules that open specific ports and CIDRs on all host endpoints.
+To avoid inadvertently cutting all host connectivity because of nonexistent or misconfigured network policy, {{prodname}} uses failsafe rules that open specific ports and CIDRs on all host endpoints.
Review the following table to determine if the defaults work for your implementation. If not, change the default ports using the parameters, **FailsafeInboundHostPorts** and **FailsafeOutboundHostPorts** in [Configuring Felix](../../reference/felix/configuration.mdx#environment-variables).
From a28d174ed10a085252211673c7a78c5fbf69342a Mon Sep 17 00:00:00 2001
From: Josh Soref <2119212+jsoref@users.noreply.github.com>
Date: Wed, 20 Mar 2024 23:18:19 -0400
Subject: [PATCH 36/55] spelling: openstack
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
---
.../release-notes/_v3.14.0-pre-release-notes.mdx | 2 +-
.../release-notes/_v3.14.0-pre-release-notes.mdx | 2 +-
calico/getting-started/openstack/installation/redhat.mdx | 4 ++--
calico/getting-started/openstack/installation/ubuntu.mdx | 4 ++--
calico/networking/openstack/configuration.mdx | 2 +-
calico/networking/openstack/multiple-regions.mdx | 8 ++++----
calico/reference/felix/configuration.mdx | 4 ++--
.../getting-started/openstack/installation/redhat.mdx | 4 ++--
.../getting-started/openstack/installation/ubuntu.mdx | 4 ++--
.../version-3.25/networking/openstack/configuration.mdx | 2 +-
.../networking/openstack/multiple-regions.mdx | 8 ++++----
.../version-3.25/reference/felix/configuration.mdx | 4 ++--
.../getting-started/openstack/installation/redhat.mdx | 4 ++--
.../getting-started/openstack/installation/ubuntu.mdx | 4 ++--
.../version-3.26/networking/openstack/configuration.mdx | 2 +-
.../networking/openstack/multiple-regions.mdx | 8 ++++----
.../version-3.26/reference/felix/configuration.mdx | 4 ++--
.../getting-started/openstack/installation/redhat.mdx | 4 ++--
.../getting-started/openstack/installation/ubuntu.mdx | 4 ++--
.../version-3.27/networking/openstack/configuration.mdx | 2 +-
.../networking/openstack/multiple-regions.mdx | 8 ++++----
.../version-3.27/reference/felix/configuration.mdx | 4 ++--
22 files changed, 46 insertions(+), 46 deletions(-)
diff --git a/calico-cloud/_includes/release-notes/_v3.14.0-pre-release-notes.mdx b/calico-cloud/_includes/release-notes/_v3.14.0-pre-release-notes.mdx
index d5f07cd8a1..1eec76858a 100644
--- a/calico-cloud/_includes/release-notes/_v3.14.0-pre-release-notes.mdx
+++ b/calico-cloud/_includes/release-notes/_v3.14.0-pre-release-notes.mdx
@@ -19,7 +19,7 @@
- In BPF dataplane mode, Felix now handles single-block IPAM pools. Previously single-block pools resulted in a collision when programming the dataplane routes. [felix #2245](https://github.com/projectcalico/felix/pull/2245) (@fasaxc)
- None required [felix #2233](https://github.com/projectcalico/felix/pull/2233) (@tomastigera)
- None required [felix #2232](https://github.com/projectcalico/felix/pull/2232) (@tomastigera)
-- [Openstack] Allow DHCP from the workload, on kernels where rp_filter doesn't already [felix #2231](https://github.com/projectcalico/felix/pull/2231) (@nelljerram)
+- [OpenStack] Allow DHCP from the workload, on kernels where rp_filter doesn't already [felix #2231](https://github.com/projectcalico/felix/pull/2231) (@nelljerram)
- all-interfaces host endpoints now supports normal network policy in addition to pre-dnat policy [felix #2228](https://github.com/projectcalico/felix/pull/2228) (@lmm)
- Add FelixConfiguration option for setting route information source [libcalico-go #1222](https://github.com/projectcalico/libcalico-go/pull/1222) (@caseydavenport)
- Added Wireguard configuration. [libcalico-go #1215](https://github.com/projectcalico/libcalico-go/pull/1215) (@realgaurav)
diff --git a/calico-cloud_versioned_docs/version-19-1/_includes/release-notes/_v3.14.0-pre-release-notes.mdx b/calico-cloud_versioned_docs/version-19-1/_includes/release-notes/_v3.14.0-pre-release-notes.mdx
index d5f07cd8a1..1eec76858a 100644
--- a/calico-cloud_versioned_docs/version-19-1/_includes/release-notes/_v3.14.0-pre-release-notes.mdx
+++ b/calico-cloud_versioned_docs/version-19-1/_includes/release-notes/_v3.14.0-pre-release-notes.mdx
@@ -19,7 +19,7 @@
- In BPF dataplane mode, Felix now handles single-block IPAM pools. Previously single-block pools resulted in a collision when programming the dataplane routes. [felix #2245](https://github.com/projectcalico/felix/pull/2245) (@fasaxc)
- None required [felix #2233](https://github.com/projectcalico/felix/pull/2233) (@tomastigera)
- None required [felix #2232](https://github.com/projectcalico/felix/pull/2232) (@tomastigera)
-- [Openstack] Allow DHCP from the workload, on kernels where rp_filter doesn't already [felix #2231](https://github.com/projectcalico/felix/pull/2231) (@nelljerram)
+- [OpenStack] Allow DHCP from the workload, on kernels where rp_filter doesn't already [felix #2231](https://github.com/projectcalico/felix/pull/2231) (@nelljerram)
- all-interfaces host endpoints now supports normal network policy in addition to pre-dnat policy [felix #2228](https://github.com/projectcalico/felix/pull/2228) (@lmm)
- Add FelixConfiguration option for setting route information source [libcalico-go #1222](https://github.com/projectcalico/libcalico-go/pull/1222) (@caseydavenport)
- Added Wireguard configuration. [libcalico-go #1215](https://github.com/projectcalico/libcalico-go/pull/1215) (@realgaurav)
diff --git a/calico/getting-started/openstack/installation/redhat.mdx b/calico/getting-started/openstack/installation/redhat.mdx
index b73a7e1171..5c0b8add7c 100644
--- a/calico/getting-started/openstack/installation/redhat.mdx
+++ b/calico/getting-started/openstack/installation/redhat.mdx
@@ -4,7 +4,7 @@ description: Install Calico on OpenStack, Red Hat Enterprise Linux nodes.
# Red Hat Enterprise Linux
-import OpenstackEtcdAuth from '@site/calico/_includes/content/_openstack-etcd-auth.mdx';
+import OpenStackEtcdAuth from '@site/calico/_includes/content/_openstack-etcd-auth.mdx';
These instructions will take you through a first-time install of
{{prodname}}. If you are upgrading an existing system, please see
@@ -283,4 +283,4 @@ On each compute node, perform the following steps:
service calico-felix restart
```
-(typha_cache_size\{syncer="bgp"\})
(typha_cache_size\{syncer="dpi"\})
typha_cache_size\{syncer="felix"\})
(typha_cache_size\{syncer="node-status"\})
(typha_cache_size\{syncer="tunnel-ip-allocation"\})
sum by (instance)
(typha_cache_size)
max by (instance)
(typha_cache_size)
|
| Example value | Example of: max by (instance)
(typha_cache_size\{syncer="felix"\})
\{instance="10.0.1.20:9093"\} 661
\{instance="10.0.1.31:9093"\} 661
|
| Explanation | The total number of key/value pairs in Typha's in-memory cache.This metric represents the scale of the {{prodname}} datastore as it tracks how many WEPs (pods and services), HEPs (hostendpoints), networksets, globalnetworksets, {{prodname}} Network Policies etc that Typha is aware of across the entire Calico Federation.You can use this metric to monitor individual syncers to Typha (like Felix, BGP etc), or to get a sum of all syncers. We recommend that you monitor the largest syncer but it is completely up to you. This is a good metric to understand how much data is in Typha. Note: If all Typhas are in sync then they should have the same value for this metric. |
-| Threshold value recommendation | The value of this metric will depend on the scale of the Calico Federation and will always increase as WEPs, {{prodname}} network policie,s and clusters are added. Achieve a baseline first, then monitor for any unexpected increases from the baseline. |
+| Threshold value recommendation | The value of this metric will depend on the scale of the Calico Federation and will always increase as WEPs, {{prodname}} network policies and clusters are added. Achieve a baseline first, then monitor for any unexpected increases from the baseline. |
| Threshold breach symptoms | Unexpected increases may indicate memory leaks and performance issues with Typha. |
| Threshold breach recommendations | Check CPU usage on Typha pods and Kubernetes nodes. Increase resources if needed, rollout and restart Typha(s) if needed. |
| Priority level | Optional. |
diff --git a/calico-cloud_versioned_docs/version-19-1/operations/monitor/metrics/recommended-metrics.mdx b/calico-cloud_versioned_docs/version-19-1/operations/monitor/metrics/recommended-metrics.mdx
index 2387a1b2e4..5082002051 100644
--- a/calico-cloud_versioned_docs/version-19-1/operations/monitor/metrics/recommended-metrics.mdx
+++ b/calico-cloud_versioned_docs/version-19-1/operations/monitor/metrics/recommended-metrics.mdx
@@ -61,7 +61,7 @@ This section provides metrics recommendations for maintaining optimal cluster op
| Metric | Note: Syncer (type) is Typha's internal name for a client (type).(typha_cache_size\{syncer="bgp"\})
(typha_cache_size\{syncer="dpi"\})
typha_cache_size\{syncer="felix"\})
(typha_cache_size\{syncer="node-status"\})
(typha_cache_size\{syncer="tunnel-ip-allocation"\})
sum by (instance)
(typha_cache_size)
max by (instance)
(typha_cache_size)
|
| Example value | Example of: max by (instance)
(typha_cache_size\{syncer="felix"\})
\{instance="10.0.1.20:9093"\} 661
\{instance="10.0.1.31:9093"\} 661
|
| Explanation | The total number of key/value pairs in Typha's in-memory cache.This metric represents the scale of the {{prodname}} datastore as it tracks how many WEPs (pods and services), HEPs (hostendpoints), networksets, globalnetworksets, {{prodname}} Network Policies etc that Typha is aware of across the entire Calico Federation.You can use this metric to monitor individual syncers to Typha (like Felix, BGP etc), or to get a sum of all syncers. We recommend that you monitor the largest syncer but it is completely up to you. This is a good metric to understand how much data is in Typha. Note: If all Typhas are in sync then they should have the same value for this metric. |
-| Threshold value recommendation | The value of this metric will depend on the scale of the Calico Federation and will always increase as WEPs, {{prodname}} network policie,s and clusters are added. Achieve a baseline first, then monitor for any unexpected increases from the baseline. |
+| Threshold value recommendation | The value of this metric will depend on the scale of the Calico Federation and will always increase as WEPs, {{prodname}} network policies and clusters are added. Achieve a baseline first, then monitor for any unexpected increases from the baseline. |
| Threshold breach symptoms | Unexpected increases may indicate memory leaks and performance issues with Typha. |
| Threshold breach recommendations | Check CPU usage on Typha pods and Kubernetes nodes. Increase resources if needed, rollout and restart Typha(s) if needed. |
| Priority level | Optional. |
diff --git a/calico-enterprise/operations/monitor/metrics/recommended-metrics.mdx b/calico-enterprise/operations/monitor/metrics/recommended-metrics.mdx
index 3d6686721d..b9aaa02726 100644
--- a/calico-enterprise/operations/monitor/metrics/recommended-metrics.mdx
+++ b/calico-enterprise/operations/monitor/metrics/recommended-metrics.mdx
@@ -61,7 +61,7 @@ This section provides metrics recommendations for maintaining optimal cluster op
| Metric | Note: Syncer (type) is Typha's internal name for a client (type).(typha_cache_size\{syncer="bgp"\})
(typha_cache_size\{syncer="dpi"\})
typha_cache_size\{syncer="felix"\})
(typha_cache_size\{syncer="node-status"\})
(typha_cache_size\{syncer="tunnel-ip-allocation"\})
sum by (instance)
(typha_cache_size)
max by (instance)
(typha_cache_size)
|
| Example value | Example of: max by (instance)
(typha_cache_size\{syncer="felix"\})
\{instance="10.0.1.20:9093"\} 661
\{instance="10.0.1.31:9093"\} 661
|
| Explanation | The total number of key/value pairs in Typha's in-memory cache.This metric represents the scale of the {{prodname}} datastore as it tracks how many WEPs (pods and services), HEPs (hostendpoints), networksets, globalnetworksets, {{prodname}} Network Policies etc that Typha is aware of across the entire Calico Federation.You can use this metric to monitor individual syncers to Typha (like Felix, BGP etc), or to get a sum of all syncers. We recommend that you monitor the largest syncer but it is completely up to you. This is a good metric to understand how much data is in Typha. Note: If all Typhas are in sync then they should have the same value for this metric. |
-| Threshold value recommendation | The value of this metric will depend on the scale of the Calico Federation and will always increase as WEPs, {{prodname}} network policie,s and clusters are added. Achieve a baseline first, then monitor for any unexpected increases from the baseline. |
+| Threshold value recommendation | The value of this metric will depend on the scale of the Calico Federation and will always increase as WEPs, {{prodname}} network policies and clusters are added. Achieve a baseline first, then monitor for any unexpected increases from the baseline. |
| Threshold breach symptoms | Unexpected increases may indicate memory leaks and performance issues with Typha. |
| Threshold breach recommendations | Check CPU usage on Typha pods and Kubernetes nodes. Increase resources if needed, rollout and restart Typha(s) if needed. |
| Priority level | Optional. |
diff --git a/calico-enterprise_versioned_docs/version-3.18-2/operations/monitor/metrics/recommended-metrics.mdx b/calico-enterprise_versioned_docs/version-3.18-2/operations/monitor/metrics/recommended-metrics.mdx
index 3d6686721d..b9aaa02726 100644
--- a/calico-enterprise_versioned_docs/version-3.18-2/operations/monitor/metrics/recommended-metrics.mdx
+++ b/calico-enterprise_versioned_docs/version-3.18-2/operations/monitor/metrics/recommended-metrics.mdx
@@ -61,7 +61,7 @@ This section provides metrics recommendations for maintaining optimal cluster op
| Metric | Note: Syncer (type) is Typha's internal name for a client (type).(typha_cache_size\{syncer="bgp"\})
(typha_cache_size\{syncer="dpi"\})
typha_cache_size\{syncer="felix"\})
(typha_cache_size\{syncer="node-status"\})
(typha_cache_size\{syncer="tunnel-ip-allocation"\})
sum by (instance)
(typha_cache_size)
max by (instance)
(typha_cache_size)
|
| Example value | Example of: max by (instance)
(typha_cache_size\{syncer="felix"\})
\{instance="10.0.1.20:9093"\} 661
\{instance="10.0.1.31:9093"\} 661
|
| Explanation | The total number of key/value pairs in Typha's in-memory cache.This metric represents the scale of the {{prodname}} datastore as it tracks how many WEPs (pods and services), HEPs (hostendpoints), networksets, globalnetworksets, {{prodname}} Network Policies etc that Typha is aware of across the entire Calico Federation.You can use this metric to monitor individual syncers to Typha (like Felix, BGP etc), or to get a sum of all syncers. We recommend that you monitor the largest syncer but it is completely up to you. This is a good metric to understand how much data is in Typha. Note: If all Typhas are in sync then they should have the same value for this metric. |
-| Threshold value recommendation | The value of this metric will depend on the scale of the Calico Federation and will always increase as WEPs, {{prodname}} network policie,s and clusters are added. Achieve a baseline first, then monitor for any unexpected increases from the baseline. |
+| Threshold value recommendation | The value of this metric will depend on the scale of the Calico Federation and will always increase as WEPs, {{prodname}} network policies and clusters are added. Achieve a baseline first, then monitor for any unexpected increases from the baseline. |
| Threshold breach symptoms | Unexpected increases may indicate memory leaks and performance issues with Typha. |
| Threshold breach recommendations | Check CPU usage on Typha pods and Kubernetes nodes. Increase resources if needed, rollout and restart Typha(s) if needed. |
| Priority level | Optional. |
diff --git a/calico-enterprise_versioned_docs/version-3.19-1/operations/monitor/metrics/recommended-metrics.mdx b/calico-enterprise_versioned_docs/version-3.19-1/operations/monitor/metrics/recommended-metrics.mdx
index 3d6686721d..b9aaa02726 100644
--- a/calico-enterprise_versioned_docs/version-3.19-1/operations/monitor/metrics/recommended-metrics.mdx
+++ b/calico-enterprise_versioned_docs/version-3.19-1/operations/monitor/metrics/recommended-metrics.mdx
@@ -61,7 +61,7 @@ This section provides metrics recommendations for maintaining optimal cluster op
| Metric | Note: Syncer (type) is Typha's internal name for a client (type).(typha_cache_size\{syncer="bgp"\})
(typha_cache_size\{syncer="dpi"\})
typha_cache_size\{syncer="felix"\})
(typha_cache_size\{syncer="node-status"\})
(typha_cache_size\{syncer="tunnel-ip-allocation"\})
sum by (instance)
(typha_cache_size)
max by (instance)
(typha_cache_size)
|
| Example value | Example of: max by (instance)
(typha_cache_size\{syncer="felix"\})
\{instance="10.0.1.20:9093"\} 661
\{instance="10.0.1.31:9093"\} 661
|
| Explanation | The total number of key/value pairs in Typha's in-memory cache.This metric represents the scale of the {{prodname}} datastore as it tracks how many WEPs (pods and services), HEPs (hostendpoints), networksets, globalnetworksets, {{prodname}} Network Policies etc that Typha is aware of across the entire Calico Federation.You can use this metric to monitor individual syncers to Typha (like Felix, BGP etc), or to get a sum of all syncers. We recommend that you monitor the largest syncer but it is completely up to you. This is a good metric to understand how much data is in Typha. Note: If all Typhas are in sync then they should have the same value for this metric. |
-| Threshold value recommendation | The value of this metric will depend on the scale of the Calico Federation and will always increase as WEPs, {{prodname}} network policie,s and clusters are added. Achieve a baseline first, then monitor for any unexpected increases from the baseline. |
+| Threshold value recommendation | The value of this metric will depend on the scale of the Calico Federation and will always increase as WEPs, {{prodname}} network policies and clusters are added. Achieve a baseline first, then monitor for any unexpected increases from the baseline. |
| Threshold breach symptoms | Unexpected increases may indicate memory leaks and performance issues with Typha. |
| Threshold breach recommendations | Check CPU usage on Typha pods and Kubernetes nodes. Increase resources if needed, rollout and restart Typha(s) if needed. |
| Priority level | Optional. |
From 220bb6bf37e4ea85ac7a09fcd133a2e77c5be91d Mon Sep 17 00:00:00 2001
From: Josh Soref <2119212+jsoref@users.noreply.github.com>
Date: Wed, 20 Mar 2024 23:58:29 -0400
Subject: [PATCH 40/55] spelling: preexisting
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
---
calico-cloud/operations/ebpf/enabling-ebpf.mdx | 2 +-
.../version-19-1/operations/ebpf/enabling-ebpf.mdx | 2 +-
calico-enterprise/operations/ebpf/enabling-ebpf.mdx | 2 +-
calico-enterprise/reference/clis/calicoctl/node/run.mdx | 4 ++--
calico-enterprise/reference/clis/calicoctl/overview.mdx | 2 +-
.../version-3.16/operations/ebpf/enabling-ebpf.mdx | 2 +-
.../version-3.16/reference/clis/calicoctl/node/run.mdx | 4 ++--
.../version-3.16/reference/clis/calicoctl/overview.mdx | 2 +-
.../version-3.17/operations/ebpf/enabling-ebpf.mdx | 2 +-
.../version-3.17/reference/clis/calicoctl/node/run.mdx | 4 ++--
.../version-3.17/reference/clis/calicoctl/overview.mdx | 2 +-
.../version-3.18-2/operations/ebpf/enabling-ebpf.mdx | 2 +-
.../version-3.18-2/reference/clis/calicoctl/node/run.mdx | 4 ++--
.../version-3.18-2/reference/clis/calicoctl/overview.mdx | 2 +-
.../version-3.18/operations/ebpf/enabling-ebpf.mdx | 2 +-
.../version-3.18/reference/clis/calicoctl/node/run.mdx | 4 ++--
.../version-3.18/reference/clis/calicoctl/overview.mdx | 2 +-
.../version-3.19-1/operations/ebpf/enabling-ebpf.mdx | 2 +-
.../version-3.19-1/reference/clis/calicoctl/node/run.mdx | 4 ++--
.../version-3.19-1/reference/clis/calicoctl/overview.mdx | 2 +-
calico/operations/ebpf/enabling-ebpf.mdx | 2 +-
calico/reference/calicoctl/node/run.mdx | 4 ++--
calico/reference/calicoctl/overview.mdx | 2 +-
.../version-3.25/operations/ebpf/enabling-ebpf.mdx | 2 +-
.../version-3.25/reference/calicoctl/node/run.mdx | 4 ++--
.../version-3.25/reference/calicoctl/overview.mdx | 2 +-
.../version-3.26/operations/ebpf/enabling-ebpf.mdx | 2 +-
.../version-3.26/reference/calicoctl/node/run.mdx | 4 ++--
.../version-3.26/reference/calicoctl/overview.mdx | 2 +-
.../version-3.27/operations/ebpf/enabling-ebpf.mdx | 2 +-
.../version-3.27/reference/calicoctl/node/run.mdx | 4 ++--
.../version-3.27/reference/calicoctl/overview.mdx | 2 +-
32 files changed, 42 insertions(+), 42 deletions(-)
diff --git a/calico-cloud/operations/ebpf/enabling-ebpf.mdx b/calico-cloud/operations/ebpf/enabling-ebpf.mdx
index a5af8d5a1e..a6ec15e3eb 100644
--- a/calico-cloud/operations/ebpf/enabling-ebpf.mdx
+++ b/calico-cloud/operations/ebpf/enabling-ebpf.mdx
@@ -230,7 +230,7 @@ resource to `"BPF"`.
kubectl patch installation.operator.tigera.io default --type merge -p '{"spec":{"calicoNetwork":{"linuxDataplane":"BPF"}}}'
```
-When enabling eBPF mode, pre-existing connections continue to use the non-BPF datapath; such connections should
+When enabling eBPF mode, preexisting connections continue to use the non-BPF datapath; such connections should
not be disrupted, but they do not benefit from eBPF mode’s advantages.
:::note
diff --git a/calico-cloud_versioned_docs/version-19-1/operations/ebpf/enabling-ebpf.mdx b/calico-cloud_versioned_docs/version-19-1/operations/ebpf/enabling-ebpf.mdx
index 97e4146991..1c5d91057e 100644
--- a/calico-cloud_versioned_docs/version-19-1/operations/ebpf/enabling-ebpf.mdx
+++ b/calico-cloud_versioned_docs/version-19-1/operations/ebpf/enabling-ebpf.mdx
@@ -230,7 +230,7 @@ resource to `"BPF"`.
kubectl patch installation.operator.tigera.io default --type merge -p '{"spec":{"calicoNetwork":{"linuxDataplane":"BPF"}}}'
```
-When enabling eBPF mode, pre-existing connections continue to use the non-BPF datapath; such connections should
+When enabling eBPF mode, preexisting connections continue to use the non-BPF datapath; such connections should
not be disrupted, but they do not benefit from eBPF mode’s advantages.
:::note
diff --git a/calico-enterprise/operations/ebpf/enabling-ebpf.mdx b/calico-enterprise/operations/ebpf/enabling-ebpf.mdx
index ea80f24764..e13105469b 100644
--- a/calico-enterprise/operations/ebpf/enabling-ebpf.mdx
+++ b/calico-enterprise/operations/ebpf/enabling-ebpf.mdx
@@ -186,7 +186,7 @@ resource to `"BPF"`.
kubectl patch installation.operator.tigera.io default --type merge -p '{"spec":{"calicoNetwork":{"linuxDataplane":"BPF"}}}'
```
-When enabling eBPF mode, pre-existing connections continue to use the non-BPF datapath; such connections should
+When enabling eBPF mode, preexisting connections continue to use the non-BPF datapath; such connections should
not be disrupted, but they do not benefit from eBPF mode’s advantages.
:::note
diff --git a/calico-enterprise/reference/clis/calicoctl/node/run.mdx b/calico-enterprise/reference/clis/calicoctl/node/run.mdx
index 0368cc597c..6f1bff857c 100644
--- a/calico-enterprise/reference/clis/calicoctl/node/run.mdx
+++ b/calico-enterprise/reference/clis/calicoctl/node/run.mdx
@@ -100,7 +100,7 @@ Options:
system.
--no-default-ippools Do not create default pools upon startup.
Default IP pools will be created if this is not set
- and there are no pre-existing Calico IP pools.
+ and there are no preexisting Calico IP pools.
--disable-docker-networking
Disable Docker networking.
--docker-networking-ifprefix=-BlockSize specifies the CIDR prefex length to use when allocating per-node IP blocks from +BlockSize specifies the CIDR prefix length to use when allocating per-node IP blocks from the main IP pool CIDR. Default: 26 (IPv4), 122 (IPv6)
diff --git a/calico-cloud_versioned_docs/version-19-1/reference/installation/_api.mdx b/calico-cloud_versioned_docs/version-19-1/reference/installation/_api.mdx index 588b7b9267..8991e936be 100644 --- a/calico-cloud_versioned_docs/version-19-1/reference/installation/_api.mdx +++ b/calico-cloud_versioned_docs/version-19-1/reference/installation/_api.mdx @@ -9157,7 +9157,7 @@ int32 (Optional)-BlockSize specifies the CIDR prefex length to use when allocating per-node IP blocks from +BlockSize specifies the CIDR prefix length to use when allocating per-node IP blocks from the main IP pool CIDR. Default: 26 (IPv4), 122 (IPv6)
diff --git a/calico-enterprise/reference/installation/_api.mdx b/calico-enterprise/reference/installation/_api.mdx index 588b7b9267..8991e936be 100644 --- a/calico-enterprise/reference/installation/_api.mdx +++ b/calico-enterprise/reference/installation/_api.mdx @@ -9157,7 +9157,7 @@ int32 (Optional)-BlockSize specifies the CIDR prefex length to use when allocating per-node IP blocks from +BlockSize specifies the CIDR prefix length to use when allocating per-node IP blocks from the main IP pool CIDR. Default: 26 (IPv4), 122 (IPv6)
diff --git a/calico-enterprise_versioned_docs/version-3.16/reference/installation/_api.mdx b/calico-enterprise_versioned_docs/version-3.16/reference/installation/_api.mdx index f32caa2678..94138f7c08 100644 --- a/calico-enterprise_versioned_docs/version-3.16/reference/installation/_api.mdx +++ b/calico-enterprise_versioned_docs/version-3.16/reference/installation/_api.mdx @@ -7746,7 +7746,7 @@ int32 (Optional)-BlockSize specifies the CIDR prefex length to use when allocating per-node IP blocks from +BlockSize specifies the CIDR prefix length to use when allocating per-node IP blocks from the main IP pool CIDR. Default: 26 (IPv4), 122 (IPv6)
diff --git a/calico-enterprise_versioned_docs/version-3.17/reference/installation/_api.mdx b/calico-enterprise_versioned_docs/version-3.17/reference/installation/_api.mdx index 97a2c18168..fd8e00bb46 100644 --- a/calico-enterprise_versioned_docs/version-3.17/reference/installation/_api.mdx +++ b/calico-enterprise_versioned_docs/version-3.17/reference/installation/_api.mdx @@ -9103,7 +9103,7 @@ int32 (Optional)-BlockSize specifies the CIDR prefex length to use when allocating per-node IP blocks from +BlockSize specifies the CIDR prefix length to use when allocating per-node IP blocks from the main IP pool CIDR. Default: 26 (IPv4), 122 (IPv6)
diff --git a/calico-enterprise_versioned_docs/version-3.18-2/reference/installation/_api.mdx b/calico-enterprise_versioned_docs/version-3.18-2/reference/installation/_api.mdx index d40eec901d..c58cf0c104 100644 --- a/calico-enterprise_versioned_docs/version-3.18-2/reference/installation/_api.mdx +++ b/calico-enterprise_versioned_docs/version-3.18-2/reference/installation/_api.mdx @@ -9101,7 +9101,7 @@ int32 (Optional)-BlockSize specifies the CIDR prefex length to use when allocating per-node IP blocks from +BlockSize specifies the CIDR prefix length to use when allocating per-node IP blocks from the main IP pool CIDR. Default: 26 (IPv4), 122 (IPv6)
diff --git a/calico-enterprise_versioned_docs/version-3.18/reference/installation/_api.mdx b/calico-enterprise_versioned_docs/version-3.18/reference/installation/_api.mdx index 345efaca6e..0fa4088c3a 100644 --- a/calico-enterprise_versioned_docs/version-3.18/reference/installation/_api.mdx +++ b/calico-enterprise_versioned_docs/version-3.18/reference/installation/_api.mdx @@ -8426,7 +8426,7 @@ int32 (Optional)-BlockSize specifies the CIDR prefex length to use when allocating per-node IP blocks from +BlockSize specifies the CIDR prefix length to use when allocating per-node IP blocks from the main IP pool CIDR. Default: 26 (IPv4), 122 (IPv6)
diff --git a/calico-enterprise_versioned_docs/version-3.19-1/reference/installation/_api.mdx b/calico-enterprise_versioned_docs/version-3.19-1/reference/installation/_api.mdx index 1eaf58a183..8bd1ae3e8f 100644 --- a/calico-enterprise_versioned_docs/version-3.19-1/reference/installation/_api.mdx +++ b/calico-enterprise_versioned_docs/version-3.19-1/reference/installation/_api.mdx @@ -9421,7 +9421,7 @@ int32 (Optional)-BlockSize specifies the CIDR prefex length to use when allocating per-node IP blocks from +BlockSize specifies the CIDR prefix length to use when allocating per-node IP blocks from the main IP pool CIDR. Default: 26 (IPv4), 122 (IPv6)
diff --git a/calico/reference/installation/_api.mdx b/calico/reference/installation/_api.mdx index ba97dbe44c..69418ce786 100644 --- a/calico/reference/installation/_api.mdx +++ b/calico/reference/installation/_api.mdx @@ -6398,7 +6398,7 @@ int32 (Optional)-BlockSize specifies the CIDR prefex length to use when allocating per-node IP blocks from +BlockSize specifies the CIDR prefix length to use when allocating per-node IP blocks from the main IP pool CIDR. Default: 26 (IPv4), 122 (IPv6)
diff --git a/calico_versioned_docs/version-3.25/reference/installation/_api.mdx b/calico_versioned_docs/version-3.25/reference/installation/_api.mdx index e4e01c1b6f..ce155aa27e 100644 --- a/calico_versioned_docs/version-3.25/reference/installation/_api.mdx +++ b/calico_versioned_docs/version-3.25/reference/installation/_api.mdx @@ -5060,7 +5060,7 @@ int32 (Optional)-BlockSize specifies the CIDR prefex length to use when allocating per-node IP blocks from +BlockSize specifies the CIDR prefix length to use when allocating per-node IP blocks from the main IP pool CIDR. Default: 26 (IPv4), 122 (IPv6)
diff --git a/calico_versioned_docs/version-3.26/reference/installation/_api.mdx b/calico_versioned_docs/version-3.26/reference/installation/_api.mdx index 166f647706..5850f58e39 100644 --- a/calico_versioned_docs/version-3.26/reference/installation/_api.mdx +++ b/calico_versioned_docs/version-3.26/reference/installation/_api.mdx @@ -5740,7 +5740,7 @@ int32 (Optional)-BlockSize specifies the CIDR prefex length to use when allocating per-node IP blocks from +BlockSize specifies the CIDR prefix length to use when allocating per-node IP blocks from the main IP pool CIDR. Default: 26 (IPv4), 122 (IPv6)
diff --git a/calico_versioned_docs/version-3.27/reference/installation/_api.mdx b/calico_versioned_docs/version-3.27/reference/installation/_api.mdx index ba97dbe44c..69418ce786 100644 --- a/calico_versioned_docs/version-3.27/reference/installation/_api.mdx +++ b/calico_versioned_docs/version-3.27/reference/installation/_api.mdx @@ -6398,7 +6398,7 @@ int32 (Optional)-BlockSize specifies the CIDR prefex length to use when allocating per-node IP blocks from +BlockSize specifies the CIDR prefix length to use when allocating per-node IP blocks from the main IP pool CIDR. Default: 26 (IPv4), 122 (IPv6)
From 5a3b3a7e64da92aec6bcfebcaa864c58e3079dd5 Mon Sep 17 00:00:00 2001 From: Josh Soref <2119212+jsoref@users.noreply.github.com> Date: Wed, 20 Mar 2024 23:38:00 -0400 Subject: [PATCH 42/55] spelling: rapidly Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> --- calico-cloud/operations/monitor/metrics/recommended-metrics.mdx | 2 +- .../operations/monitor/metrics/recommended-metrics.mdx | 2 +- .../operations/monitor/metrics/recommended-metrics.mdx | 2 +- .../operations/monitor/metrics/recommended-metrics.mdx | 2 +- .../operations/monitor/metrics/recommended-metrics.mdx | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/calico-cloud/operations/monitor/metrics/recommended-metrics.mdx b/calico-cloud/operations/monitor/metrics/recommended-metrics.mdx index 5082002051..d53fa3ba90 100644 --- a/calico-cloud/operations/monitor/metrics/recommended-metrics.mdx +++ b/calico-cloud/operations/monitor/metrics/recommended-metrics.mdx @@ -459,7 +459,7 @@ The following policy metrics are a separate endpoint exposed by Felix that are u | Metric |felix_logs_dropped
|
| Example value | felix_logs_dropped\{endpoint="metrics-port", instance="10.0.1.20:9091", job="felix-metrics-svc", namespace="calico-system", pod="calico-node-qzpkt", service="felix-metrics-svc"\} 0
|
| Explanation | The number of logs Felix has dropped. Note that this metric does not count flow-logs; it counts logs to stdout. |
-| Threshold value recommendation | Occasional drops are normal. Investigate if drop counters rapidily rise. |
+| Threshold value recommendation | Occasional drops are normal. Investigate if drop counters rapidly rise. |
| Threshold breach symptoms | Felix will drop logs if it cannot keep up with writing them out. These are ordinary code logs, not flow logs. Calico-node may be under resource constraints. |
| Threshold breach recommendations | Check CPU usage on calico-nodes and Kubernetes nodes. Increase resources if needed, and rollout restart calico-node(s) if needed. |
| Priority level | Optional. |
diff --git a/calico-cloud_versioned_docs/version-19-1/operations/monitor/metrics/recommended-metrics.mdx b/calico-cloud_versioned_docs/version-19-1/operations/monitor/metrics/recommended-metrics.mdx
index 5082002051..d53fa3ba90 100644
--- a/calico-cloud_versioned_docs/version-19-1/operations/monitor/metrics/recommended-metrics.mdx
+++ b/calico-cloud_versioned_docs/version-19-1/operations/monitor/metrics/recommended-metrics.mdx
@@ -459,7 +459,7 @@ The following policy metrics are a separate endpoint exposed by Felix that are u
| Metric | felix_logs_dropped
|
| Example value | felix_logs_dropped\{endpoint="metrics-port", instance="10.0.1.20:9091", job="felix-metrics-svc", namespace="calico-system", pod="calico-node-qzpkt", service="felix-metrics-svc"\} 0
|
| Explanation | The number of logs Felix has dropped. Note that this metric does not count flow-logs; it counts logs to stdout. |
-| Threshold value recommendation | Occasional drops are normal. Investigate if drop counters rapidily rise. |
+| Threshold value recommendation | Occasional drops are normal. Investigate if drop counters rapidly rise. |
| Threshold breach symptoms | Felix will drop logs if it cannot keep up with writing them out. These are ordinary code logs, not flow logs. Calico-node may be under resource constraints. |
| Threshold breach recommendations | Check CPU usage on calico-nodes and Kubernetes nodes. Increase resources if needed, and rollout restart calico-node(s) if needed. |
| Priority level | Optional. |
diff --git a/calico-enterprise/operations/monitor/metrics/recommended-metrics.mdx b/calico-enterprise/operations/monitor/metrics/recommended-metrics.mdx
index b9aaa02726..ebf664b106 100644
--- a/calico-enterprise/operations/monitor/metrics/recommended-metrics.mdx
+++ b/calico-enterprise/operations/monitor/metrics/recommended-metrics.mdx
@@ -459,7 +459,7 @@ The following policy metrics are a separate endpoint exposed by Felix that are u
| Metric | felix_logs_dropped
|
| Example value | felix_logs_dropped\{endpoint="metrics-port", instance="10.0.1.20:9091", job="felix-metrics-svc", namespace="calico-system", pod="calico-node-qzpkt", service="felix-metrics-svc"\} 0
|
| Explanation | The number of logs Felix has dropped. Note that this metric does not count flow-logs; it counts logs to stdout. |
-| Threshold value recommendation | Occasional drops are normal. Investigate if drop counters rapidily rise. |
+| Threshold value recommendation | Occasional drops are normal. Investigate if drop counters rapidly rise. |
| Threshold breach symptoms | Felix will drop logs if it cannot keep up with writing them out. These are ordinary code logs, not flow logs. Calico-node may be under resource constraints. |
| Threshold breach recommendations | Check CPU usage on calico-nodes and Kubernetes nodes. Increase resources if needed, and rollout restart calico-node(s) if needed. |
| Priority level | Optional. |
diff --git a/calico-enterprise_versioned_docs/version-3.18-2/operations/monitor/metrics/recommended-metrics.mdx b/calico-enterprise_versioned_docs/version-3.18-2/operations/monitor/metrics/recommended-metrics.mdx
index b9aaa02726..ebf664b106 100644
--- a/calico-enterprise_versioned_docs/version-3.18-2/operations/monitor/metrics/recommended-metrics.mdx
+++ b/calico-enterprise_versioned_docs/version-3.18-2/operations/monitor/metrics/recommended-metrics.mdx
@@ -459,7 +459,7 @@ The following policy metrics are a separate endpoint exposed by Felix that are u
| Metric | felix_logs_dropped
|
| Example value | felix_logs_dropped\{endpoint="metrics-port", instance="10.0.1.20:9091", job="felix-metrics-svc", namespace="calico-system", pod="calico-node-qzpkt", service="felix-metrics-svc"\} 0
|
| Explanation | The number of logs Felix has dropped. Note that this metric does not count flow-logs; it counts logs to stdout. |
-| Threshold value recommendation | Occasional drops are normal. Investigate if drop counters rapidily rise. |
+| Threshold value recommendation | Occasional drops are normal. Investigate if drop counters rapidly rise. |
| Threshold breach symptoms | Felix will drop logs if it cannot keep up with writing them out. These are ordinary code logs, not flow logs. Calico-node may be under resource constraints. |
| Threshold breach recommendations | Check CPU usage on calico-nodes and Kubernetes nodes. Increase resources if needed, and rollout restart calico-node(s) if needed. |
| Priority level | Optional. |
diff --git a/calico-enterprise_versioned_docs/version-3.19-1/operations/monitor/metrics/recommended-metrics.mdx b/calico-enterprise_versioned_docs/version-3.19-1/operations/monitor/metrics/recommended-metrics.mdx
index b9aaa02726..ebf664b106 100644
--- a/calico-enterprise_versioned_docs/version-3.19-1/operations/monitor/metrics/recommended-metrics.mdx
+++ b/calico-enterprise_versioned_docs/version-3.19-1/operations/monitor/metrics/recommended-metrics.mdx
@@ -459,7 +459,7 @@ The following policy metrics are a separate endpoint exposed by Felix that are u
| Metric | felix_logs_dropped
|
| Example value | felix_logs_dropped\{endpoint="metrics-port", instance="10.0.1.20:9091", job="felix-metrics-svc", namespace="calico-system", pod="calico-node-qzpkt", service="felix-metrics-svc"\} 0
|
| Explanation | The number of logs Felix has dropped. Note that this metric does not count flow-logs; it counts logs to stdout. |
-| Threshold value recommendation | Occasional drops are normal. Investigate if drop counters rapidily rise. |
+| Threshold value recommendation | Occasional drops are normal. Investigate if drop counters rapidly rise. |
| Threshold breach symptoms | Felix will drop logs if it cannot keep up with writing them out. These are ordinary code logs, not flow logs. Calico-node may be under resource constraints. |
| Threshold breach recommendations | Check CPU usage on calico-nodes and Kubernetes nodes. Increase resources if needed, and rollout restart calico-node(s) if needed. |
| Priority level | Optional. |
From fb0671fa8d48a019572fb64ecb15ae67e4931687 Mon Sep 17 00:00:00 2001
From: Josh Soref <2119212+jsoref@users.noreply.github.com>
Date: Wed, 15 Nov 2023 23:03:01 -0500
Subject: [PATCH 43/55] spelling: retransmitted
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
---
.../visibility/elastic/flow/datatypes.mdx | 2 +-
.../visibility/elastic/flow/datatypes.mdx | 2 +-
.../visibility/elastic/flow/datatypes.mdx | 2 +-
.../visibility/elastic/flow/datatypes.mdx | 2 +-
.../visibility/elastic/flow/datatypes.mdx | 2 +-
.../visibility/elastic/flow/datatypes.mdx | 103 ------------------
.../visibility/elastic/flow/datatypes.mdx | 2 +-
.../visibility/elastic/flow/datatypes.mdx | 103 ------------------
8 files changed, 6 insertions(+), 212 deletions(-)
delete mode 100644 calico-enterprise_versioned_docs/version-3.18-2/visibility/elastic/flow/datatypes.mdx
delete mode 100644 calico-enterprise_versioned_docs/version-3.19-1/visibility/elastic/flow/datatypes.mdx
diff --git a/calico-cloud/visibility/elastic/flow/datatypes.mdx b/calico-cloud/visibility/elastic/flow/datatypes.mdx
index b1fc02a703..4a15f0610c 100644
--- a/calico-cloud/visibility/elastic/flow/datatypes.mdx
+++ b/calico-cloud/visibility/elastic/flow/datatypes.mdx
@@ -61,7 +61,7 @@ The following table details the key/value pairs in the JSON blob, including thei
| `tcp_max_min_rtt` | long | Maximum MinRTT in micro seconds. This field is only available if flowLogsEnableTcpStats is enabled |
| `tcp_mean_mss` | long | Mean TCP MSS. This field is only available if flowLogsEnableTcpStats is enabled |
| `tcp_min_mss` | long | Minimum TCP MSS. This field is only available if flowLogsEnableTcpStats is enabled |
-| `tcp_total_retransmissions` | long | Total retransmitted packets. This field is only available if flowLogsEnableTcpStats is enabled |
+| `tcp_total_retransmissions` | long | Total retransmitted packets. This field is only available if flowLogsEnableTcpStats is enabled |
| `tcp_lost_packets` | long | Total lost packets. This field is only available if flowLogsEnableTcpStats is enabled |
| `tcp_unrecovered_to` | long | Total unrecovered timeouts. This field is only available if flowLogsEnableTcpStats is enabled |
diff --git a/calico-cloud_versioned_docs/version-19-1/visibility/elastic/flow/datatypes.mdx b/calico-cloud_versioned_docs/version-19-1/visibility/elastic/flow/datatypes.mdx
index b1fc02a703..4a15f0610c 100644
--- a/calico-cloud_versioned_docs/version-19-1/visibility/elastic/flow/datatypes.mdx
+++ b/calico-cloud_versioned_docs/version-19-1/visibility/elastic/flow/datatypes.mdx
@@ -61,7 +61,7 @@ The following table details the key/value pairs in the JSON blob, including thei
| `tcp_max_min_rtt` | long | Maximum MinRTT in micro seconds. This field is only available if flowLogsEnableTcpStats is enabled |
| `tcp_mean_mss` | long | Mean TCP MSS. This field is only available if flowLogsEnableTcpStats is enabled |
| `tcp_min_mss` | long | Minimum TCP MSS. This field is only available if flowLogsEnableTcpStats is enabled |
-| `tcp_total_retransmissions` | long | Total retransmitted packets. This field is only available if flowLogsEnableTcpStats is enabled |
+| `tcp_total_retransmissions` | long | Total retransmitted packets. This field is only available if flowLogsEnableTcpStats is enabled |
| `tcp_lost_packets` | long | Total lost packets. This field is only available if flowLogsEnableTcpStats is enabled |
| `tcp_unrecovered_to` | long | Total unrecovered timeouts. This field is only available if flowLogsEnableTcpStats is enabled |
diff --git a/calico-enterprise/visibility/elastic/flow/datatypes.mdx b/calico-enterprise/visibility/elastic/flow/datatypes.mdx
index 012e075cd1..dd4af63568 100644
--- a/calico-enterprise/visibility/elastic/flow/datatypes.mdx
+++ b/calico-enterprise/visibility/elastic/flow/datatypes.mdx
@@ -61,7 +61,7 @@ The following table details the key/value pairs in the JSON blob, including thei
| `tcp_max_min_rtt` | long | Maximum MinRTT in micro seconds. This field is only available if flowLogsEnableTcpStats is enabled |
| `tcp_mean_mss` | long | Mean TCP MSS. This field is only available if flowLogsEnableTcpStats is enabled |
| `tcp_min_mss` | long | Minimum TCP MSS. This field is only available if flowLogsEnableTcpStats is enabled |
-| `tcp_total_retransmissions` | long | Total retransmitted packets. This field is only available if flowLogsEnableTcpStats is enabled |
+| `tcp_total_retransmissions` | long | Total retransmitted packets. This field is only available if flowLogsEnableTcpStats is enabled |
| `tcp_lost_packets` | long | Total lost packets. This field is only available if flowLogsEnableTcpStats is enabled |
| `tcp_unrecovered_to` | long | Total unrecovered timeouts. This field is only available if flowLogsEnableTcpStats is enabled |
diff --git a/calico-enterprise_versioned_docs/version-3.16/visibility/elastic/flow/datatypes.mdx b/calico-enterprise_versioned_docs/version-3.16/visibility/elastic/flow/datatypes.mdx
index 9f57229655..87663de94a 100644
--- a/calico-enterprise_versioned_docs/version-3.16/visibility/elastic/flow/datatypes.mdx
+++ b/calico-enterprise_versioned_docs/version-3.16/visibility/elastic/flow/datatypes.mdx
@@ -61,7 +61,7 @@ The following table details the key/value pairs in the JSON blob, including thei
| `tcp_max_min_rtt` | long | Maximum MinRTT in micro seconds. This field is only available if flowLogsEnableTcpStats is enabled |
| `tcp_mean_mss` | long | Mean TCP MSS. This field is only available if flowLogsEnableTcpStats is enabled |
| `tcp_min_mss` | long | Minimum TCP MSS. This field is only available if flowLogsEnableTcpStats is enabled |
-| `tcp_total_retransmissions` | long | Total retransmitted packets. This field is only available if flowLogsEnableTcpStats is enabled |
+| `tcp_total_retransmissions` | long | Total retransmitted packets. This field is only available if flowLogsEnableTcpStats is enabled |
| `tcp_lost_packets` | long | Total lost packets. This field is only available if flowLogsEnableTcpStats is enabled |
| `tcp_unrecovered_to` | long | Total unrecovered timeouts. This field is only available if flowLogsEnableTcpStats is enabled |
diff --git a/calico-enterprise_versioned_docs/version-3.17/visibility/elastic/flow/datatypes.mdx b/calico-enterprise_versioned_docs/version-3.17/visibility/elastic/flow/datatypes.mdx
index 9f57229655..87663de94a 100644
--- a/calico-enterprise_versioned_docs/version-3.17/visibility/elastic/flow/datatypes.mdx
+++ b/calico-enterprise_versioned_docs/version-3.17/visibility/elastic/flow/datatypes.mdx
@@ -61,7 +61,7 @@ The following table details the key/value pairs in the JSON blob, including thei
| `tcp_max_min_rtt` | long | Maximum MinRTT in micro seconds. This field is only available if flowLogsEnableTcpStats is enabled |
| `tcp_mean_mss` | long | Mean TCP MSS. This field is only available if flowLogsEnableTcpStats is enabled |
| `tcp_min_mss` | long | Minimum TCP MSS. This field is only available if flowLogsEnableTcpStats is enabled |
-| `tcp_total_retransmissions` | long | Total retransmitted packets. This field is only available if flowLogsEnableTcpStats is enabled |
+| `tcp_total_retransmissions` | long | Total retransmitted packets. This field is only available if flowLogsEnableTcpStats is enabled |
| `tcp_lost_packets` | long | Total lost packets. This field is only available if flowLogsEnableTcpStats is enabled |
| `tcp_unrecovered_to` | long | Total unrecovered timeouts. This field is only available if flowLogsEnableTcpStats is enabled |
diff --git a/calico-enterprise_versioned_docs/version-3.18-2/visibility/elastic/flow/datatypes.mdx b/calico-enterprise_versioned_docs/version-3.18-2/visibility/elastic/flow/datatypes.mdx
deleted file mode 100644
index 9f57229655..0000000000
--- a/calico-enterprise_versioned_docs/version-3.18-2/visibility/elastic/flow/datatypes.mdx
+++ /dev/null
@@ -1,103 +0,0 @@
----
-description: Data that Calico Enterprise sends to Elasticsearch.
----
-
-# Flow log data types
-
-## Big picture
-
-{{prodname}} sends the following data to Elasticsearch.
-
-The following table details the key/value pairs in the JSON blob, including their [Elasticsearch datatype](https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-types.html).
-
-| Name | Datatype | Description |
-| --------------------------------- | ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `host` | keyword | Name of the node that collected the flow log entry. |
-| `start_time` | date | Start time of log collection in UNIX timestamp format. |
-| `end_time` | date | End time of log collection in UNIX timestamp format. |
-| `action` | keyword | - `allow`: {{prodname}} accepted the flow.dest_name_aggr
for more information, such as the name of the pod if it was aggregated. |
-| `dest_name_aggr` | keyword | Contains one of the following values:source_name_aggr
for more information, such as the name of the pod if it was aggregated. |
-| `source_name_aggr` | keyword | Contains one of the following values: dest_name_aggr
for more information, such as the name of the pod if it was aggregated. |
-| `dest_name_aggr` | keyword | Contains one of the following values:source_name_aggr
for more information, such as the name of the pod if it was aggregated. |
-| `source_name_aggr` | keyword | Contains one of the following values: