Git is simply too hard.
I have mixed feelings about this article. On one hand, Git is too hard indeed. I personally google certain Git operations from time to time.
On another hand, this article doesn't provide any alternatives or ideas on how to fix this situation. Also, a lot of Git complexity comes from its distributed nature. Distributed systems are much harder to architect compared to centralized ones. Although, currently, we're mostly using Git as a centralized system nowadays.
So, I'll just add this well-known comics here.
#git
A system design exercise for on-premise infrastructure. The article is called DevOps Big Picture (On-Premises). However, it only explores a single example with a limited scope and a lot of assumptions. Yet, you still can use this diagram as a baseline in system design interviews, for example.
Unfortunately, data layer is completely missing there. I mean, data layer is the most difficult one, so a lot of people are omitting it on purpose. I cannot blame them for that. So, you can have a mental exercise and think about how would you manage the persistent data in the proposed infrastructure 😉
#design #kubernetes
A story from VS Code developers about how they made bracket pair colorization 10,000x faster.
I like such articles, which touch topics of raw computer science. I think such stories help us to reconnect with the beauty of our craft.
Although, it won't make me switch to VS Code from NeoVim :D
#computer_science #microsoft
A new episode of our voice chat chat (in Ukrainian)!
This time we spoke about job related topics beyond DevOps. Specifically:
- How often does it make sense to change a job. And what does “often” even mean in this context.
- Does it make sense to grow professionally beyond the Senior level or it can be the final stop in one’s career.
You can listen to this episode on:
- YouTube
- Substack
- Spotify
- Apple Podcasts
- Google Podcasts
BTW, since I moved the audio hosting to Substack, it makes sense to subscribe there to get new episodes right after they’re published.
#voice #career #job #ukrainian
Цього разу теми також були повʼязані із роботою в цілому. Обговорили наскільки це Ок часто змінювати місце роботи і що взагалі означає це "часто".
Також поговорили про те, чи варто рости у карʼєрі вище рівня senior.
Матеріали, що згадуються в епізоді:
- Staff Engineer website - https://staffeng.com/
- The Staff Engineer's Path book - https://www.amazon.com/Staff-Engineers-Path-Tanya-Reilly-ebook/dp/B0BG16Y553
- Engineering Management: The Pendulum Or The Ladder by Charity Majors - https://charity.wtf/2019/01/04/engineering-management-the-pendulum-or-the-ladder/
Музика на початку і в кінці епізоду: Depth Charge by Metre.
VictoriaMetrics have released their first iteration of the log platform!
Here’s the info:
The first release of VictoriaLogs!Release page on GitHubDocumentationDocker demosHelm Chart
Here you can find a Benchmark for VictoriaLogs
Since I’m not a user, it’s hard for me to provide feedback right away. Yet, if you use it or want to try and want to provide any feedback to the maintainers, do not hesitate to submit bug reports and feature requests on GitHub.
#victoriametrics #logs #observability
This is VictoriaLogs Preview release
It provides the following key features:
VictoriaLogs can accept logs from popular log collectors. See these docs.
VictoriaLogs is much easier to setup and oper...
Today I'm announcing my retirement from Google. Even the best rides come to an end. As I turn the page on this chapter, I realized I've spent the last 25 years learning how to work, I hope to spend the rest of my life learning how to live.
HashiCorp posted an article in their blog on why platform teams should run as product teams.
If you're familiar with the topic of Platform Engineering, likely there is not that much new information for you. However, I think it's important to repeat those points, because the more people see them and start acting this way, in the better shape the industry will be.
Also, this article contains links to other articles and case studies that clarify some aspects. I like it when an article is a so-called "crossroad". So, you can continue exploring a topic once you've done with the original piece.
P.S. I cannot come up with a short tag for the platform engineering related topics. So, I would appreciate it if suggest something in the chat.
#platfom_engineering #hashicorp
Maksym Vlasov - the co-author of this channel - has written an article about how to create Terraform lockfiles for hundreds of root modules.
You can read it in:
- My blog. This is the first guest article, BTW!
- Or you can find it on Substack (don't forget to subscribe there!)
Also, the live stream with Maksym and Terraform-master - Anton Babenko - is live right now!
#terraform #hashicorp #oc
This is the first guest article in this blog. This is one is by Maxym Vlasov - my co-author of the CatOps channel.
Pre-history As you may know, Terraform 1.4.0 has introduced changes, which break the previous unintentional behavior. Previously, you could ignore the lockfile and use cached providers as long as the version constraints in the code were okay with your local cache. Starting from 1.4.0, Terraform always checks the lockfile before going into your cache directory.
For today's Donations Monday I want to remind you about the Kolo charity foundation, which has a goal to raise 10M UAH for Shark UAV.
Direct link to donate.
#donations #Ukraine
OpenAI shares their story of running large Kubernetes clusters.
Their setup is quite unique since they mostly running research jobs. Still, there are couple of takeaways for running large-size clusters. For example, reducing the number of DaemonSets and the number of the node count fluctuations.
Also, as usual the most interesting part is the “Unsolved problems” paragraph.
#kubernetes
We’ve scaled Kubernetes clusters to 7,500 nodes, producing a scalable infrastructure for large models like GPT-3, CLIP, and DALL·E, but also for rapid small-scale iterative research such as Scaling Laws for Neural Language Models.
With the whole AI hype going on, it's interesting to see how companies are trying to find an application for AI in their products.
Sometimes it's just pure hype, in my opinion. There are some
"AI-powered" tools that existed just fine without AI. However, I personally see three major areas for AI (LLMs to be precise) in the operational field:
- Taking over some boring tasks like writing some Bash, Makefiles and so on.
- Observability: basically explaining alerts to humans and suggest possible solutions. Perhaps, even apply those suggestions.
- Knowledge management. LLM can answer reoccurring questions instead of a support person. You can even try to teach a model based on your internal documentation and so on.
And here are some practical implementations in some of those areas:
- GitLab’s new security feature uses AI to explain vulnerabilities to developers
- Pulumi AI that writes IaC for you.
P.S. The news about GitLab came from our chat. So, if you have any interesting news to share, do not hesitate to join!
#ai #gitlab #pulumi #iac
Developer platform GitLab today announced a new AI-driven security feature that uses a large language model to explain potential vulnerabilities to developers, with plans to expand this to automatically resolve these vulnerabilities using AI in the future.
A video report from KubeCon featuring Denys Vasyliev, Stanislav Kolenkin, and myself.
It‘s in Ukrainian (mostly). And we also have a text report which is coming soon.
#event #kubernetes
KubeCon-2023 Амстердам. Про нове життя Service Mesh, складність Kubernetes та тренди індустрії.
Ведучі:
https://www.linkedin.com/in/yrochnyak/
https://www.linkedin.com/in/stanislav-kolenkin-4b6b96a/
https://www.linkedin.com/in/denys-vasyliev/
Гості:
https://www.linkedin.com/in/viktorfarcic @DevOpsToolkit
https://twitter.com/kelseyhightower
00:00 Check-in
00:14 Вітаю на KubeConʼ23
00:35 KubeCon Vibe
00:50 Вітання від Стаса
01:17 З Юрієм під лампою
01:30 Ранкова кава
01:48 Showcase та Project pavilion
03:50 Огляд докладів та планування
06:15 Гості подкасту та спікери
07:22 Ще трогхи вайбу
07:52 min.io
08:25 Booking.com
08:35 O'Reilly
08:53 Anynies
10:00 Kubiya.ai
10:26 netapp
10:44 Linux Foundation
11:25 Що цікавого вже знайшли
11:35 Calico
12:35 XL please
12:49 Розпаковка обіду
13:35 Splunk
14:50 Launge area: саморозвиток
15:52 Не провтикайте сесію
17:16 Argocd
18:00 Gitops @ AWS
18:27 Що по роботам
19:01 Huawei пішли звідси
19:28 Helios Opentelemetry
19:55 Open Source @ Mercedes-Benz
20:42 Подкаст із мерса
20:50 Почнемо з позитивчику
21:07 Про мулти-кластер
21:41 Cluster Busters
22:39 Перший кубкон у Юрія стався в Астері
23:00 Сила комʼюніті
23:35 Тренди KubeCon'23
24:22 Фейли KubeConʼ23
25:01 Кейс PlayStation
26:12 Apono
26:58 Куди поділись іновації
27:30 Service Mesh з поверненням
28:20 А що по HA у waypoint
28:45 Відповідає John Howard
29:11 Сила комʼюніті-2
29:48 env0
30:22 Це вам не ямілікі шльопать
31:07 Viktor Farcic - Куберенетес зникне
32:22 Про кости та FinOps
33:47 Kubecost
34:17 Crossplane
34:46 Про складність Kubernetes
35:24 Viktor Farcic про Complexity
36:00 Юрій про стандарти та Lego
36:49 Viktor Farcic - сomplexity у Crossplane
37:19 Що обʼєднує Huawei та Nginx
38:30 Компанії повинні не зупинятись у розвитку
38:50 Кейс Nginx API
39:50 Viktor Farcic: Yaml - це для роботів
40:44 Envoy vs Nginx - back to the roots
41:41 Kelsey Hightower: Istio Ambient Mesh
43:22 Юрій про циклічність технологій
45:03 Kelsey Hightower: ChatGPT
46:41 Love, AI & Robots
47:47 Roboverse Reply
48:13 Юрій: technology fleshback
49:19 Тест на проді чи на кошках
50:30 KSOC - stend for Ukraine
51:11 Steve Wade: KSOC security startup
52:00 Фіксимо LinkedIn українською
52:56 Party time
#kubernetes #kubecon #istio #google #ebpf #servicemesh #envoy #crossplane @DevOpsToolkit
It turned out that IBM has a lot of free courses on SRE: www.ibm.com/trainin…eer(sre)
Sure, the main goal is to make you familiar with their cloud and get some adopters. However, some courses look generic. Thus, you may benefit from them even if you don’t plan to use IBM Cloud.
#learning #ibm
Puppet Labs have issued a new State of DevOps 2023 report.
This time it’s focused on Platform Engineering and how it helps organizations to achieve their goals and move further with their DevOps journey. Key takeaways (opinionated):
- While DevOps helps to foster collaboration and delivery velocity inside teams, platform engineering helps to increase the delivery velocity across the organization.
- Companies that have implemented platform engineering approach are satisfied with it. Also, companies that have platform teams for longer period of time are more satisfied, which is a good sign.
- Platform engineering treats infrastructure (observability, CI/CD, etc.) as a product, not as project. Therefore, platform teams benefit from a product manager position within a team.
- Yet, about a half of respondents have reported that their senior leadership is still concerned about the topic of platform engineering or confused about it.
- Centralized platform team is more common compared to decentralized and people who work in a centralized structure are more satisfied.
- Organizations plan to hire engineers to work on their internal platforms. So, you‘re safe :)
- 01 Normalize the technology stack => 02 Standardize and reduce variability => 03 Expand DevOps practices => 04 Automate infrastructure delivery => 06 Provide self-service capabilities => ???? => PROFIT!!1
#report #culture #platform_engineering #devops
The State of Platform Engineering Report is the 2023 edition of our State of DevOps Report. Download it today & learn platform engineering's impact on DevOps.