Fluent-bit container deployment failed in Windows nodes

[tjgitdh]

I'm trying to deploy fluent-bit to Windows by using the Windows image fluent/fluent-bit:windows-2019-2.0.9.
But it failed and the the pod describe is attached

Name: fluent-bit-monitor-windows-2019-c5ddb
Namespace: kube-system
Priority: 0
Service Account: fluent-bit-monitor-windows-2019
Node: akswinnode001/10.50.16.28
Start Time: Wed, 15 Mar 2023 17:46:12 +0530
Labels: app.kubernetes.io/instance=fluent-bit-monitor-windows-2019
app.kubernetes.io/name=fluent-bit
controller-revision-hash=5466575b8d
kubernetes.io/cluster-service=true
pod-template-generation=1
Annotations: checksum/config: 2791234556678888888888888888888888888888888888888888888888888888888
checksum/luascripts: 333333333333333333444444444444455555555555555555556666666666666
Status: Pending
IP:
IPs:
Controlled By: DaemonSet/fluent-bit-monitor-windows-2019
Containers:
fluent-bit:
Container ID:
Image: fluent/fluent-bit:windows-2019-2.0.9
Image ID:
Port: 2020/TCP
Host Port: 0/TCP
State: Waiting
Reason: ContainerCreating
Ready: False
Restart Count: 0
Limits:
cpu: 500m
memory: 200Mi
Requests:
cpu: 100m
memory: 150Mi
Liveness: http-get http://:http/ delay=0s timeout=1s period=10s #success=1 #failure=3
Readiness: http-get http://:http/api/v1/health delay=0s timeout=1s period=10s #success=1 #failure=3
Environment:
KUBERNETES_SERVICE_HOST: ppla001-836e2d07.hcp.eastus.azmk8s.io
FLUENT_AZURE_WORKSPACE_ID: <set to the key 'WSID' in secret 'ama-logs-secret'> Optional: false
FLUENT_AZURE_WORKSPACE_KEY: <set to the key 'KEY' in secret 'ama-logs-secret'> Optional: false
KUBERNETES_PORT_443_TCP_ADDR: ppla001-836e2d07.hcp.eastus.azmk8s.io
KUBERNETES_PORT: tcp://ppla001-836e2d07.hcp.eastus.azmk8s.io:443
KUBERNETES_PORT_443_TCP: tcp://ppla001-836e2d07.hcp.eastus.azmk8s.io:443
Mounts:
/etc/machine-id from etcmachineid (ro)
/fluent-bit/etc/custom_parsers.conf from config (rw,path="custom_parsers.conf")
/fluent-bit/etc/fluent-bit.conf from config (rw,path="fluent-bit.conf")
/var/lib/docker/containers from varlibdockercontainers (ro)
/var/log from varlog (rw)
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-8dg9v (ro)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
config:
Type: ConfigMap (a volume populated by a ConfigMap)
Name: fluent-bit-monitor-windows-2019
Optional: false
varlog:
Type: HostPath (bare host directory volume)
Path: /var/log
HostPathType:
varlibdockercontainers:
Type: HostPath (bare host directory volume)
Path: /var/lib/docker/containers
HostPathType:
etcmachineid:
Type: HostPath (bare host directory volume)
Path: /etc/machine-id
HostPathType: File
kube-api-access-8dg9v:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
ConfigMapOptional:
DownwardAPI: true
QoS Class: Burstable
Node-Selectors: kubernetes.azure.com/os-sku=Windows2019
kubernetes.io/os=windows
Tolerations: :NoExecute op=Exists
:NoSchedule op=Exists
Events:
Type Reason Age From Message

---

Normal Scheduled 10m default-scheduler Successfully assigned kube-system/fluent-bit-monitor-windows-2019-c5ddb to akswinnode001
Warning FailedMount 6m41s kubelet Unable to attach or mount volumes: unmounted volumes=[etcmachineid], unattached volumes=[kube-api-access-8dg9v config varlog varlibdockercontainers etcmachineid]: timed out waiting for the condition
Warning FailedMount 4m23s (x2 over 8m56s) kubelet Unable to attach or mount volumes: unmounted volumes=[etcmachineid], unattached volumes=[config varlog varlibdockercontainers etcmachineid kube-api-access-8dg9v]: timed out waiting for the condition
Warning FailedMount 2m8s kubelet Unable to attach or mount volumes: unmounted volumes=[etcmachineid], unattached volumes=[etcmachineid kube-api-access-8dg9v config varlog varlibdockercontainers]: timed out waiting for the condition
Warning FailedMount 42s (x13 over 10m) kubelet MountVolume.SetUp failed for volume "etcmachineid" : hostPath type check failed: /etc/machine-id is not a file

[tjgitdh]

I think we need to give windows specific volume mounts

https://github.com/fluent/helm-charts/blob/main/charts/fluent-bit/values.yaml#:~:text=fluent%2Dbit.fullname%22-,volumeMounts,true,-args