136 private links
Git is hard: screwing up is easy, and figuring out how to fix your mistakes is fucking impossible. Git documentation has this chicken and egg problem where you can't search for how to get yourself out of a mess, unless you already know the name of the thing you need to know about in order to fix your problem.
So here are some bad situations I've gotten myself into, and how I eventually got myself out of them in plain english.
We had the chance to see quite a bit of clusters in our years of experience with kubernetes (both managed and unmanaged - on GCP, AWS and Azure), and we see some mistakes being repeated. No shame in that, we’ve done most of these too!
I’ll try to show the ones we see very often and talk a bit about how to fix them.
Notice the line makepdf & makedoc & openapp. Here I am are running the 3 functions in parallel. The wait command does exactly that, waiting for the previous things to finish. When everything is done, the pdf file opens. Let’s look at the timing now:
real 0m24.677s
user 0m21.669s
sys 0m1.746s
It is running ~27% faster. Only by wrapping the code in different functions.
As an extra, in bash the code is not evaluated all at once. If you edit a script while it is being executed, the script behaves differently. Wrapping it in functions solves that problem too.
A brief look at models for integrating Kubernetes clusters into existing networks.
Keynote for the GUUG FFG 2015, Stuttgart (Video: FrosCON, deutsche Sprache)
binenv will help you download, install and manage the binaries programs (a.k.a. distributions) you need in you everyday DevOps life (e.g. kubectl, helm, ...).
Think of it as a tfenv + tgenv + helmenv + ...
Now you can install your favorite utility just by typing binenv install something.
Learn fast from my years of being a container consultant and Docker implementer. Come join me for a jam-packed session of decisions you need to make and key technical factors you should know. No fluff, all practicals. Updated for 2019 and based on my 3 years of top-10 DockerCon talks.
You should show up if:
• You are planning or involved with building/using a Docker production system.
• You are thinking of using Swarm and/or Kubernetes (but not required).
• You like random 80's/90's video game trivia thrown at you.
DevOps in the Real World is far from perfect, yet we all dream of that amazing auto-healing fully-automated micro-service infrastructure that we'll have "someday." But until then, how can you really start using containers today, and what decisions do you need to make to get there?
This session is designed for practitioners who are looking for ways to get started now with Docker and container orchestration in production. This is not a Docker 101, but rather it's to help you be successful on your way to Containerizing [...]
The business case for collaborative #DevOps http://t.co/rrIIpCI4 #ibm #developerworks #rational #tivoli #ibmconnected
Collaborative DevOps - when application development meets operations http://t.co/ARI0nQFs #ibminnovate #rational #devops #tivoli
DevOps: Can this really help the Ops guru? http://t.co/8OtqGFkp #provisioning #devops #continuous #delivery #smartcloud