Open jamonation opened 1 month ago
@jamonation have you tried the latest image that will be built on every PR
@jamonation @benjaminhuo I'm also getting the same error. The workaround to move from
container: repository: "kubesphere/fluent-operator" tag: v2.1.0 tag: v2.8.0
Isn't working?
I'll try latest and report back @benjaminhuo, thanks for the help!
This is issue for us too, cannot seem to use 2.8 or 2.9
I dont see being able to use disableComponentControllers: "fluentd" and make use of fluent-bit configurations. This results into
2024-05-28T13:21:44Z ERROR controller-runtime.source if kind is a CRD, it should be installed before calling Start ......
Also relative to:
https://github.com/fluent/fluent-operator/blob/v2.9.0/charts/fluent-operator/templates/fluent-operator-deployment.yaml#L101-L107
The logic is totally changed from v2.7.0
2.9.0 -> putting as same arg 2.7.0 -> as seperate value for arg
Describe the issue
I'm running into an issue building a fluent-operator image using the Makefile, or using the
go build ...
invocation and packaging the resultingmanager
binary into an image. Either approach results in pod restarts when deploying the operator.The errors look like the following:
Example MultilineParser error using
docker build
imageExample ClusterMultilineParser from
go build...
imageBoth methods will show both Cluster/Multiline errors and the pod will restart. The operator will however create fluent-bit and fluentd pods given the appropriate manifest.
To Reproduce
build the image
helm install
Expected behavior
The pod should not be restarting and throwing errors about CRDs.
Your Environment
v2.8.0
containerd://1.7.15-k3s1
Linux d186e0ca7a21 6.6.16-linuxkit #1 SMP Fri Feb 16 11:54:02 UTC 2024 aarch64 Linux
How did you install fluent operator?
Using helm:
Additional context
Running with the
kubesphere/fluent-operator:v2.8.0
image explicitly, or by not setting theoperator.container.repository
value in the helm chart results in no errors.