DevOps&SRE Library
17.8K subscribers
462 photos
4 videos
2 files
4.76K links
Библиотека статей по теме DevOps и SRE.

Реклама: @ostinostin
Контент: @mxssl

РКН: https://knd.gov.ru/license?id=67704b536aa9672b963777b3&registryType=bloggersPermission
Download Telegram
reverst

Reverst is a (load-balanced) reverse-tunnel server and Go server-client library built on QUIC and HTTP/3.


https://github.com/flipt-io/reverst
Kubernetes EOL: Understanding the K8s Release Cycle and How to Prepare for EOL

https://komodor.com/learn/kubernetes-eol-understanding-the-k8s-release-cycle-and-how-to-prepare-for-eol
Running JVM Applications on Kubernetes: Beyond java -jar

Discover some important tips about running JVM applications in containerized environments orchestrated by Kubernetes


https://medium.com/codex/running-jvm-applications-on-kubernetes-beyond-java-jar-a095949f3e34
A Tale of Two VLANS

Splitting service traffic on-prem with MetalLB


https://blog.miraco.la/a-tale-of-two-vlans
Progressive Delivery for Stateful Services Using Argo Rollouts

https://codefresh.io/blog/progressive-delivery-for-stateful-services-using-argo-rollouts
Forwarded from AWS Notes
​​Terraform best practices from AWS

https://docs.aws.amazon.com/prescriptive-guidance/latest/terraform-aws-provider-best-practices/introduction.html

Backend

▫️ Use S3 for remote storage
▫️ Facilitate team collaboration
▫️ Separate the backends for each environment
▫️ Actively monitor remote state activity

Code

▫️ Implement a standard repository structure
▫️ Structure for modularity
▫️ Follow naming conventions
▫️ Use attachment resources
▫️ Use default tags
▫️ Meet Terraform Registry requirements
▫️ Use recommended module sources
▫️ Follow coding standards

Versions

▫️ Use the TFLint
▫️ Monitor new releases

Modules

▫️ Use variables for customization
▫️ Understand dependencies
▫️ Use trusted sources

#Terraform
K3s Traefik Ingress - configured for your homelab!

https://sklar.rocks/k3s-traefik-ingress
Kubernetes Deep Health Checks

Distributed systems are often described as a double-edged sword. There is plenty of excellent content out there written on both why they suck and also why they are great. This is not one of those posts. I would say generally I am an advocate and believer in distributed systems where they make sense, but the goal of this blog post (and the two others that will follow) is to share some stories with you about where I have got something wrong within a distributed system that has led to a far reaching impact.

In this first post, I will share a mistake that I have seen made in multiple companies now that can lead to cascading failure. I call it the Kubernetes deep health check.

https://encore.dev/blog/horror-stories-k8s
Free Kubernetes

List of free Trials/Credit for Managed Kubernetes Services


https://github.com/learnk8s/free-kubernetes
sig

Interactive grep


https://github.com/ynqa/sig
Building a GitOps CI/CD Pipeline with GitHub Actions (SOC 2)

This guide presents a simple and developer-friendly GitOps-based CI/CD pipeline built on GitHub Actions, designed for SOC 2 compliance. Having successfully implemented this approach numerous times, I'm sharing an illustrative version for reference. You can explore a working implementation on your own on GitHub (https://github.com/cicd-excellence), or continue reading for a step-by-step breakdown.


https://mathieularose.com/gitops-cicd-github-actions
Solving the mystery of pods health checks failures in Kubernetes

Pipedrive Infra operates self-managed Kubernetes clusters in different clouds, mainly AWS and on-premise OpenStack.

At the time of writing, we manage over 20 different clusters — more and less specific, big and small.


https://medium.com/pipedrive-engineering/solving-the-mystery-of-pods-health-checks-failures-in-kubernetes-55b375493d03
Tableau on Kubernetes: How not to design a Kubernetes offering

Tableau announced that you can run their server on Kubernetes back in 2021. Now that it’s been a few years, let’s take a look and see how it is to setup.


https://medium.com/@almenon214/tableau-on-kubernetes-how-not-to-design-a-kubernetes-offering-b18decf30c18