Taking a swing at the operator over the past week,...
# fluent-operator
r
Taking a swing at the operator over the past week, and ran into a little snag trying to follow the various scenarios in the walkthrough. I went for the fluentbit to fluentd collector scenario, and it seems fluentd is requesting a volume for buffering. I was struggling with finding the CR value that disables/overrides this behaviour (permanence in helm I believe). Anyone possibly give me a pointer or ref link to disabling the request for a pvc (memory/ephemeral storage scenario) for the fluentbit to fluentd forward scenario? Thank you for any help, been a fun tool to play around with.
I think I may have finally stumbled on it testing, will post in case anyone else ever gets stuck digging for it lol
Copy code
---
apiVersion: <http://fluentd.fluent.io/v1alpha1|fluentd.fluent.io/v1alpha1>
kind: Fluentd
metadata:
  name: fluentd
  labels:
    <http://app.kubernetes.io/name|app.kubernetes.io/name>: fluentd
spec:
  globalInputs:
  - forward:
      bind: 0.0.0.0
      port: 24224
  replicas: 1
  image: kubesphere/fluentd:v1.14.6
  buffer:
    disableBufferVolume: true
In case anyone else gets stuck the buffer line was the key., unfortunately hit a wall on needing a custom armhf kube-logging image to keep gong forward as the arm64 doesnt work on a k3s/raspberry pi 4 setup. Will tackle fluentd at a later time in this RnD
to note the fluent/fluentd image has an armhf it works, but lacks the plugins to support the operator built in. Running a registry and hosting images wasnt in this particular project
p
To be honest, we've just been moving to Fluent Bit for all aggregation and dropping fluentd entirely. It probably depends on your specific plugin needs though
r
I pivoted to that in my RnD for now, I find the market has a both styles commonly used still, I think alot of engineers like th elayered approach more out of comfort, I tend to as well, but its mostly inconsequential. I just liked my classic style in the walkthrough and was like lemme try my goto. Really the only gotcha was the lack of armhf support that stopped me, sad reason, but not my first exp with the fun of arm