DevOps & SRE notes – Telegram
DevOps & SRE notes
12K subscribers
42 photos
19 files
2.5K links
Helpful articles and tools for DevOps&SRE

WhatsApp: https://whatsapp.com/channel/0029Vb79nmmHVvTUnc4tfp2F

For paid consultation (RU/EN), contact: @tutunak


All ways to support https://telegra.ph/How-support-the-channel-02-19
Download Telegram
Good article about scaning vulnerabilities
https://semaphoreci.com/blog/govulncheck
The article discusses how to use eBPF (extended Berkeley Packet Filter) to collect telemetry data from a service without code changes and without requesting engineering efforts. eBPF provides the ability to execute programs on the Operational System Kernel, extending the OS capabilities and leveraging the kernel's privileged ability to control the system. The author explains how to use Pixie, an open-source observability solution for Kubernetes applications that uses eBPF to collect telemetry data automatically. Pixie offers features such as network monitoring, database query profiling, continuous application profiling, and Kafka monitoring. However, Pixie has two drawbacks, long-term data retention, and a lack of support for ARM architectures. The article concludes by suggesting other tools that offer similar features to Pixie, such as Cilium Hubble.

https://itnext.io/observability-strategies-to-not-overload-engineering-teams-ebpf-b034b26d7f1d
kubectl foreach is a command-line tool that enables running kubectl commands on one or more contexts (clusters) in parallel. Users can match context names from kubeconfig using patterns such as exact names and regular expressions. The tool offers options for limiting parallel executions, disabling confirmation prompts, and replacing values in kubectl arguments with context names. kubectl foreach can be installed using Krew kubectl plugin manager and used to query pods and run commands on multiple contexts at the same time. The tool is not intended for deploying workloads to clusters or using programmatically yet.

https://github.com/ahmetb/kubectl-foreach
This article provides a deep dive into container file systems, specifically the use of OverlayFS in containers. It explains the need for container file systems to reduce data redundancy and save disk space, as well as how UnionFS mounts multiple directories together in one directory. The article also provides sample commands to illustrate how OverlayFS works and how Docker container uses it to divide container image files into multiple layers. Overall, this article is useful for those who want to understand the technical details of container file systems and how they work in containers.
https://medium.com/geekculture/k8s-container-file-system-ec26eda8b3ea
The article explains how to enable communication between microservices in a Kubernetes cluster, using various methods. The author starts by deploying a simple setup that simulates two pods communicating with each other. They then explore different methods to achieve communication between these pods, including using pod IPs directly, creating and using services, and communicating between services across namespaces. The author also explains how to use environment variables and fully-qualified DNS names to address services. The article is a useful reference for anyone working with Kubernetes microservices. https://dev.to/narasimha1997/communication-between-microservices-in-a-kubernetes-cluster-1n41
👌1
The article discusses the differences between Red Hat OpenShift and Kubernetes, two popular container orchestration management systems. While Kubernetes is an open-source container orchestration system developed by Google, OpenShift is a cloud-based Kubernetes container platform that offers consistent security, built-in monitoring, centralized policy management, and compatibility with Kubernetes container workloads. OpenShift contains all the native Kubernetes and Podman features and adds value through its own management functionality and DevOps tooling features. OpenShift offers stronger security features than native Kubernetes, but its stricter policies can make it harder to administer initially. While Kubernetes is more flexible, OpenShift is cheaper and offers enterprise-level support, making it more valuable to large organizations. The article provides details on deployment options, support, cost, releases and updates, networking, templates, image registry management, and integrated CI/CD for both systems.
https://itnext.io/openshift-vs-kubernetes-what-is-the-difference-cadee96497b7