11–20 of 172 posts
Kubernetes no thanks. Terraform + Kamal [1] on Digital Ocean is the way I deploy/run apps now. [1] https://kamal-deploy.org/
Why is this better then Ansible + Docker Compose?
Hi everyone, We've gone through a lot of pain to get this blueprint working since our AWS costs were getting out of hand but we didn't want to part ways with CDK. We've now got the same stack structure going with Pulumi and Digital ocean, having the same ease of development with at least 60% cost reduction.
Keep an eye on reachability and performance. I’ve seen DO consistently perform terribly and/or drop connections for months (that is, didn’t look like some brief routing glitch somewhere) for some US and Canadian routes (not, like, Sri Lanka or something) on excellent Internet connections. The fix was moving to AWS, problem gone. It felt like a shitty-peering-agreements issue.
It’s not a drop in replacement. It might be worth it depending on what you’re doing.
Earlier quoted context omitted.
Plain Podman systemd integration is way more powerful and secure, as it does not mess with firewall and allows to run rootless containers using services. It's even possible to run healthchecks and enforce building images just before starting service making on-demand containers using systemd-proxyd possible. Check example: https://github.com/Mati365/hetzner-podman-bunjs-deploy
> way more powerful and secure I don't care about powerful. That's the opposite of what I want. I could just use k8s if I cared about that.
Kubernetes no thanks. Terraform + Kamal [1] on Digital Ocean is the way I deploy/run apps now. [1] https://kamal-deploy.org/
I've looked into Kamal but it feels so "It's as complex as Kubernetes but isn't so support is going to be nightmarish." Why is this better then Ansible + Docker Compose?
Earlier quoted context omitted.
Keep an eye on reachability and performance. I’ve seen DO consistently perform terribly and/or drop connections for months (that is, didn’t look like some brief routing glitch somewhere) for some US and Canadian routes (not, like, Sri Lanka or something) on excellent Internet connections. The fix was moving to AWS, problem gone. It felt like a shitty-peering-agreements issue.
People will pretend that this quality difference doesn’t exist in networking, uptime, server quality. It’s not a drop in replacement. It might be worth it depending on what you’re doing.
Earlier quoted context omitted.
> way more powerful and secure I don't care about powerful. That's the opposite of what I want. I could just use k8s if I cared about that.
It looks like you don't even care about opening documentation before pressing reply. Podman is a simple hammer without any moving parts, that used properly can be used to build fancy stuff without much knowledge.
Kubernetes no thanks. Terraform + Kamal [1] on Digital Ocean is the way I deploy/run apps now. [1] https://kamal-deploy.org/
Plain Podman systemd integration is way more powerful and secure, as it does not mess with firewall and allows to run rootless containers using services. It's even possible to run healthchecks and enforce building images just before starting service making on-demand containers using systemd-proxyd possible. Check example: https://github.com/Mati365/hetzner-podman-bunjs-deploy
EKS has become a clusterf*ck to manage and provision. This looks very useful. Bare metal k8s, even running on EC2, might be another option.
Earlier quoted context omitted.
Plain Podman systemd integration is way more powerful and secure, as it does not mess with firewall and allows to run rootless containers using services. It's even possible to run healthchecks and enforce building images just before starting service making on-demand containers using systemd-proxyd possible. Check example: https://github.com/Mati365/hetzner-podman-bunjs-deploy
Does it support zero downtime deploys?