AWSDoor is a red team automation tool designed to simulate advanced attacker behavior in AWS environments

https://github.com/OtterHacker/AWSDoor

This write-up explores the emerging discipline of AI Reliability Engineering (AIRe) as the "Third Age of SRE." It argues that the unique challenges of AI workloads, such as their probabilistic nature and new failure modes like model decay, require an evolution of traditional Site Reliability Engineering principles.
https://thenewstack.io/ai-reliability-engineering-welcome-to-the-third-age-of-sre/

This dispatch offers a detailed walkthrough for backend engineers on creating a Kubernetes Operator using Go and Kubebuilder. The author, Amr Elhewy, simplifies complex DevOps concepts by building a practical "PodTracker" operator that sends Slack notifications for new pod creations.
https://hewi.blog/a-backend-engineer-lost-in-the-devops-world-making-a-kubernetes-operator-with-go

MLOps Tools For Managing & Orchestrating The Machine Learning LifeCycle

https://github.com/polyaxon/polyaxon

OpenYurt - Extending your native Kubernetes to edge(project under CNCF)

https://github.com/openyurtio/openyurt

🔥 FREE premium exam prep on AWS Skill Builder until Jan 5, 2026!

https://skillbuilder.aws/

🎓 𝗖𝗼𝘃𝗲𝗿𝘀:
🔸AWS Certified Cloud Practitioner (CLF-C02)
🔸AWS AI Practitioner

💡 𝗪𝗵𝗮𝘁 𝘆𝗼𝘂 𝗴𝗲𝘁 (𝗻𝗼𝗿𝗺𝗮𝗹𝗹𝘆 𝗽𝗮𝗶𝗱):
✅ Official practice exams
✅ Hands-on labs (SimuLearn)
✅ AWS Escape Room (learning by playing)
✅ Flashcards & learning plans

Plus, there are always-free resources:
• Official practice questions
• Free AWS training events
• AWS Educate (labs + potential free exam vouchers)

#AWS_certification

This post compares Amazon EKS Auto Mode and Azure AKS Automatic, evaluating which platform offers a superior managed Kubernetes solution. While acknowledging AWS's progress, the author ultimately argues that AKS Automatic's more comprehensive, end-to-end automation makes it the clear winner for a truly hands-off experience.
https://pixelrobots.co.uk/2024/12/amazon-eks-auto-mode-vs-azure-aks-automatic-the-better-managed-kubernetes-solution/

This paper delves into disaster recovery architectures that go beyond simple high availability to ensure systems remain operational even when HA fails. Yakaiah Bommishetti outlines various DR strategies, from cold backups to active-active multi-site setups, emphasizing the critical difference between preventing failures and restoring services after a catastrophe.
https://hackernoon.com/beyond-high-availability-disaster-recovery-architectures-that-keep-running-when-ha-fails

Cloudflare, again

Open Source Marketplace For Developer Tools

https://github.com/alexellis/arkade

Will the "Code Orange" help Cloudflare?
https://blog.cloudflare.com/fail-small-resilience-plan/

A set of modern Grafana dashboards for Kubernetes.

https://github.com/dotdc/grafana-dashboards-kubernetes

This case study examines the build-versus-buy decision for Terraform CI/CD orchestration by analyzing a custom-built tool called Terraflow. The author reflects on the trade-offs between creating a bespoke solution that perfectly fits a specific workflow and the opportunity cost of diverting engineering resources from core business features.
https://terrateam.io/blog/build-vs-buy-terraflow-case-study

This tutorial guides readers through building a unified OpenTelemetry pipeline in Kubernetes to correlate metrics, logs, and traces. Fatih Koç explains how to deploy the OTel Collector as both a DaemonSet and a gateway to centralize enrichment and sampling, ultimately reducing incident resolution time.
https://fatihkoc.net/posts/opentelemetry-kubernetes-pipeline/

Kamaji is the Hosted Control Plane Manager for Kubernetes.

https://github.com/clastix/kamaji

Fast featureful friendly wifi terminal UI. 🛜✨

https://github.com/shazow/wifitui

This documentation demystifies the structure of Kubernetes YAML files by breaking them down into their three core components: metadata, spec, and status. It explains how users define the desired state in the spec, while Kubernetes continuously works to align the actual status with that intent through its reconciliation loop.
https://medium.com/@thisara.weerakoon2001/demystifying-kubernetes-yaml-ef9e92acf3df

This engineering publication from DoubleVerify presents a case study on synchronizing database schema updates across multiple projects and environments. The team developed a solution using a shared, standalone schema migrations repository and Kubernetes pre-install hooks to automate and coordinate the process.
https://medium.com/doubleverify-engineering/a-case-study-in-synchronizing-database-schema-updates-between-projects-and-environments-a69a3cc38985

eBPF based cloud-native load-balancer for Kubernetes|Edge|Telco|IoT|XaaS.

https://github.com/loxilb-io/loxilb

Kubernetes v1.35: Timbernetes — Only the Important Parts (Part 1): Deprecations, removals

Removal of cgroup v1 support
Cgroup v2 is now the modern standard, Kubernetes is ready to retire the legacy cgroup v1 support in v1.35. This is an important notice for cluster administrators: if you are still running nodes on older Linux distributions that don't support cgroup v2, your `kubelet` will fail to start. To avoid downtime, you will need to migrate those nodes to systems where cgroup v2 is enabled.

Deprecation of ipvs mode in kube-proxy
Because of this maintenance burden, Kubernetes v1.35 deprecates `ipvs` mode. Although the mode remains available in this release, `kube-proxy` will now emit a warning on startup when configured to use it.

Final call for containerd v1.X
While Kubernetes v1.35 still supports containerd 1.7 and other LTS releases, this is the final version with such support. The SIG Node community has designated v1.35 as the last release to support the containerd v1.X series.

Not so long ago, I posted news about moving CDK for Terraform to read-only mode, and now I think this outcome was inevitable.

- Programming languages are not well suited for describing infrastructure because they provide too much flexibility.

- Different companies can use different programming languages to describe essentially the same infrastructure.

- The entry barrier becomes higher: a DevOps engineer now needs to understand code written by someone else before them. We already have problems with code smells in application development, and this problem will not be any better when it comes to infrastructure denoscription.

- HCL is not perfect, but it is more straightforward. Terraform has become a de facto standard, and even its fork is not very popular (why change something if everything works?). The IaC world is generally inert.

- The market is already occupied by Pulumi, so to succeed you would need to be significantly better—but you can’t.

For all these reasons, CDK for Terraform never became popular. The same thing will likely happen to AWS CDK sooner or later.

https://news.1rj.ru/str/devops_sre_notes/2567