3 ms·

My issue with Kubernetes is mostly broken and oudated YAML configuration for packages. Try google for Nginx kubernetetes, most of results are broken if you appl

My issue with Kubernetes is mostly broken and oudated YAML configuration for packages. Try google for Nginx kubernetetes, most of results are broken if you apply them. Worse, you have no idea to fix them rather than delete resources and try out another way. It's like someone try to update a REST API and forget to update YAML swagger documentation. So K8S, or K3S is not an issue, they're fine, it's the configuration that sucks to keep up with.

hvgk 5y ago
Ah yes. Broken ass helm charts is 90% of my day. I maintain internal forks of about 40 different public charts. Good money but a world of pain.
- pojzon 5y ago
  This seems like a company issue to not see value in updating your stack constantly. Thats a part of being DevOps.
  - hvgk 5y ago
    I think it’s an external QA issue as we have to fix all the broken shit upstream. 90% of the stuff out there is garbage.
4140tm 5y ago
The main reason for not working NGINX examples is because there are two NGINX ingress controllers - one by NGINX and one maintained by k8s. Real fun if one does not know this upfront. Ingress api version changes don't help much, of course