You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The configured pull secret was not part of the pod spec for fluentbit and thus the config-reloader image could not be pulled.
Expected behaviour:
I expected that the configured pull secret appears as part of the pod spec for fluentbit pods and that the config-reloader image is pulled through our internal image registry.
Steps to reproduce the bug:
Apply FluentbitAgent with configHotReload using at least one image.imagePullSecrets
Look at spec of running fluentbit pods whether the pull secret appears
Hello @sebhoss
This was fixed and merged. It will be included in the next release.
In the meantime, you can pass your imagepullsecret for configReloader in the fluentbit one at FluentbitAgent.spec.image.imagePullSecrets.
Describe the bug:
I created a
FluentbitAgent
like this:The configured pull secret was not part of the pod spec for fluentbit and thus the config-reloader image could not be pulled.
Expected behaviour:
I expected that the configured pull secret appears as part of the pod spec for fluentbit pods and that the config-reloader image is pulled through our internal image registry.
Steps to reproduce the bug:
FluentbitAgent
withconfigHotReload
using at least oneimage.imagePullSecrets
Additional context:
none
Environment details:
/kind bug
The text was updated successfully, but these errors were encountered: