CatOps – Telegram
CatOps
5.09K subscribers
94 photos
5 videos
19 files
2.57K links
DevOps and other issues by Yurii Rochniak (@grem1in) - SRE @ Preply && Maksym Vlasov (@MaxymVlasov) - Engineer @ Star. Opinions on our own.

We do not post ads including event announcements. Please, do not bother us with such requests!
Download Telegram
For the #Donations Monday I would like to remind you about the UA Responders foundation that collects funds for tactical medicine, hospitals and other medical equipment.

I trust these people and I know a couple of them personally.

Thank you for supporting #Ukraine!
3
I know that many of you, folks, do not like Azure or Microsoft in general. Yet, this is one of the major cloud providers.

So, today I want to share with you a bundle of the materials to help you to get ready for Azure exams.

Ace your Microsoft certification exams bundle on Humble Bundle.

#books
👍11💩3🔥1
Avoiding Pitfalls in Go is a good article for those who just starts their journey with this language.

Yet, there are some aspects that are useful even if you use it already. Especially, if your use cases were limited to some simple code.

#programming #go
👍15🥱1
Here’s some original content, folks!

I wrote an article on how to create a workflow in GitHub Actions that is triggered with a comment.

There are some caveats with such workflows in GHA. Also, you have to do some additional tweaks to make it better from the UX perspective.

You can read the article:

- In my blog
- On Substack

Hope, you’ll enjoy it!

#github #cicd
👍10
Small fundraiser campaigns are good to cover local needs right here, right now.

Currently, my wife is raising 150k UAH to get 18 complete medical kits to the 27th battalion of the 67th brigade of the AFU.

Her brother's girlfriend's relative serves in that battalion.

Requisites for donations:

🎯 Goal: 150 000.00 ₴

🔗 Monobank Jar:
https://send.monobank.ua/jar/5zCptYx1sb

💳 Card number
5375 4112 0823 3556

Thank y'all for your support!

#donations #Ukraine
👍7
Bounded channels is a common way of limiting the concurrency in Go applications.

From this article you can learn some theory behind this approach as well as about the sync/semaphore package. I didn’t know about the latter.

#programming #go
🔥7
Amazing article about decision making

It's big but it's worth it.
TLDR version can be "try to understand why it was done in this way, before trying to abolish or replace it with something else. Otherwise, it can get worse than it was."

#culture
👍11
​​Happy Independence Day, fellas!
🎉💛💙🎉
70👍8🫡8
The drama around HashiCorp’s decision to move to Business Source License (BSL) continues. So, now we have OpenTF.

However, today I want to share with you this sane article: Why We Are Not Supporting OpenTF which pretty much resonates with my thoughts.

P.S. Here is OpenTF if you’re interested.

#hashicorp
👍184👎4
As for today, I would like to remind you about the fundraiser that my wife is running currently:

The goal is to get 150k UAH (~3700 EUR) for 18 complete medical kits to the 27th battalion of the 67th brigade of the AFU.

Requisites for donations:

🔗 Monobank Jar:
https://send.monobank.ua/jar/5zCptYx1sb

💳 Card number
5375 4112 0823 3556

Right no, a little bit more than 2/3 is there.

Thank y'all for your support!

#donations #Ukraine
👍8
Fixing a memory leak in Kubernetes with a single line of code.

I love such debug stories because you can read them almost as a thriller or a detective literature. Also, this case is very interesting indeed and it took that team a couple of months to figure it out.

A takeaway for myself:
- It‘s useful to have a dashboard (and potentially a monitor) that shows the difference of the node memory usage and the memory usage by pods.

#kubernetes #postmortem
🤣11👍1😢1
If you’re using serverless computing in your company (it for your own project) you may be interested in the State of Serverless report by DataDog.

On things that I really appreciate about this report is that they have out their methodology in the article as well.

#serverless
3
The beginning of each month is usually the time when you're being charged for all your subnoscriptions.

So, it's also a good time for me to remind you that you can subscribe to Come Back Alive - one of the biggest and well-known charity foundations in Ukraine!

#donations #Ukraine
7
Today, I would like to present to you The Dark Side of SRE.

Basically, this is a yet another article on the things that sucks at work. Things like stress from the incidents, continuous context switch, the need to use multiple technologies and thus inability to become an expert in one, and so on...

I disagree with some points made in this article. Specifically:

- Operational Treadmill:
this where Platform Engineering shines. The whole idea of PE is to switch from the reactive operational approach to the proactive
product-focused approach (OPS still exists in this paradigm, tho)

- The Limited Career Progression: I didn't get this point at all. An SRE can become a manager just as any other engineer if they wish. Obviously, being a manager requires a completely different skill set. However, this point almost sounds like the author was denied a promotion and now is sour about it.

Yet, this article has an interesting document
linked
- an instruction from Google SREs on what to expect from an SRE
position outside Google. It's hilarious, TBH. This document shows once again how inconsistent are the noscripts across the industry. Especially, when it comes to the OPS roles.

#culture #sre
👍13
I usually do not post event announcements, but there are two exceptions.

One of them is DevOps Days Ukraine! This year we have a topic of Disaster Recovery.

I'm one of the organizers of this conference, and we are going to have the next one very soon: on the 14-15th of September, with some amazing speakers from the industry.

The conference is online, so you can join from anywhere in the world! Just keep in mind that the conference is held in the Kyiv timezone.

See you there!

#event
👍12
If you have AWS Lambdas in Go, you likely know that AWS is going to deprecate the go1.x runtime and forces its users to migrate to the generic al2.provided runtime.

The premise is that the new runtime is more performant. However, here is an article that argues why this move is bad for Go users on AWS as well as goes through some caveats you may encounter during the migration.

#go #aws #serverless
👍61