Markus Thömmes
Markus Thömmes
I think we should start thinking about this more holistically. This is also related to #4557 which is a broader issue about dealing with and surfacing pod issues past the...
@vagababov is looking at this realm now. I'll assign since it'll likely impact the behavior here too. /assign @vagababov
@benjaminhuo @wenchajun this seems worth pulling in.
@benjaminhuo @wenchajun this seems worth pulling in.
@benjaminhuo @wenchajun this seems worth pulling in.
Config generation itself should be fairly straightforward for me to implement in the watcher. I'd imagine that's a bit of RBAC + moving the code + adding a few flags...
This made me wonder actually: Once config generation is inside the watcher, do we need the fluentbit-manager itself at that point? We could pass `FluentBitConfigName` and `NamespacedFluentBitCfgSelector` to the watcher...
Hmm. Checkpoint/Restore seems rather finicky in the presence of hostPath mounts anyway, I think? There's no guarantee that the host's filesystem looks identical on another machine I guess 🤔. Isn't...
For my somewhat specific use-case of fluent-bit specifically, I do believe that just having stable inode numbers across pods would be sufficient. For posterity, their sqlite DB looks like this...
@ayushr2 do you have a feeling for whether or not your proposal could be massaged into an acceptable state wrt. S/R or if it could be put behind a flag...