| ▲ | bijowo1676 6 hours ago |
| so op just recreated with sticks and tape a very basic feature what k8s does out of the box, and nobody else would be able to support his creation, because its handrolled adhoc with sparse documentation. sounds like ghetto engineering |
|
| ▲ | tomhow 2 hours ago | parent | next [-] |
| Please try to be less snarky and dismissive in comments on HN. The guidelines make it clear we're trying for something better here, and this is meant to be a place where we can appreciate building for its own sake. https://news.ycombinator.com/newsguidelines.html |
|
| ▲ | zzyzxd 5 hours ago | parent | prev | next [-] |
| If this creation stays as is, then it's not very complicated and pretty easy to understand and support. But that is a big IF, and very likely won't be true. Over time people will add more useful features to it, then it becomes another Kubernetes (and if you don't have a strong engineering team, it will probably be much worse than Kubernetes). |
|
| ▲ | cyberax 5 hours ago | parent | prev | next [-] |
| Perhaps we should look the other way: why use K8s if podman-compose can do the same? Maybe we should deprecate it and move towards simpler and more robust solutions? |
| |
| ▲ | canto 5 hours ago | parent [-] | | If all you have is a hammer, everything looks like a nail. | | |
| ▲ | 000ooo000 2 hours ago | parent [-] | | This is just the derogatory version of "picking tech which aligns with existing expertise and resource availability". |
|
|
|
| ▲ | dantillberg 6 hours ago | parent | prev | next [-] |
| [dead] |
|
| ▲ | alexaholic 6 hours ago | parent | prev [-] |
| [flagged] |
| |
| ▲ | tomhow 2 hours ago | parent | next [-] | | Please don't reply to a bad comment with another bad comment on HN. That's how we get flamewars, which is exactly what we want to avoid. https://news.ycombinator.com/newsguidelines.html | |
| ▲ | zzyzxd 5 hours ago | parent | prev | next [-] | | It's totally fine to not to use k8s. Personally, I think I have made several good decisions in my career to use/avoid k8s in different scenarios. But if someone wrote a blog to brag about not using k8s, they can't stop people from wanting to compare their work against k8s. If there's any arrogance in the air, it feels stronger on the other side. | |
| ▲ | bijowo1676 5 hours ago | parent | prev | next [-] | | I am not sure the argument "muhh k8s is too complex, I will roll docker instead" flies well in the age of cloud managed k8s offerings EKS is literally one click of a button away and you dont need to handroll this. even if you dont know AWS console nor terraform, claude code with aws mcp can do that for you | | |
| ▲ | robmccoll 5 hours ago | parent | next [-] | | The problem I have with Kunernetes in general is that everything is slow and configuring everything seems needlessly complex in common use cases. | |
| ▲ | switchbak 5 hours ago | parent | prev [-] | | I worked at a place (a big name in a given vertical!), where the SRE looked at K8S and said "hold my beer". Out came Docker, dnsmasq, miles of duct tape and a whole lot of swearing. Just to come nowhere close to reinventing something better folks were doing years prior. Just because you can (or think you can) doesn't mean you should. I sure do hope no one is maintaining that NIH monstrosity now! |
| |
| ▲ | tbrownaw 5 hours ago | parent | prev [-] | | Are you implying that leaning on standard tooling is more arrogant than "hold my beer"? |
|
