At the startup I last worked at, we used a Docker/Kubernetes stack for our SaaS product.
We found the lack of environment / concurrent build support a huge bottleneck though, so I developed a tool to make it much easier to deploy kubernetes projects.
I recently open sourced it and launched it, take a look! [1]
The website itself is also using sanic and open source, in case you want an example [2]
Please let me know if you have any feedback! I'd love to know which features are most important to work on next.
This tool looks useful, but the first thing I see when I hit the landing page is this:
> Tired of kubernetes tools that don't prioritize user experience?
This is quite a loaded sentence. It ignores whatever reasoning there may be (design, resourcing, differences of opinion) behind the state of Kubernetes tooling, and even assumes that the tooling is bad, and assumes that you have the answer.
I'm all for simple, strong statements to pitch a product, but this instead feels adversarial, derogatory, and potentially naive.
I'm sure this is not your intention, so it would be a shame for this to be the first impression the community gets of Sanic.
Perhaps "Ready for the next evolution of Kubernetes tooling?" might be a bit more positive?
At the startup I last worked at, we used a Docker/Kubernetes stack for our SaaS product.
We found the lack of environment / concurrent build support a huge bottleneck though, so I developed a tool to make it much easier to deploy kubernetes projects.
I recently open sourced it and launched it, take a look! [1]
The website itself is also using sanic and open source, in case you want an example [2]
Please let me know if you have any feedback! I'd love to know which features are most important to work on next.
[1] https://github.com/distributed-containers-inc/sanic [2] https://github.com/distributed-containers-inc/sanic-site