From 1d1887205aa2e1c25091d025c5ca294d7b9abaeb Mon Sep 17 00:00:00 2001 From: Catherine Luse Date: Mon, 19 Oct 2020 11:25:16 -0700 Subject: [PATCH] Fix typo --- content/rancher/v2.x/en/logging/v2.5/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.x/en/logging/v2.5/_index.md b/content/rancher/v2.x/en/logging/v2.5/_index.md index 14043395a47..826efb55e25 100644 --- a/content/rancher/v2.x/en/logging/v2.5/_index.md +++ b/content/rancher/v2.x/en/logging/v2.5/_index.md @@ -277,7 +277,7 @@ You can do the same with Rancher's existing taints, or with your own custom ones Yes, clusters with Windows worker support logging with some small caveats... 1. Windows node logs are currently unable to be exported. -2. ```fluentd-configcheck``` pod(s) will fail due to an [upstream issue](https://github.com/banzaicloud/logging-operator/issues/592), where ```tolerations``` and ```nodeSelector``` settings are not interited from the ```logging-operator```. +2. ```fluentd-configcheck``` pod(s) will fail due to an [upstream issue](https://github.com/banzaicloud/logging-operator/issues/592), where ```tolerations``` and ```nodeSelector``` settings are not inherited from the ```logging-operator```. **Adding NodeSelector Settings and Tolerations for Custom Taints**