Live data from Hacker News

Infrastructure as Code Should Feel

scalefactory.com

51–52 of 52 posts

Re: Infrastructure as Code Should Feel

#51
post #47

I think more about culture that you should have "automate first" mindset. Yes, changing 500 lines in a text file if you can write grep replace in 30 seconds is nice. Automating deployment that you are doing once a month and is taking 20 mins to prepare and run, I don't feel it. Because developing such automation takes considerable resources especially if you cannot test it right away on prod and have to make test env…

Automation is not only about saving time, it's also about guaranteeing consistency and quality.

Re: Infrastructure as Code Should Feel

#52
post #46
post #24

Earlier quoted context omitted.

I was about to disagree with you until I read the part where you are using terraform with k8s. IaC starts breaking down once you start using k8s - especially if you are using a flavor like EKS that is both kubernetes but is also its own IaC platform.

k8s has its own built in IaC with object definitions (usually yaml or some sort of yaml templates) and controllers to apply the changes. I don't think most people are managing k8s objects directly with edit/patch--they're just applying complete yaml/object definitions to override current state. If you want drift/auto apply you can use a CD solution like Argo

Yes, that is what I was referring to.
Post reply on HN