We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Even after specifying custom docker image for fluent bit, default image is being used in the fluent-bit pods.
Fluentbit daemonset configuration
apiVersion: fluentbit.fluent.io/v1alpha2 kind: FluentBit metadata: name: fluent-bit namespace: fluent labels: app.kubernetes.io/name: fluent-bit spec: {{- with .Values.fluentbit.annotations }} annotations: {{- toYaml . | nindent 4 }} {{- end }} image: eu.gcr.io/fluent-operator-fluentbit:3.1.7-sap0 {{- with .Values.fluentbit.imagePullSecrets }} imagePullSecrets: {{- toYaml . | nindent 4 }} {{- end }} imagePullPolicy: {{ .Values.fluentbit.imagePullPolicy }} positionDB: hostPath: path: /var/lib/fluent-bit/ resources: requests: cpu: {{ .Values.fluentbit.requests.cpu }} memory: {{ .Values.fluentbit.requests.memory }} limits: cpu: {{ .Values.fluentbit.limits.cpu }} memory: {{ .Values.fluentbit.limits.memory }} fluentBitConfigName: fluent-bit-only-config tolerations: - operator: Exists
Fluent bit pods should be created with the custom docker image.
- Fluent Operator version: 3.1.0 - Container Runtime: docker - Operating system: linux - Kernel version: 6.6.35-cloud-amd64
Using helm chart version 3.1.0
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the issue
Even after specifying custom docker image for fluent bit, default image is being used in the fluent-bit pods.
Fluentbit daemonset configuration
Actual fluentbit daemonset pod
To Reproduce
Expected behavior
Fluent bit pods should be created with the custom docker image.
Your Environment
How did you install fluent operator?
Using helm chart version 3.1.0
Additional context
No response
The text was updated successfully, but these errors were encountered: