Just visit the repo: https://github.com/docker/machine It is archived and hasn't had a commit in almost 2.5 years. See also: https://github.com/docker/roadmap/issues/245. - Source: Hacker News / over 2 years ago

I applaud the decision to use AGPL-3.0. For me, it's a license that provides forward guarantees to the Community: no proprietary forks can happen, so any fork will be an OSS fork from which the upstream project may benefit too, which benefits all users. That's the reason we chose this license for StackGres [1], another project in the Postgres space. [1]: https://stackgres.io. - Source: Hacker News / about 1 month ago

This is good and interesting recipe to get Keycloak and Postgres on Kubernetes. There is an important improvement, though: the Postgres deployed here is not production ready (high availability, backups, monitoring, etc). We run Keycloak on StackGres [1] which gives us production-ready Postgres setup (disclaimer: it's dogfooding). Happy to share the YAML manifests used to deploy Keycloak with StackGres. Maybe we... - Source: Hacker News / about 1 year ago

Others have been mentioned already and there's also stackgres. Source: about 1 year ago

The key for me is the level of automation that you can reach at a reasonable "development cost". Let me elaborate. K8s, if anything, is an API. An API that allows you to interact with compute, storage and networks in a way that is abstracted from the actual underlying infrastructure. This is incredibly powerful. You can, essentially, code and automate all your infrastructure. But this goes beyond deployment,... - Source: Hacker News / over 1 year ago

I haven't used that one. I've looked into StackGres before and it seems pretty slick, but based on the featureset, I don't think that it has multi-master support yet. Source: over 1 year ago