3 ms·
>For example, you're no longer manually editing nginx conf, You now have to do the configuration in YAML, which is MUCH MUCH worse.
by mrweasel 6y ago
>For example, you're no longer manually editing nginx conf,
You now have to do the configuration in YAML, which is MUCH MUCH worse.
- zimbatm 6y agoOr more accurately, you now have to understand both the nginx.conf file format, and the right way to nudge the YAML so it produces what you want. Plus some intermediate wrapper script that sets things up on container start that does more funky things based on environment variables.
- what2build 6y agoWhich is really weird we do this since 80% of tasks fall within sane defaults territory. My last employer had something like 10 hits every 5 minutes. Somehow we needed the entire Kube ecosystem for that. I’ve been storing good JSON templates in Dynamodb and iterating on code to query and deploy. Building up a collection that lets me deploy to AWS or GCP with one tool, editing fields I want to edit per setup. Working with just my code and validating outputs is way less. On the one hand everyone is all “write less code, it’s too complicated.” while ignoring ops tooling always ends up a fiasco of DSLs and templating hell.
- nouney 6y agoI don't get it, how do you configure nginx with a YAML file?
- verdverm 6y agoYou don't directly. You add some extra lines of yaml to an k8s ingress resource, nginx detects this and updates itself. A single nginx container can service many ingresses for each of your apps. The idea is to distribute the config to the app manifests they are related to