#Kubernetes takeover BEGINS! Welcome to our first host, @thockin! He’ll be here to talk about #K8s and answer your burning questions for the next two hours 
#K8s5pic.twitter.com/YuAQ63JVqt
Google Cloud. Kubernetes Steering Committee emeritus, K8s SIG Architecture co-Chair emeritus, CNCF TOC member emeritus
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Add this Tweet to your website by copying the code below. Learn more
Add this video to your website by copying the code below. Learn more
By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.
| Country | Code | For customers of |
|---|---|---|
| United States | 40404 | (any) |
| Canada | 21212 | (any) |
| United Kingdom | 86444 | Vodafone, Orange, 3, O2 |
| Brazil | 40404 | Nextel, TIM |
| Haiti | 40404 | Digicel, Voila |
| Ireland | 51210 | Vodafone, O2 |
| India | 53000 | Bharti Airtel, Videocon, Reliance |
| Indonesia | 89887 | AXIS, 3, Telkomsel, Indosat, XL Axiata |
| Italy | 4880804 | Wind |
| 3424486444 | Vodafone | |
| » See SMS short codes for other countries | ||
This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.
Hover over the profile pic and click the Following button to unfollow any account.
When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.
The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.
Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.
Get instant insight into what people are talking about now.
Follow more accounts to get instant updates about topics you care about.
See the latest conversations about any topic instantly.
Catch up instantly on the best stories happening as they unfold.
#Kubernetes takeover BEGINS! Welcome to our first host, @thockin! He’ll be here to talk about #K8s and answer your burning questions for the next two hours 
#K8s5pic.twitter.com/YuAQ63JVqt
I'm not sure if this is your area of expertise, but what do you think is an effective way of running stuff on k8s? We landed on gitops, using tools that apply resources to the cluster and update manifests when new image is pushed, but I'm not sure if it's the right way to go.
I am a big fan of #gitops. I am less of a fan of automatic pushes to prod when artifacts change. Having your app configs checked into git, whether naked or templatized, or kustomized, is so obvious to me that I can't believe some people don't....
But updates to prod should be intentional and probably proceed no faster than a human can stop them. Dev/test is another conversation, and automagic stuff is more appropriate there.
That was another thing I wanted to ask, but it didn't fit in - would you recommend having a completely separate cluster for production?
This is a tradeoff (surprise!). You get better isolation and blast radius, but you get lower efficiency (generally). Only you can decide how much those extras are worth to you, both in terms of literal machines cost and in terms of human cost (complexity, docs, admins). -TH
My answer would be yes: separate clusters for prod.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.