nodeAgents deprecated - how to enable windows support?

[mweibel]

We're using logging-operator since >3 years and finally are upgrading to the latest and greatest version.
Since we unfortunately need windows nodes in our cluster, we also need windows support.

So far we've enabled it by setting nodeAgents in the Logging CRD as follows:

nodeAgents:
  - name: winagent
    profile: windows
    nodeAgentFluentbit:
      tls:
        enabled: false
      inputTail:
        Buffer_Chunk_Size: "1MB"
        Buffer_Max_Size: "5MB"
      daemonSet:
        spec:
          template:
            spec:
              nodeSelector:
                kubernetes.io/os: windows
              tolerations:
                - operator: Exists
              containers:
                - name: fluent-bit
                  image: fluent/fluent-bit:windows-2019-2.2.2
                  resources:
                    limits:
                      cpu: 500m
                      memory: 500M
                    requests:
                      cpu: 200m
                      memory: 200M

I've seen in the CRD docs that nodeAgents is going away soon.

So, how do I enable and configure windows support? :)

Thank you.

[pepov]

The development on that API got deprioritized and no one picked it up since. The original plan was to move that feature out to a separate CRD but the code would need to be aligned with the legacy code powering the fluentbit spec (the same that is used by the new FluentbitAgent CRD as well), so it would require significant effort. We don't plan to remove it without a way out, but please note, that the code behind it has not received any updates or new features for almost a year and the future of the whole API is a bit uncertain now, probably time to revisit.

[mweibel]

thank you for your answer. Yeah we'll keep that in mind. We've successfully tested the latest version including windows support so far and it works well enough. If we see something we'll for sure provide issues and/or PRs to help with it 👍