Live data from Hacker News

Viewing profile — psviderski

psviderski

HN member
Joined
Mon, Jul 15, 2024, 6:58 AM UTC
HN karma
433
Public activity
78 items

About psviderski

Building a simpler Kubernetes alternative: https://uncloud.run

ex-Canva, ex-JetBrains, ex-Wargaming

Contacts:

  https://x.com/psviderski
  https://t.me/spyyy
  me@psviderski.name

Recent public activity

  1. comment
    Comment #48550447

    >I think there is a real hole in the market for a simple solution that lets you deploy some containers to some instances in a declarative fashion without all of that complexity Tha…

  2. story
  3. comment
    Comment #47888121

    There is very little reason to need auto-scaling when you run on pre-purchased VMs/servers. You've paid for all the compute so you can run as many replicas as it can fit and you ne…

  4. comment
    Comment #47886367

    Yep, the latest release embeds the install script in the CLI binary instead of using curl | sh, so it's versioned together with the CLI.

  5. comment
    Comment #47884293

    Why would you want to use K8s for one or two beefy servers? It's designed for solving a different problem at a large scale.

  6. comment
    Comment #47873865

    Yes but at small scale. Myself and a handful of others from our Discord run it in production. The core build/push/deploy workflows are stable and most of the heavy lifting at runti…

  7. comment
    Comment #47873633

    A single VM is indeed the most pragmatic setup that most apps really need. However I still prefer to have at least two for little redundancy and peace of mind. It’s just less stres…

  8. comment
    Comment #46187867

    > In fact could you not just cron the cli deployment command on the nodes and get an effective poor man's declarative layer to guard against node failures if your ok with a 1 min o…

  9. comment
    Comment #46156080

    No, and this is out of scope at least for now. Please see another reply: https://news.ycombinator.com/item?id=46146434

  10. comment
    Comment #46156056

    Haha the K8s knowledge will definitely pay off. But Uncloud did exist three months ago. Clearly my marketing needs work :D On the bright side, you can always use both

  11. comment
    Comment #46156013

    Uncloud is a bit lower-level, CLI-only (for now), with no central server. If some nodes go offline, the rest keep working and stay manageable. It also has the WireGuard overlay net…

  12. comment
    Comment #46155844

    >with swarm and traefik, I can define url rewrite rules as container labels. Is something equivalent available? Yep, you define the mapping between the domain name and the internal…

  13. comment
    Comment #46155583

    How was your Swarm experience so far? It's so disappointing that Docker seems to slowly but steadily abandoning it. There is only a couple dozen mainly maintenance commits in the s…

  14. comment
    Comment #46155474

    As I mentioned in the sibling comment, please note that in this case you only get round-robin, not failover. If one of the addresses is down, the DNS record will continue returning…

  15. comment
    Comment #46155415

    Thanks! If you're running the ucloud cluster in AWS, service containers should be able to access RDS the same way the underlying EC2 instances can (assuming RDS is in the same VPC …

  16. comment
    Comment #46155287

    Great setup! Where Uncloud helps is when you need containers across multiple machines to talk to each other. Your setup sounds like single-node or nodes that don't need to discover…

  17. comment
    Comment #46155140

    >A normal person wouldn't think 'hey lets use k8s for the low stakes deployment over here'. I'm afraid I have to disappoint you

  18. comment
    Comment #46147691

    Fair points on the career and onboarding angle. It’s hard to argue against "everyone knows it". But with that mentality, we'd never challenge anything. COBOL was the industry stand…

  19. comment
    Comment #46147262

    Uncloud is lower-level. Dokploy seems to be positioning as a PaaS with a web UI using Docker Swarm under the hood for multi-node container management. Uncloud operates at that same…

  20. comment
    Comment #46147050

    This is exactly how it works now. The Compose file is the declarative specification of your services you want to run. When you run 'uc deploy' command: - it reads the spec from you…

  21. comment
    Comment #46146893

    For the public cluster with multiple ingress (caddy) nodes you'd need a load balancer in front of them to properly handle routing and outage of any of them. You'd use the IP of the…

  22. comment
    Comment #46146837

    I don't know what the specific requirements for the distributed erlang/elixir but I believe the networking should support it. Containers get unique IPs on a WireGuard mesh with dir…

  23. comment
    Comment #46146805

    Come join our cozy Discord server https://uncloud.run/discord . There is one guy joined recently who is migrating his homelab setup from Swarm right now. Also another community mem…

  24. comment
    Comment #46146615

    Totally valid concern. That was a shortcut to iterate quickly in early development. It’s time to do it properly now. Appreciate the feedback. This is exactly the kind of thing I ne…

  25. comment
    Comment #46146434

    Thank you! That's actually the trade off. There is no automatic rescheduling in uncloud by design. At least for now. We will see how far we can get without it. If you want your ser…