From 0656aa0652546bd3d774ad00fecf7e3e9fa0e824 Mon Sep 17 00:00:00 2001 From: Nick Gerace Date: Sun, 18 Oct 2020 13:21:59 -0400 Subject: [PATCH 1/2] Add clarification on Windows logging support Add clarification on Windows logging support with some caveats. These will be subject to change with upstream fixes and internal improvements. --- content/rancher/v2.x/en/logging/v2.5/_index.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) 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 42fea2004b4..14043395a47 100644 --- a/content/rancher/v2.x/en/logging/v2.5/_index.md +++ b/content/rancher/v2.x/en/logging/v2.5/_index.md @@ -272,11 +272,12 @@ spec: In the above example, we ensure that our pod only runs on Linux nodes, and we add a ```toleration``` for the taint we have on all of our Linux nodes. You can do the same with Rancher's existing taints, or with your own custom ones. -**Why do we not schedule logging-related pods on Windows nodes?** +**Are clusters with Windows worker nodes supported?** -No parts of the logging stack are compatible with Windows Kubernetes nodes. -For instance, if a logging pod is attempting to pull its image from a container registry, there may only be Linux-compatible images available. -In this scenario, the pod would be stuck in an ```ImagePullBackOff``` status; and would eventually change to a ```ErrImagePull``` status. +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```. **Adding NodeSelector Settings and Tolerations for Custom Taints** From 1d1887205aa2e1c25091d025c5ca294d7b9abaeb Mon Sep 17 00:00:00 2001 From: Catherine Luse Date: Mon, 19 Oct 2020 11:25:16 -0700 Subject: [PATCH 2/2] 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**