Every time we update openshift in azure, my cribl config is lost.
since we have the free version, we cannot use git repository.
would using persistent storage helps keep the config because the update process drains the node from the cluster and restart them on another node. I suspect this is why the config is not kept.
I’m bringing this question back hoping to get an answer this time
Hello, Cribl configs for worker groups are kept within your Leader node rather than the Workers so I’m not sure why you’d encounter an issue. If an Openshift Cribl Stream worker node is wiped/replaced, you can just rebuild a replacement.
If you wish to preserve key elements of a Cribl deployment or experiment with portability you can always try a packs based approach and export these to your preferred storage location yourself.
From a design philosophy viewpoint, I’d suggest you should (ideally) plan and account for Worker Nodes to be stateless. Whilst this isn’t strictly true as data dwells for buffering, processing and queuing, it does help with a replacement or interchange approach which marries up with with a container based deployment architecture.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.