$ docker build . -tag gcr.io/google-samples/hello-app:1.0
$ docker push gcr.io/google-samples/hello-app:1.0
$ kubectl run hello-server --image gcr.io/google-samples/hello-app:1.0 --port 8080
$ kubectl expose deployment hello-server --type "LoadBalancer"
where the Dockerfile content is: FROM golang:1.8-alpine
ADD . /go/src/hello-app
RUN go install hello-app
FROM alpine:latest
COPY --from=0 /go/bin/hello-app .
ENV PORT 8080
CMD ["./hello-app"]
https://cloud.google.com/kubernetes-engine/docs/quickstarthttps://github.com/GoogleCloudPlatform/kubernetes-engine-sam...
I'm not saying that is a bad thing by itself, but there definitely is huge amount of added complexity behind the scenes.
To the best of my exposure, Kubernetes is a well engineered system.
You can try to go cross-country with either of them. One was engineered to survive extreme environments, protect you from the elements, and move really fast. The other was engineered to leave you exposed, operate in a moderate climate, and go much slower.
If you have problems with the former, it's time to call the technicians. If you have problems with the latter, you might fix it yourself with a pocket screwdriver.
https://docs.aws.amazon.com/codedeploy/latest/userguide/gett...
Distelli (now Puppet Pipelines) too:
https://www.youtube.com/watch?v=ZZlYADohS4Q
And then there are the PaaS options like Heroku, Beanstalk, AppEngine, Lambda, Serverless, and Apex.
That was my point. I wanted to point out that while some people have only/first heard about failover in the context of kubernetes, it is not something that is specific to kubernetes or even the problem that kubernetes was build to solve.
Of course it is not designed to be a failover solution specifically and using it (exclusively) as such would be ill-advised; I was just trying to be diplomatic while pointing that out.
But the parent's comment is missing the point. K8s is not for failover. K8s is literally just a giant monolith of microservices for running microservices. It's not intended to provide failover for non-microservices, it's intended only to run microservices, and as a side-effect of needing to be able to scale them, it inherently provides some failover mechanisms.