Amazon has nothing in the category of exception tracking.
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.
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