![lynn [they]](https://pbs.twimg.com/profile_images/1223460457068949505/qqfjH_c2_normal.jpg)
My 2nd one is the "Rule of Garrison" - sometimes you don't need containers or k8s, and that's ok.
Prikaži ovu nit
I'm collecting myths about k8s and containers -- what are your favorites? I'm going with "The world is still running on PHP and Java, ain't no one rewriting all of that in golang" as my first one. Keep it light and snarky. :p
-
-
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
K8s isn’t for databases. Or Elastic Sesch. Or Splunk.
-
Ooh interesting, I was going to go with "You don't need to put your databases in k8s, they've been working fine for decades, find lower hanging fruit."
- Još 1 odgovor
Novi razgovor -
-
-
k8s is the panacea . Fact is you need deep linux knowledge to operate and run k8s
-
One thing I did want to add is how deeply knowledgeable about the kernel and userspace k8s engineers tend to be. (And kind of have to be). That whole "moving up the stack" feels overblown, some of the most knowledgeable kernel people I've ever seen work on k8s!
- Još 2 druga odgovora
Novi razgovor -
-
-
The majority of Dockerfiles is: FROM ubuntu:latest COPY /git/monolith /monolith ENTRYPOINT ["/monolith"]
-
Nobody knows how to write a Deployment from scratch. All of the extant ones are all hacked up copies from whatever is the first result in "kubectl get deployment"
- Još 1 odgovor
Novi razgovor -
-
-
"It's secure by default!"
- Kraj razgovora
Novi razgovor -
-
-
Monolith = bad Containers = no longer my problem and always better than monolith. What's that I hear
? 40GB container, sounds great! 
#DevOps
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.