San Jose, CA
2019-06-10 to 2019-06-13
Description
Everyone keeps telling you that containers need orchestration, but you’re not so sure; maybe they could go for some light jazz? Or maybe serverless is here to save us from the tyranny of (virtual) machines, but meanwhile somebody’s gotta kuber some netes, and it’s likely to be you. Let’s take a walk through the cloud native landscape and talk about what’s new, what’s next, and what you need to get started with Kubernetes right now (before sentient machines have a chance to destroy us all).
Slides
Tweets
next is @bridgetkromhout !! Kube for the impatient #VelocityConf
— Smasher of DBs. First of her name. (@dbsmasher) June 13, 2019
.@bridgetkromhout walks us through the cloud native landscape and shares what’s new, what’s next, and what you need to get started with Kubernetes right now (before sentient machines have a chance to destroy us all)—now on the #VelocityConf keynote stage.
— O'Reilly Infrastructure & Ops (@OReillyInfraOps) June 13, 2019
Shout out to @abbyfuller we love you and miss you #VelocityConf
— Smasher of DBs. First of her name. (@dbsmasher) June 13, 2019
❤️ the @bridgetkromhout talk title- Kubernetes for the impatient 😂 #velocityconf pic.twitter.com/TxlBWlUAdY
— Karthik Gaekwad (@iteration1) June 13, 2019
Kube according to Babylon 5 @bridgetkromhout #VelocityConf pic.twitter.com/y0gY9bncFn
— Smasher of DBs. First of her name. (@dbsmasher) June 13, 2019
“You gotta have some service mesh obviously” @bridgetkromhout #VelocityConf
— Smasher of DBs. First of her name. (@dbsmasher) June 13, 2019
#VelocityCon @bridgetkromhout on Kubernetes for the impatient pic.twitter.com/pTNJd9LpOe
— Vallery Lancey (@vllry) June 13, 2019
First....was the colossus ... v custom built. @bridgetkromhout #VelocityConf
— Smasher of DBs. First of her name. (@dbsmasher) June 13, 2019
There’s zillions of tools available, and we need some, but not most? How do we navigate this without being an expert? #VelocityCon pic.twitter.com/rpAIVeQ9TL
— Vallery Lancey (@vllry) June 13, 2019
Thanks @bridgetkromhout you got me on slide 3 with the once in a lifetime reference 😂 pic.twitter.com/p7FJEqClpf
— Karthik Gaekwad (@iteration1) June 13, 2019
Cloud...according to XKCD @bridgetkromhout #VelocityConf pic.twitter.com/xFYkEpFYCb
— Smasher of DBs. First of her name. (@dbsmasher) June 13, 2019
“Containers are not a rel thing” @jessfraz being quoted by @bridgetkromhout #VelocityConf
— Smasher of DBs. First of her name. (@dbsmasher) June 13, 2019
“Anything you do in the Kubernetes ecosystem, you have a lot of decisions to make.” @bridgetkromhout helps navigate the @CloudNativeFdn cloud native trail map. #VelocityConf pic.twitter.com/ktlAAQXDnz
— Bryan Friedman (@bryanfriedman) June 13, 2019
Step 1: only solve problems that you actually have. pic.twitter.com/XFaRZ7ANW8
— Vallery Lancey (@vllry) June 13, 2019
Now @bridgetkromhout is up to talk about Kubernetes for the Impatient!#VelocityConf pic.twitter.com/NOR5rgN82b
— Tom Leaman (@tleam) June 13, 2019
Near the beginning of time:
— Tom Leaman (@tleam) June 13, 2019
We did a lot of code breaking with very purpose built machines.
Now:
We are now at a point where we use highly generalized hardware and abstractions that minimize our need for deep interaction (like managing data center temp)#VelocitConf pic.twitter.com/T0FymjGrHI
💯 irl container repeatable @bridgetkromhout #velocityConf pic.twitter.com/xa7MViyEjM
— Karthik Gaekwad (@iteration1) June 13, 2019
You dont say..... 😂#VelocityConf pic.twitter.com/wqXNM6oi4e
— Smasher of DBs. First of her name. (@dbsmasher) June 13, 2019
Containers solve a problem: repeatable deployment.
— Vallery Lancey (@vllry) June 13, 2019
They don’t solve everything, and they give us new work and fun failure modes. #VelocityCon pic.twitter.com/nKHKRy4lou
"What problems do you have?" @bridgetkromhout pic.twitter.com/L9blpgnwtY
— Mike Serra (@packet_guardian) June 13, 2019
“But I am not even kubering any netes yet!” @bridgetkromhout #VelocityConf
— Smasher of DBs. First of her name. (@dbsmasher) June 13, 2019
Containers don’t solve all problems. @bridgetkromhout delivers a keynote on #k8s #VelocityConf https://t.co/wIGmebS6Qv pic.twitter.com/EFFKCrMTIl
— Alex Elman (@_pkill) June 13, 2019
.@mickeyboxell favorite @CloudNativeFdn tool- @HelmPack. We also use Helm to build and deploy artifacts for @OracleIaaS Container Engine. #velocityConf @bridgetkromhout pic.twitter.com/DiOJkxdmcR
— Karthik Gaekwad (@iteration1) June 13, 2019
Practical advice 💯 use something that confronts with the SMI spec for service mesh @bridgetkromhout #velocityConf
— Karthik Gaekwad (@iteration1) June 13, 2019
Late to the kubernetes party? Lucky you! The tools are better now.@bridgetkromhout #velocityConf pic.twitter.com/HnuQRGkzFa
— Jessica Joy Kerr (@jessitron) June 13, 2019
Kubernetes has been our for 5 years, but you’re not late to the party. The tools keep better better with time. Bridget highlights CNAB and Porter as examples of easy ways to define workloads. #VelocityCon pic.twitter.com/eKsjiCO0q6
— Vallery Lancey (@vllry) June 13, 2019
Thanks to the wonderful @bridgetkromhout for closing today’s #VelocitConf keynotes and a million apologies to @everettharper for not getting one... I was so mesmerized by your excellent talk that I forgot to step away and take one 😢 Encore? pic.twitter.com/O3PcaiiD7v
— Ines Sombra (@randommood) June 13, 2019
Still think OPA is still in early stages but might prove to be a really great answer for policy definition for your cloudnative infra! #velocityConf @bridgetkromhout pic.twitter.com/uwYj1aPAuk
— Karthik Gaekwad (@iteration1) June 13, 2019
Consisten development, repeatable deployment @bridgetkromhout keeping it real ! #helm #porter #cnab #servicemeshintetface focus learn choose #openpolicyagent #VelocityConf pic.twitter.com/t2LKf4R90Y
— Shikha Jain (@be_shikha) June 13, 2019
.....yup.... #VelocityConf pic.twitter.com/qEfKu9bJ07
— Smasher of DBs. First of her name. (@dbsmasher) June 13, 2019
Please join @CloudNativeFdn SIGs- we all need a lot of help to make cloudnative successful. It’s kind of on us if it fails #velocityConf @bridgetkromhout
— Karthik Gaekwad (@iteration1) June 13, 2019
How do we decide what project/tool is right for us? Perhaps look at Github and the project health. Are issues being addressed? Is development open? Is there a roadmap and are things on track?#velocityConf
— Vallery Lancey (@vllry) June 13, 2019
“Process is scar tissue from past experience” @bridgetkromhout #VelocityConf
— Smasher of DBs. First of her name. (@dbsmasher) June 13, 2019
“We’re building a dystopia”
— Vallery Lancey (@vllry) June 13, 2019
“It’s important that we use this reality-shaping power for good”#VelocityConf
Shout out to nethack from @bridgetkromhout in her keynote 😃
— boo radley : 20xx (@boo_radley) June 13, 2019
“Process is scar tissue around past failures.”@bridgetkromhout #VelocityConf
— Heidi is Doing A Think about tech (@wiredferret) June 13, 2019
Overheard from @bridgetkromhout at #VelocityConf: "Process is scar tissue for past failures."
— Gordon Myers (@soapergem) June 13, 2019
"Process is scar tissue for past failure" - @bridgetkromhout #VelocityConf
— Devin Lafreniere (@devsoftweb) June 13, 2019
Thanks @bridgetkromhout!!!! Great talk #VelocityConf
— Karthik Gaekwad (@iteration1) June 13, 2019
"Process is scar tissue from past failures..." @bridgetkromhout #velocityconf
— wirehead (@wirehead) June 13, 2019
Choose tech projects and tools consciously. Use this reality-shaping power for good. Look at project health on GitHub. @bridgetkromhout at #VelocityConf pic.twitter.com/V8ouSQ9yAo
— ginablaber (@ginablaber) June 13, 2019
If Microsoft can brag that Azure is majority Linux, your enterprise can change too.@bridgetkromhout #velocityConf pic.twitter.com/s80JqzlO3q
— Jessica Joy Kerr (@jessitron) June 13, 2019
The “we’ve always done it this way” narrative doesn’t work, and we should push back against it. As @bridgetkromhout described it: “process is scar tissue from past failures” #VelocityConf pic.twitter.com/Unb0fPdLJH
— Michael Villaseñor (@mvillatech) June 13, 2019
Bummed that I couldn’t be there to watch @bridgetkromhout’s #VelocityConf keynote this morning. https://t.co/AV701NONXh
— Joe Laha (@joelaha) June 13, 2019
Great #VelocityConf keynote by @bridgetkromhout on a framework on how to make decisions around your usage of #Kubernetes and aspects of it you need to prioritize, etc. pic.twitter.com/30ufV4zq0X
— Noureen Syed (@NoureenSyed) June 13, 2019
@bridgetkromhout quote: “process is scar tissue from past failures”. #perspective #truth #VelocityConf— Mick (@mickelback00) June 13, 2019
1⃣1⃣ Then @bridgetkromhout was back for keynote 2⃣ on #k8s for the impatient! This really made us feel seen! 😅https://t.co/qACCDdivcB
— DataStax Developers (@DataStaxDevs) June 13, 2019