News for hackers. Stuff that matters.
Re:Do not do in code what can be done in infrastructure (2017) by tootie on Friday August 13, 2021 @01:08PM (#28171618)
I'm sitting here trying to make sense of how nginx parses regexes and I feel this in my bones. Any critical function buried in infrastructure is going to be inherently so much harder to debug and test in a predictable way. I lean towards putting as much as possible into application code and keeping infra as simple as possible.
Re:Do not do in code what can be done in infrastructure (2017) by robertlagrant on Friday August 13, 2021 @03:29PM (#28173433)
I agree. I think k8s virtualizing ingress, networking, monitoring, restarting, logging is brilliant; I just wish I could write code to make it happen instead of reams of YAML.
Re:Do not do in code what can be done in infrastructure (2017) by p_l on Sunday August 15, 2021 @02:03PM (#28190831)
Remember that kubernetes doesn't actually use YAML anywhere - it just makes it available as convenience, and you can just as well call the API manually or use one of the client libraries.
Re:Do not do in code what can be done in infrastructure (2017) by javagram on Friday August 13, 2021 @06:56PM (#28175843)
Generating the yaml-equivalent config files using Jsonnet can help with this, I rarely see it mentioned online though.