HashiCorp announced a general availability of the Terraform Cloud Operator, which allows you abstract the infrastructure as Kubernetes resources.

In order to use it you have to have Terraform Cloud subnoscription, so this is might be not that important news per se. However, this shows that Kubernetes is a platform on its own and people alongside with well-known companies acknowledge that. Also, managing your insfrastructure from within a Kubernetes cluster doesn't seem like a wrong order of operations. Such things like Terraform Cloud Operator only proves that.

BTW, you can write-up your use case for potential Terraform OSS Operator in this issue

#kubernetes #hashicorp

Навігація:
00:00 - Вступне слово
02:04 - Соц. активність в університеті
09:31 - Журнал "КПІшник" і секс-карта КПІ
14:05 - Створення DevOps-ком'юніті
20:50 - Як ростити спільноту без реклами
27:20 - Мовне питання в інтернаціональних спільнотах
32:18 - Токсік і як з ним боротись
36:50 - Як своє ком'юніті впливає на кар'єру
45:26 - Монетизація своєї спільноти
49:35 - Hashicorp User Group
53:54 - Як зробити свою HUG
59:30- Конференція DevOps Days

Дивитись на YouTube: https://youtu.be/YiqNuZLbzlg

Спілкуємось зі спікерами тут: https://news.1rj.ru/str/dislike_chat
Анонси майбутніх подій тут: https://news.1rj.ru/str/dislike_unsubscribe
Слухати на вашій улюбленій подкаст-платформі: https://anchor.fm/dislike-unsubscribe

CatOps: https://news.1rj.ru/str/catops
HUG Kyiv: https://www.meetup.com/Kyiv-HashiCorp-User-Group/
DevOps Days Kyiv: https://devopsdays.com.ua/

Argo Workflows v3.0 is out!

An article provides some history of Argo development as well as new features of the v3.0 release:

- New APIs for Argo Events
- Controller High-Availability
- Key-only artifacts make it easier to perform map-reduce operations
- Moving the repository. Now it's argo-workflows, not just argo, which caused a lot of confusion with ArgoCD
- Go modules support

#kubernetes #argo #cicd

We are happy to announce that Call For Papers for Lightning Talks is now open for DevOps Days Kyiv 2021! (we because, I'm a part of organizational committee as well, hehe)

Lightning Talk is a 5 minute talk without Q&A, where you can share any topic you're passinate about, share your thoughts and knowledge, and inspire others.

CFP close on the 15th of March 2021

#event

Статья о том как устроена DynamoDB в амазон. Очень наглядный пример архитектуры БД широкого назначения. https://medium.com/@uditsharma/internals-of-dynamodb-b3b7912256ae

I know that this article is not about DevOps or infrastructure engineering, pipelines, whatsoever.

But I got some genuine satisfaction reading this.

Parse JSON like a Rockstar!

P.S. PC players of GTA online may appreciate this post anyways

​​Important math

UPD from our subscribers: a handy website to convert SLAs

Обновите свой git, пжалста

https://www.openwall.com/lists/oss-security/2021/03/09/3

#git #exploit

Some good practices on how to tag your AWS infrastructure for better cost management and compliance audits.

As someone, who works with AWS on the daily basis, I can say that this article is pretty useful. We are trying to create a similar account structure / tagging in the company I work for as well.

This article sums up ideas regarding proper resources tagging and also AWS account layout, which can help you to organize and track your assets better.

It recommends some third-party tools for cost audits as well.

#aws

Basic practices for optimizing read and write performance in PostgreSQL.

A long read about the factors that affect PostgreSQL performance as well as some insights regarding the internals.

#postgresql #db

An article on how to scale Celery workers in Kubernetes based on RabbitMQ queue depth.

Basically, this is an example of how to use custom metrics for scaling. They were using KEDA to collect those metrics. So, it may also be interesting to those who want to know more about KEDA itself.

#kubernetes

"Quick read" by John Arundel called Writing slower Go programs. Actually, this can relate not only to Go.

The idea is that you'd better optimize your code for readability, brevity, and simplicity to understand; rather than speed. Unless, you're working in an industry that requires blazing fast response times or works under shortage of resources. Such as game development, IoT, network equipment and so on. However, if you do work in such an industry, you likely know, what's you're doing.

#go #programming

At some point senior engineers may ask themselves: where do grow next? Is being a manager an only way to go?

That's not quite true. StaffEng has some guides as well as personal stories of people who grew beyond a Senior noscript, while still staying on the tech track.

#culture

Some best practices for GKE networking by, well, Google.

As was said in one book:unless you've actually done the work, you're in no position to encode it as a best practice.

#gcp #gke #kubernetes #networking

A new article by Julia Evans Get better at programming by learning how things work.

It’s impossible for a single person to know everything. Especially, in such complicated systems as we have in modern IT. And it’s fine, you can still do a good job.

However, you can become even better engineer by getting down to the nature of things. Especially, when you have a tricky bug to chase.

Here are some tips from Julia on how to get there:
- Just learning a few facts can help a lot
- Connect new facts to information you already know
- Ask yes/no questions
- Googling is a skill

#culture

This is not really a DevOps-ish article. However, salary topic is something that ususally interesting to everyone.

Here is an outcome of a personal research regarding salaries in the Netherlands and Europe. Personal in this case means that this research was primary driven by a private person.

I'm not familiar with dutch market personally, but overall the ideas described in this blog post are relevant to Germany as well.

Of course, things are quite different for non-EU/non-US countries. Especially, Post-soviet countries. However, it's a huge benefit that as an IT specialist you can compete not only on the local market, but also globally.

<for our russian-speaking subscribers>

Many thanks to “Потестим в проде” podcast for having me as a guest!

If you want to listen to me speaking about the common problems in devops-ish terminology, differences between IT market in Kyiv and Berlin, and if you need Kubernetes to run your personal blog, you can find the recordings on:

- YouTube
- Apple Podcasts
- Google Podcasts

Podcast is in Russian.

#slides #podcast

Thinking of starting a new open source project? Or your company wants to open some internal work?

At some point you'll need to start thinking about the licenses. Taking care of it earlier helps you to avoid problems like the recent issue of Rails and mimemagic

However, you're an engineer and not a lawyer, right? Here are just a couple of resources, which can help you navigate through the differences of the Open Source licenses.

- Choose an open source license - very brief and clear guide for beginners
- TLDRLegal - another quick start guide, but contains more types of licenses

#legal #foss

​​strace is a very old yet popular tool for Linux troubleshooting. Moreover, on many Ops interviews an interviewer is only satisfied when a candidate mentiones strace during the troubleshooting questions section. And of course, there are more bonus points for mentioning that strace shows system calls of a given process(es) and their arguments and return values.

Although, what are we trying to solve with it? And when to use it?

Julia Evans collected 9 common categories of problems which people use to solve with strace:

- where’s the config file?
- what other files does this program depend on?
- why is this program hanging?
- is this program stuck?
- why is this program slow?
- hidden permissions errors
- what command line arguments are being used?
- why is this network connection failing?
- why does this program succeed when run one way and fail when run in another way?

P.S. She also has a free webzine on how strace works!

Ten commandments of Go - a set of advices for better Go code.

Some of them are applicable not only for Go. Especially, number 10.

P.S. Even if your content is all right, try to avoid any religious analogies. That's just silly

#go #programming