I don't think we use any Alpha features, I know there are a couple Beta APIs from Kube we use, but we would be using those no matter where we ran our Kube deployment. We use fluentd for our log collection and Prometheus for metrics and alerting combined with Elastalert. So don't have any experience with Stackdriver.
Why is working with SSL certs an issue? We use the NGINX Ingress with cert-manager and have yet to have an issue. We only have a couple domains pointed at the cluster though, not sure if thats where your issue comes from. The two just worked though with very little tweaking.
Average availability for the year across those environments is 99.99%.
I'd say that's decent enough to use.
Their support is hilariously bad at times, though.
I find it a bit ironic that the mobile and web side of the house are pushing very heavily for IPv6 adoption and yet they expect their cloud customers not to need it.
That was my experience when we needed something.
Dont get me started on docs and operations.
Eg: Using Azure we found out the hard way that the Firewall was cutting connections after 5m of inactivity. Changing that setting? Their docs are wrong, stack overflow kindof helps, but to fix it we had to use windows based tooling in a vm since their linux based stuff didnt work.
I know this will happen sooner or later with anybody, but on average the experience with GCP was superb.
I do agree re: certs. That is the only thing I really hate, doing LE when they could run this for you. But they will launch an SSL solutio since they have one now for AppEngine.
Could you elaborate on this? Which firewall is this? I remember something similar with their load balancer but I thought this was fixed years ago. Might you have some link to the issue? Thanks.
StackDriver error reporting is a lite product intended mostly for folks with small applications on AppEngine.
There is a recent post by Corey Quinn entitled CloudWatch Is of the Devil, but I Must Use It discussing the extremely poor usability of Amazon CloudWatch [0]. Here’s another story about the general weirdness of the product [1]
I would strongly recommend using a dedicated exception tracker like Sentry.io, they have an excellent full featured product at a extremely reasonable price.
GCP has clearly documented Platform Launch stages for Alpha, Beta, and General Availability [2].
The Kubernetes project itself follows the same definition for these identifiers as GCP.
Specifically Beta is considered to be acceptable for most production use-cases, but it is not guaranteed that the API will remain backwards compatible.
So if you’re running the majority of cloud services, beta is fine. If you’re running a system that will cause permanent harm to humans, don’t use beta.
One last note, GCP has just released a fully managed certificate product for their global load balancer. There is fully integrated Kubernetes support which has not yet been announced formally [3].
Certificates for Kubernetes on Amazon are less integrated than the above. There’s several options, it’s not clear without extensive research and testing what the tradeoffs are, and in the end it turns out that there is not an officially supported Amazon option.
[0] https://www.linuxjournal.com/content/cloudwatch-devil-i-must... [1] https://www.circonus.com/2016/10/no-fixed-glitch/ [2]https://cloud.google.com/terms/launch-stages [3] https://github.com/GoogleCloudPlatform/gke-managed-certs
Leader in k8s? Not for production. I defy you to do a gcp gke deployment without using beta or alpha features (that specifically say don’t use this for production). Stackdriver error reporting springs to mind. And working with SSL certs/let’s encrypt is a close second.
If you want a couple more peeves for your list how about documentation? I regularly find documentation heavy on theory light on specifics.
GCP is my favorite thing that is almost good enough to use. I’m hoping the change of leadership actually improves things. GCP could stand to re-focus on a “customer first” philosophy.