Mateusz Gozdek
1.2K posts

Mateusz Gozdek
@_invidian
Linux and Kubernetes expert, member of OSS community, Go developer, food lover, finds bugs, yak shaver, TDD advocate, Senior Software Engineer at @microsoft
Berlin, Germany Присоединился Nisan 2019
178 Подписки156 Подписчики

Ever wondered what it's like working in the field of Mineralogy? Here's a handy one-panel guide to give you some idea #Mineralogy #Geology

English



Well, annual check-in:
- ✅New cluster provisioning works
- ✅Backups and restoration works
- ✅Updated to latest K8s 1.28
- ✅Updated all components to latest versions
And of course I spent plenty of time debugging some minor issues, like last year!
Mateusz Gozdek@_invidian
Well, annual check-in: - ✅New cluster provisioning works - ✅Backups and restoration works - ✅Updated to latest K8s 1.25 And of course I spent plenty of time debugging some minor issues.
English

@ibuildthecloud Define simpler :) I'm genuinely curious about your take at it!
English

@LinuxHandbook Interesting! But this "glboal" typo in the infographics is really bad... 😁
English

Rome was not built in a day, but grep was (sort of) 😎
The origin story behind the creation of grep utility is fascinating.
The co-creator of the UNIX operating system, Ken Thompson, developed grep 'overnight'.
Actually, he had a personal tool for searching for text in files.
His department head Doug McIlroy came to him and said, "You know it would be really great if we could look for things in files".
"I'll think about it overnight", said Thompson.
He went back home and modified the code in his tool to fix bugs. Took him an hour at most.
The next day, he presented it to McIlroy and he exclaimed,
"This is exactly what I wanted"
And the rest is history.
If you are wondering why the utility is called grep and not search, there is perfectly good logic behind it 👇

English

@dylanbeattie @StickerApp Sounds like a good task for new ChatGPT 🤔
English

The list of things I don’t know seems to keep growing.
Here is an interesting thing I learned the hard way this past week.
My docker server which I use for testing is 10 years old, work decided to give me a brand new server for the daily tests. I switched it, but for my surprise the test ran SLOWER. 10% slower. Odd this new server is so much juicer more RAM and cores how is it slower.
doing a docker inspect on my old and new container I found out the old container (docker 20.10.7 ) has a property called “CgroupnsMode” set to “Host”. While my new container (docker 24.0.5) has same property set as “private”
started googling and sure enough there this whole thing cgroup v1 and v2. I know cgroups are used to control resources but that is pretty much where my knowledge ends haha.
but essentially in the old docker, all containers are in the same control group as the container runtime so they all share the resources and its as much as you gave docker.
in the new one each container gets its OWN control group.
so I switched the default to host and boom performance became way better. then the old machine, its like in a Blue Lock Anime when Chigiri breaks his shackles and unlocks his power.
Now questions that I trying to figure out is what exactly are those limits set on each of the private control groups. Because clearly something was holding back the processes.

English











