When one admin makes voice chats online, another - makes voice chats offline
HUG Kyiv #12: CICD, GitOps, Terraform!
What:
- The Magic of CICD approaches and infrastructure building
- GitOps strategies for Terraform
- Terraform bad practices. What I've learned from 2 years working that way.
Who:
- Oleg Chulanov @ Diebold Nixdorf
- Igor Rodionov @ CloudPosse
- Konstantin Lazarenko @ Star
When: Saturday 28th August, 18:00 (Kyiv TZ)
Where: Officially it's Kyiv, details in meetup. + Online
Languages: Russian, Ukrainian
Please, register here
#event
HUG Kyiv #12: CICD, GitOps, Terraform!
What:
- The Magic of CICD approaches and infrastructure building
- GitOps strategies for Terraform
- Terraform bad practices. What I've learned from 2 years working that way.
Who:
- Oleg Chulanov @ Diebold Nixdorf
- Igor Rodionov @ CloudPosse
- Konstantin Lazarenko @ Star
When: Saturday 28th August, 18:00 (Kyiv TZ)
Where: Officially it's Kyiv, details in meetup. + Online
Languages: Russian, Ukrainian
Please, register here
#event
Not long ago, I wrote about the rise of Kubernetes distributions. So, take a few more:
* Airship - a tool for creating platforms based on Kubernetes, which is backed by some big tech.
* KubeZero - opinionated zero downtime Kubernetes platform
* Cluster.dev - and of course an opinionated Kubernetes cluster setup tool by SHALB
Hope, you can find something useful for you. Or you can build your own opinionated setup tooling, of course.
Because people need platforms, not clusters!
#kubernetes
* Airship - a tool for creating platforms based on Kubernetes, which is backed by some big tech.
* KubeZero - opinionated zero downtime Kubernetes platform
* Cluster.dev - and of course an opinionated Kubernetes cluster setup tool by SHALB
Hope, you can find something useful for you. Or you can build your own opinionated setup tooling, of course.
Because people need platforms, not clusters!
#kubernetes
www.airshipit.org
Airship: Automated clusters Deployment for Open Source Infrastructure
Airship is a collection of loosely coupled but interoperable open source tools that declaratively automate cloud provisioning.
All of us read a lot these days. Documentation, articles, books, how-tos, even the CatOps posts. We need to consume and prcess enormous amounts of information in order to just stay afloat.
So, is there a way to make it better? How can one keep up with the flow?
How to Remember What You Read provides some practical advices on how to improve the quality of the reading process as well as… well, remember what you read.
Although, it’s not at all a technical article, this content may be beneficial for everyone, who’s going through the piles of tech literature. I would even argue that that tese advices might be more valuable in this case. Since, professional literature is usually more data dence than fiction.
If you want to see just a brief summary of this article, let it be this. Quote:
But if you only remember six things after reading this article, it should be the following truths about reading:
1. Quality matters more than quantity. If you read one book a month but fully appreciate and absorb it, you’ll be better off than someone who skims half the library without paying attention.
2. Speed-reading is bullshit. Getting the rough gist and absorbing the lessons are two different things. Confuse them at your peril.
3. Book summary services miss the point. A lot of companies charge ridiculous prices for access to vague summaries bearing only the faintest resemblance to anything in the book. Summaries can be a useful jumping-off point to explore your curiosity, but you cannot learn from them the way you can from the original text.
4. Fancy apps and tools are not needed. A notebook, index cards, and a pen will do just fine.
5. We shouldn’t read stuff we find boring. Life is far too short.
6. Finishing the book is optional. You should start a lot of books and only finish a few of them.
#books #culture
So, is there a way to make it better? How can one keep up with the flow?
How to Remember What You Read provides some practical advices on how to improve the quality of the reading process as well as… well, remember what you read.
Although, it’s not at all a technical article, this content may be beneficial for everyone, who’s going through the piles of tech literature. I would even argue that that tese advices might be more valuable in this case. Since, professional literature is usually more data dence than fiction.
If you want to see just a brief summary of this article, let it be this. Quote:
But if you only remember six things after reading this article, it should be the following truths about reading:
1. Quality matters more than quantity. If you read one book a month but fully appreciate and absorb it, you’ll be better off than someone who skims half the library without paying attention.
2. Speed-reading is bullshit. Getting the rough gist and absorbing the lessons are two different things. Confuse them at your peril.
3. Book summary services miss the point. A lot of companies charge ridiculous prices for access to vague summaries bearing only the faintest resemblance to anything in the book. Summaries can be a useful jumping-off point to explore your curiosity, but you cannot learn from them the way you can from the original text.
4. Fancy apps and tools are not needed. A notebook, index cards, and a pen will do just fine.
5. We shouldn’t read stuff we find boring. Life is far too short.
6. Finishing the book is optional. You should start a lot of books and only finish a few of them.
#books #culture
Farnam Street
How to Remember What You Read
The benefits of reading are negated if you forget remember what you read. This article discusses a tested system to increase retention. Learn how to use active reading to remember more from books.
Humble Bundle has a new portion of O'Reilly's Linux books
As usual, you can pay €1, ~€9, or ~€15 to unlock books about useful Linux utilities and other related stuff. The bundle is valid till the 12th of September. It includes:
- Bash Cookbook
- Linux Observability with BPF
- Mastering Regular Expressions
- Effective awk Programming
- Linux Pocket Guide
- Cybersecurity Ops with bash
- Learning the Bash Shell
- Learning the vi and Vim Editors
- Linux in a Nutshell
- sed & awk
- Linux System Programming
- Classic Shell Scripting
- Linux Device Drivers
- Introducing Regular Expressions
- grep Pocket Reference
- Unix Power Tools
#books
As usual, you can pay €1, ~€9, or ~€15 to unlock books about useful Linux utilities and other related stuff. The bundle is valid till the 12th of September. It includes:
- Bash Cookbook
- Linux Observability with BPF
- Mastering Regular Expressions
- Effective awk Programming
- Linux Pocket Guide
- Cybersecurity Ops with bash
- Learning the Bash Shell
- Learning the vi and Vim Editors
- Linux in a Nutshell
- sed & awk
- Linux System Programming
- Classic Shell Scripting
- Linux Device Drivers
- Introducing Regular Expressions
- grep Pocket Reference
- Unix Power Tools
#books
Humble Bundle
Humble Book Bundle: Unix & Linux by O'Reilly
O’Reilly wants to make you a Unix and Linux wizard, with books like bash Cookbook & Linux Observability with BPF. Pay what you want & support charity!
Continuing the topic of Linux utilities, here is a good guide about
In nutshell,
#toolz
xargs utility.In nutshell,
xargs allows you to work with outputs provided by another program. So, you can think of many applications of it. My favorite one is that xargs has a -P flag, which allows you to parallel processing of the outputs. So, it can be more optimal than running a for loop in some occasions.#toolz
HUG Kyiv #12: CICD, GitOps, Terraform tommorow!
Program:
- Oleg Chulanov: The Magic of CICD approaches and infrastructure building rus
- Igor Rodionov: GitOps strategies for Terraform rus
- Konstantin Lazarenko: Terraform bad practices. What I've learned from 2 years working that way. ukr
Will be 28th August, 18:00 (Kyiv TZ) in Kyiv and YouTube
#event
Program:
- Oleg Chulanov: The Magic of CICD approaches and infrastructure building rus
- Igor Rodionov: GitOps strategies for Terraform rus
- Konstantin Lazarenko: Terraform bad practices. What I've learned from 2 years working that way. ukr
Will be 28th August, 18:00 (Kyiv TZ) in Kyiv and YouTube
#event
CNCF is creating a new working group around "Cooperative Delivery".
Here is a part of the problem statement this group is trying to address:
In most app-delivery scenarios, the packaging format and delivery mechanism of the application artifacts are targeted, but not necessarily the app's infrastructure dependencies such as data stores and message queues. That is, application and infrastructure delivery are not coordinated. Often, applications are heavily dependent on infrastructure resources that are not directly linked to a specific deployment, and therefore problems with non-existing infrastructure resources might cause deployments to fail. In addition to this, the application and infrastructure lifecycles are not synchronized, creating additional complexity and challenges when delivering workloads.
The goal of this group is not to provide a definitive solution, rather gather the information in the industry on how people are doing "cooperative delivery". Which trends are there. Are there any emerging approaches, etc.
It'll be very interesting to see their findings. Struggles with application bundling is something I encounter personally and I believe a lot of other engineers do.
#culture #cncf
Here is a part of the problem statement this group is trying to address:
In most app-delivery scenarios, the packaging format and delivery mechanism of the application artifacts are targeted, but not necessarily the app's infrastructure dependencies such as data stores and message queues. That is, application and infrastructure delivery are not coordinated. Often, applications are heavily dependent on infrastructure resources that are not directly linked to a specific deployment, and therefore problems with non-existing infrastructure resources might cause deployments to fail. In addition to this, the application and infrastructure lifecycles are not synchronized, creating additional complexity and challenges when delivering workloads.
The goal of this group is not to provide a definitive solution, rather gather the information in the industry on how people are doing "cooperative delivery". Which trends are there. Are there any emerging approaches, etc.
It'll be very interesting to see their findings. Struggles with application bundling is something I encounter personally and I believe a lot of other engineers do.
#culture #cncf
Google Docs
Cooperative Delivery WG - Charter
Cooperative Delivery WG - Charter Cooperative Delivery WG - Charter Interested Parties Problem Statement What combinations of tooling are available out there that aim to resolve this problem, and what are the gaps encountered? Examples of known patterns…
A blog post by Charity Majors about why you should ask Ops questions when interviewing software engineers.
In short, we all are responsible for the stability of our systems as well as encouraging good practices of deploying, releasing, observing software, etc. Therefore, it's not enough to just have an SRE team and push that burden on them. Reliability and operations should be a concern for any team within a company.
Quote:
Our industry has gotten very good at pressing operations engineers to get better at writing code, writing tests, and software engineering in general these past few years. Which is great! But we have not been nearly so good at pushing software engineers to level up their systems skills. Which is unfortunate, because it is just as important.
#culture
In short, we all are responsible for the stability of our systems as well as encouraging good practices of deploying, releasing, observing software, etc. Therefore, it's not enough to just have an SRE team and push that burden on them. Reliability and operations should be a concern for any team within a company.
Quote:
Our industry has gotten very good at pressing operations engineers to get better at writing code, writing tests, and software engineering in general these past few years. Which is great! But we have not been nearly so good at pushing software engineers to level up their systems skills. Which is unfortunate, because it is just as important.
#culture
charity.wtf
Why every software engineering interview should include ops questions
I’ve fallen way behind on my blog posts — my goal was to write one per month, and I haven’t published anything since MAY. Egads. So here I am dipping into the drafts archives! Thi…
An opinionated list of the books on distributed systems and system design.
Many of those books are well-known, but a few of them were new to me. So, I hope you can find something interesting for you there as well!
#books
Many of those books are well-known, but a few of them were new to me. So, I hope you can find something interesting for you there as well!
#books
Best Books Hub
20 Best Books on Distributed Systems (2022 Review) - Best Books Hub
List of best distributed system books review. Discover the good distributed system books for elementary, intermediate and advanced readers.
Ok. That's interesting.
Docker is updating their pricing model once again and here is the interesting part:
At Docker we remain committed to continuing to provide an easy-to-use, free experience for individual developers, open source projects, education, and small businesses. In fact, altogether these communities represent more than half of all Docker usage. Docker Personal and all its components – including Docker CLI, Docker Compose, Kubernetes, Docker Desktop, Docker Build/BuildKit, Docker Hub, Docker Official Images, and more – *remain free for these communities*.
Specifically, small businesses (fewer than 250 employees AND less than $10 million in revenue) may continue to use Docker Desktop with Docker Personal for free. The use of Docker Desktop in large businesses, however, requires a *Pro*, *Team*, or *Business* paid subscription, starting at $5 per user per month.
I'm still not 100%, but it sounds like you won't be able to use Docker Desktop on you corporate laptop starting from 31st January 2022 if your company is "big enough".
Here's a Twitter thread by Corey Quinn on this issue.
#docker
Docker is updating their pricing model once again and here is the interesting part:
At Docker we remain committed to continuing to provide an easy-to-use, free experience for individual developers, open source projects, education, and small businesses. In fact, altogether these communities represent more than half of all Docker usage. Docker Personal and all its components – including Docker CLI, Docker Compose, Kubernetes, Docker Desktop, Docker Build/BuildKit, Docker Hub, Docker Official Images, and more – *remain free for these communities*.
Specifically, small businesses (fewer than 250 employees AND less than $10 million in revenue) may continue to use Docker Desktop with Docker Personal for free. The use of Docker Desktop in large businesses, however, requires a *Pro*, *Team*, or *Business* paid subscription, starting at $5 per user per month.
I'm still not 100%, but it sounds like you won't be able to use Docker Desktop on you corporate laptop starting from 31st January 2022 if your company is "big enough".
Here's a Twitter thread by Corey Quinn on this issue.
#docker
Docker
Announcing Upgraded Docker Plans: Simpler, More Value, Better Development and Productivity | Docker
Docker announces significant upgrades to its subscription plans, delivering more value, flexibility, and tools for customers of all sizes.
There might be a few engineering managers on this channel.
So, here is an awesome engineering management list.
However, it also contains some things that might be interesting for engineers like risk management, capacity planning as well as the list of calendar software, time trackers, etc.
#management
So, here is an awesome engineering management list.
However, it also contains some things that might be interesting for engineers like risk management, capacity planning as well as the list of calendar software, time trackers, etc.
#management
GitHub
GitHub - engineering-management/awesome-engineering-management: Pointers and tools for learning and day-to-day practice of engineering…
Pointers and tools for learning and day-to-day practice of engineering management & leadership. - GitHub - engineering-management/awesome-engineering-management: Pointers and tools for lear...
Today at 17:00 UTC we are going to have our usual voice chat (in Ukrainian and Russian) to discuss the topics, you've proposed and voted for in the chat, which follows the DevOps Days Open Spaces format.
Today we are going to talk about "DevOps buzz-words" and how to provide meaningful feedback to your peers.
As usual. We will start from these topics and then if the discussion drifts, it drifts.
You can join the voice chat via this link:
https://t.iss.one/catops_chat?voicechat
Hear you there!
UPD: Voice charts are in Ukrainian or Russian language
#event
Today we are going to talk about "DevOps buzz-words" and how to provide meaningful feedback to your peers.
As usual. We will start from these topics and then if the discussion drifts, it drifts.
You can join the voice chat via this link:
https://t.iss.one/catops_chat?voicechat
Hear you there!
UPD: Voice charts are in Ukrainian or Russian language
#event
A magnificent write-up by Tanya Reilly about doing glue work!
It's such a shame I haven't read and shared this piece earlier!
So, basically what's glue work? It's about enabling others, picking up loose ends in your organization, etc. Usually, this is non-promotable work, i.e. not under your direct responsibilities. However, this is also usually a crucial work which helps your organization to move forward.
In this article Tanya argues that even though such work is inevitable, moreover expected, on senior and staff-plus positions; doing a lot of glue can be harmful during your early stages of career.
There are a lot of things to think about after reading this one. For example, I have revisited my opinions on Personal Development Plans personally. Previously, I thought this can be easily replaced by personal OKRs, but now I realize that PDP is a meaningful way to work with your manager and agree on which types of work are expected and, the most important, promotable in your current stage of career.
Very good read, much recommend!
#culture #career
It's such a shame I haven't read and shared this piece earlier!
So, basically what's glue work? It's about enabling others, picking up loose ends in your organization, etc. Usually, this is non-promotable work, i.e. not under your direct responsibilities. However, this is also usually a crucial work which helps your organization to move forward.
In this article Tanya argues that even though such work is inevitable, moreover expected, on senior and staff-plus positions; doing a lot of glue can be harmful during your early stages of career.
There are a lot of things to think about after reading this one. For example, I have revisited my opinions on Personal Development Plans personally. Previously, I thought this can be easily replaced by personal OKRs, but now I realize that PDP is a meaningful way to work with your manager and agree on which types of work are expected and, the most important, promotable in your current stage of career.
Very good read, much recommend!
#culture #career
No Idea Blog
Being Glue — No Idea Blog
Slides and notes for the Being Glue talk.
There were a lot of culture posts here lately, but no worries were still in the engineering domain!
So, today I want to share a neat detective/mystery story abut ZFS by Brendan Gregg.
It's called "ZFS Is Mysteriously Eating My CPU" and I won't add any more details here to keep the suspense.
Enjoy!
#performance #linux
So, today I want to share a neat detective/mystery story abut ZFS by Brendan Gregg.
It's called "ZFS Is Mysteriously Eating My CPU" and I won't add any more details here to keep the suspense.
Enjoy!
#performance #linux
Unless you contribute to Terraform core, this won't be super relevant for you.
However, this update is a bit disturbing.
Quote:
Due to current low staffing on the Terraform Core team at HashiCorp, we are not routinely reviewing and merging community-submitted pull requests. We do hope to begin processing them again soon once we're back up to full staffing again, but for the moment we need to ask for patience. Thanks!
Source
Kudos to HashiCorp for being explicit about it, though!
#hashicorp #terraform
However, this update is a bit disturbing.
Quote:
Due to current low staffing on the Terraform Core team at HashiCorp, we are not routinely reviewing and merging community-submitted pull requests. We do hope to begin processing them again soon once we're back up to full staffing again, but for the moment we need to ask for patience. Thanks!
Source
Kudos to HashiCorp for being explicit about it, though!
#hashicorp #terraform
GitHub
Be explicit that community PR review is currently paused · hashicorp/terraform@6562466
Terraform enables you to safely and predictably create, change, and improve infrastructure. It is a source-available tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and…
Yet another list of tools, which ease Kubernetes operations.
The majority of things in this list are not new and actually well-known across the industry. However, I found here a few interesting things I would like to take a closer look at. For example, Capsule for multi-tenant support and Kubevela - an implementation of Open Application Model (OAM).
BTW, Open Application Model is a pretty interesting concept. I really need to write about it here more often.
#kubernetes
The majority of things in this list are not new and actually well-known across the industry. However, I found here a few interesting things I would like to take a closer look at. For example, Capsule for multi-tenant support and Kubevela - an implementation of Open Application Model (OAM).
BTW, Open Application Model is a pretty interesting concept. I really need to write about it here more often.
#kubernetes
Medium
Kubernetes Essential Tools: 2021
Review of the best tools for Kubernetes
A humble bundle with books about Kubernetes from Pluralsight.
As usual, you can pay €21.24 for 23 books, €17.64 for 13, or at least €1 for 7.
The books in this bundle are practical guides for configuring different aspects of Kubernetes or setting up it on platforms like AKS.
Personally, I'm not a big fan of technology-specific books. This type of knowledge tend to become obsolete too fast these days. However, if you need hands-on manuals for Kubernetes right here right now, this could be a good choice.
Also, I've never read books by Pluralsight, but their online courses are nice. So, I think the books should also be good.
#books
As usual, you can pay €21.24 for 23 books, €17.64 for 13, or at least €1 for 7.
The books in this bundle are practical guides for configuring different aspects of Kubernetes or setting up it on platforms like AKS.
Personally, I'm not a big fan of technology-specific books. This type of knowledge tend to become obsolete too fast these days. However, if you need hands-on manuals for Kubernetes right here right now, this could be a good choice.
Also, I've never read books by Pluralsight, but their online courses are nice. So, I think the books should also be good.
#books
Humble Bundle
Humble Software Bundle: Kubernetes with Pluralsight
Learn Kubernetes in and out with Pluralsight software like Why Kubernetes & Getting Started with Google Kubernetes Engine. Pay what you want & support charity!
Flame graphs is a powerful tool to visualize an application profile and spot narrow places in your codebase.
Kubectl Flame brings this functionality as a frictionless
Currently, it supports Java using
Also, since we're talking about performance, here is a free-to-use Kubernetes Instacne Calculator, which helps you to calculate the optimal size of cloud nodes based on your resource requests and limits.
#kubernetes #performance
Kubectl Flame brings this functionality as a frictionless
kubectl plugin! Now, you can generate a flame graph from a running pod using just kubectl.Currently, it supports Java using
async-profiler, Go using ebpf profiling. Python support is based on py-spy. Ruby support is based on rbspy.Also, since we're talking about performance, here is a free-to-use Kubernetes Instacne Calculator, which helps you to calculate the optimal size of cloud nodes based on your resource requests and limits.
#kubernetes #performance
Medium
Introducing Kubectl Flame: Effortless Profiling on Kubernetes
A kubectl plugin that allows you to profile production applications with low-overhead by generating FlameGraphs
An article that saved me some time yesterday.
It's about how to append custom paths to the
However, you can do it as below:
#cicd #gha
It's about how to append custom paths to the
$PATH variable on a GitHub Actions runner. As you may guess, it's not simply $PATH.However, you can do it as below:
- run: echo "${HOME}/<YOUR_CUSTOM_BIN>" >> $GITHUB_PATH
#cicd #gha
www.scivision.dev
Append PATH in GitHub Actions
how to append to PATH in GitHub Actions
It’s been 5 years since Envoy was open sourced.
Therefore, Matt Klein (one of the creators of Envoy) published a longread with the retrospective of these years and the way Envoy made from an internal proxy in Lift to kinda default choice for cloud environments.
This read may beinteresting for those who work on the open source tools in their companies as well as for the individual open source contributors.
#oss #longread
Therefore, Matt Klein (one of the creators of Envoy) published a longread with the retrospective of these years and the way Envoy made from an internal proxy in Lift to kinda default choice for cloud environments.
This read may beinteresting for those who work on the open source tools in their companies as well as for the individual open source contributors.
#oss #longread
Matt Klein
5 years of Envoy OSS
Today marks the 5 year anniversary of the open sourcing of Envoy Proxy. It would not be an exaggeration to say that professionally, the last 5 years have been a roller coaster of epic proportions, my