This is an insightful article. A learning for me was how the author managed to switch multiple cloud providers even while being a one man SAAS.
Kubernetes is overwhelming because of 2 things: Overload of terminology, and Distributed systems day 2 operations.
Author succeeds so well because he has a starter stack (install, CI pipeline, secure, monitor, scale) maintained as code, and it works every time.
For someone starting new, the learning curve is high. Bootstrapping is easy, but day 2 on kubernetes is hard. Benefits outweigh is learning curve imho.
Specific to DigitalOcean kubernetes API server issues, we have rolled out some resource provisioning improvements for newly created clusters very recently. Also making ongoing improvements to backend monitoring.
Thanks for the response! To clarify, I still a happy customer of DO, and would still use it for some other projects.
I have also had a fair share of issues with AWS services in the past (Athena, they took care of it a few months later), and GCP too. And I understand that no product is ever perfect.
I wish companies would have better visibility to allow them to approve DO for cloud stuff. Struggled to get the necessary compliance docs under NDA from DO
BW topic is not related to container registry, but worth mentioning as it is being discussed in this thread. Regarding the outbound data transfer pricing for a $5/month droplet, you get minimum 1TB/month free Internet-bound BW. The price of 0.01/GB kicks in only after that.
There's a really big gap between the $0.01/gb you are talking about being charged on droplets and the $0.10/gb that DigitalOcean is using on newer offerings like this and "App Platform".
The fact that somebody could put a caching proxy in front of the container registry -- on a droplet also hosted at DigitalOcean -- and have their bandwidth costs fall 10x for doing that does indeed provide further illustration of the absurdity of DigitalOcean's new approach to bandwidth pricing.
This is an insightful article. A learning for me was how the author managed to switch multiple cloud providers even while being a one man SAAS.
Kubernetes is overwhelming because of 2 things: Overload of terminology, and Distributed systems day 2 operations.
Author succeeds so well because he has a starter stack (install, CI pipeline, secure, monitor, scale) maintained as code, and it works every time.
For someone starting new, the learning curve is high. Bootstrapping is easy, but day 2 on kubernetes is hard. Benefits outweigh is learning curve imho.
Specific to DigitalOcean kubernetes API server issues, we have rolled out some resource provisioning improvements for newly created clusters very recently. Also making ongoing improvements to backend monitoring.