I am very invested, at least emotionally, in Coop Cloud as it is a project that is very much in alignment with what I think the Internet needs to remain useful and free. Won’t go into much detail about this here as this page is more about Coop Cloud than anything else.

More thoughts on Coop Cloud

Here is an unorganized braindump of things I’ve been thinking about regarding Coop Cloud.

  • “Coop Cloud is doing for Docker Swarm what Helm does for Kubernetes”
    • Coop Cloud recipes are analogous to Helm charts.
    • There is a ton that Coop Cloud can learn from the Helm project.
  • Recipes should be managed as archive file packages and not as cloned git repositories.
    • If you want to stick with git, at least make them bare repositories.
    • Gitea already allows you to manage packages per git repositories or organization.
    • Gitea can serve as a recipe repository.
  • Suggested architecture for recipe repositories.
    • One git repository, multiple recipe components as packages.
  • There needs to be something like a coop equivalent of artifacthub.io.
    • Allow listing of multiple recipe repositories.
  • Visual discipline is needed for a seamless user experience.

Let’s think about the infrastructure of Coop Cloud at the moment

  • coopcloud.tech home site
  • git.coopcloud.tech Gitea instance
  • recipes.coopcloud.tech site catalogue of recipes
  • docs.coopcloud.tech

Heretical thoughts

  • Bear with me here. I think it might be worth seriously considering a move towards k3s.
    • A lot of energy and breath has been spent defending docker Swarm.
    • Kubernetes is complex and hard; That’s why there are currently so many projects that attempt to build solutions to make Kubernetes simpler.
    • Kubernetes is resource intensive and requires multiple nodes out of the box.
    • K3s is a lightweight version of Kubernetes.
  • The paradigms for abra and Coop Cloud development would shift fundamentally from building around a tool, to building on top of a tool.
  • I need to cite sources for the following statement: Kubernetes projects get a lot more attention and funding than do projects around docker swarm. It might be wise to tap into that for the sake of the Coop Cloud project’s funding.
  • Tools like Kompose would help make the transition from Swarm to K3s a lot less painful.