3 ms·
You mention a questionably designed custom operator and an add-on from a SIG. This is like blaming Linux for the UI in Gimp.
by antonvs 10mo ago
You mention a questionably designed custom operator and an add-on from a SIG. This is like blaming Linux for the UI in Gimp.
- jbaiter 10mo agoAlso not like logging setups outside of k8s can't be a horror show too. Like, have you ever had to troubleshoot a rsyslog based ELK setup? I'll forever have nightmares from debugging RainerScript mixed with the declarative config and having to read the source code to find out why all of our logs were getting dropped in the middle of the night.
- NewJazz 10mo agoI'd also argue the whole external DNS thing could have happened with any dynamic DNS automation... And yes it is a completely optional add-on!
- zsoltkacsandi 10mo ago> a questionably designed custom operator This is the logging operator, the most used logging operator in the cloud native ecosystem (we built it). > This is like blaming Linux for the UI in Gimp. I never blamed anything, read my comment again. I only pointed out that problems arise when you use something to do something that is not built for. Like a container orchestrator managing infrastructure (DNS, logging pipelines). That is why I wrote to "it is super important to treat a container orchestrator a container orchestrator". Not a logging pipeline orchestrator, or a control plane for Route 53 DNS. This has nothing to do with Kubernetes, but with the people who choose to do everything with it (managing the whole infrastructure).