Five Months of Kubernetes

We&#x27;ve been deploying Kubernetes for clients since, well, 1.0 (very recently) and have nothing but great things to say about it. If you want something approximating a Heroku-like experience but in your own environment (AWS, GKE, or even on-prem) K8s is a super awesome way to get there. Sure, like anything it&#x27;s got some rough edges that you&#x27;ll get cut on, but it improves every 3 months. :D<p>Big kudos to the k8ts team at Goog, and all the other contributors!

&gt; Kubernetes does not offer a clean solution for a number of problems you might face, such as stateful applications.<p>petset is a solution for stateful applications [1]. It&#x27;s still in alpha though. I heard rumours that it will enter beta in about 3 months.<p>1. <a href="http:&#x2F;&#x2F;kubernetes.io&#x2F;docs&#x2F;user-guide&#x2F;petset&#x2F;" rel="nofollow">http:&#x2F;&#x2F;kubernetes.io&#x2F;docs&#x2F;user-guide&#x2F;petset&#x2F;</a>

&gt; In general, Elastic Beanstalk works fine and has a very gentle learning curve; it didn’t take long for all teams to start using it for their projects.<p>This is one of the most pressing issues I tend to evaluate on infrastructures. I&#x27;m curious to see a few months down the line your opinion on how the dev teams embraced Kubernetes&#x27; setups independently or if they kept depending on a dev-ops team to do so.

I&#x27;ve been using ecs-cli for my container deployments on AWS <a href="https:&#x2F;&#x2F;github.com&#x2F;kaihendry&#x2F;count" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;kaihendry&#x2F;count</a><p>I wonder if I should try kubernetes. It seems a lot more complex but the tooling looks better maintained.

I&#x27;d be very interested to see the code for the AWS Lambda functions mentioned—specifically the one about ephemeral development environments based on open PRs. We&#x27;re building something similar at InQuicker and it&#x27;d be great to see how other people are approaching it.

Great article, very easy to read and tons of useful info. Love seeing fellow Brazilians giving it a go.

&gt; First, we created one DNS record for each service (each initially pointing to the legacy deployment in Elastic Beanstalk) and made sure that all services referenced each other via this DNS. Then, it was just a matter of changing those DNS records to point the corresponding Kubernetes-managed load balancers.<p>If anyone could explain this, does this mean - the services still are being accessed from Public IP or does Kubernetes managed load balancers are Private IPs that can the individual nodes know about ?

Did you try ECS as an alternative to Elastic Beanstalk? Would be interested in hearing your pros and cons for ECS vs Kubernetes on EC2.

I am very close to giving &quot;k8s&quot; a try.<p>Despite a lot of work on trying to figure out how to get us up on docker for CI workloads - the ecosystem is very confusing in terms of docker-cloud, docker-compose vs. docker-machine (on linux vs. osx) etc.