fluentbit resource does not create daemonsets

[anthonyoride]

Describe the issue

i have deployed fluentbit using the operator following the official guide https://github.com/kubesphere-sigs/fluent-operator-walkthrough. however i don't see the fluent bit daemonsets.

To Reproduce

below is my resource definition as seen from the official guide

apiVersion: fluentbit.fluent.io/v1alpha2
kind: FluentBit
metadata:
name: fluent-bit
namespace: fluent
labels:
app.kubernetes.io/name: fluent-bit
spec:
image: kubesphere/fluent-bit:v1.8.11
positionDB:
hostPath:
path: /var/lib/fluent-bit/
resources:
requests:
cpu: 10m
memory: 25Mi
limits:
cpu: 500m
memory: 200Mi
fluentBitConfigName: fluent-bit-only-config
tolerations:

• operator: Exists

Expected behavior

with the above custom resource, fluent bits daemonsets should be created but they are not.

Your Environment

- Fluent Operator version: v1.8.11
- Container Runtime: crio
- Operating system: linux
- Kernel version:

How did you install fluent operator?

fluent was installed using the manifest => https://raw.githubusercontent.com/fluent/fluent-operator/release-2.5/manifests/setup/setup.yaml

Additional context

No response

[cw-Guo]

You need a ClusterFluentBitConfig manifest too to create a daemonset.
Quoted from the original workthrough

The FluentBit CR works together with ClusterFluentBitConfig and they should be created together.

[anthonyoride]

@cw-Guo thanks for your response. i did have the ClusterFluentBitConfig created as well.

apiVersion: fluentbit.fluent.io/v1alpha2
kind: ClusterFluentBitConfig
metadata:
name: fluent-bit-config
labels:
app.kubernetes.io/name: fluent-bit
spec:
service:
parsersFile: parsers.conf
inputSelector:
matchLabels:
fluentbit.fluent.io/enabled: "true"
fluentbit.fluent.io/mode: "k8s"
filterSelector:
matchLabels:
fluentbit.fluent.io/enabled: "true"
fluentbit.fluent.io/mode: "k8s"
outputSelector:
matchLabels:
fluentbit.fluent.io/enabled: "true"
fluentbit.fluent.io/mode: "k8s"

I created every resources quoted in the docs

[anthonyoride]

this is resolved it was due to the fluentBitConfigName field in the fluentbit resource not matching with the name of the ClusterFluentBitConfig name