AWSDoor is a red team automation tool designed to simulate advanced attacker behavior in AWS environments
https://github.com/OtterHacker/AWSDoor
https://github.com/OtterHacker/AWSDoor
GitHub
GitHub - OtterHacker/AWSDoor: AWSDoor is a red team automation tool designed to simulate advanced attacker behavior in AWS environments
AWSDoor is a red team automation tool designed to simulate advanced attacker behavior in AWS environments - OtterHacker/AWSDoor
❤2
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/
https://thenewstack.io/ai-reliability-engineering-welcome-to-the-third-age-of-sre/
The New Stack
AI Reliability Engineering: Welcome to the Third Age of SRE
SREs must build AI we can trust, leveraging the emerging ecosystem of tools and standards.
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
https://hewi.blog/a-backend-engineer-lost-in-the-devops-world-making-a-kubernetes-operator-with-go
🔥3
MLOps Tools For Managing & Orchestrating The Machine Learning LifeCycle
https://github.com/polyaxon/polyaxon
https://github.com/polyaxon/polyaxon
GitHub
GitHub - polyaxon/polyaxon: MLOps Tools For Managing & Orchestrating The Machine Learning LifeCycle
MLOps Tools For Managing & Orchestrating The Machine Learning LifeCycle - polyaxon/polyaxon
👍4
OpenYurt - Extending your native Kubernetes to edge(project under CNCF)
https://github.com/openyurtio/openyurt
https://github.com/openyurtio/openyurt
GitHub
GitHub - openyurtio/openyurt: OpenYurt - Extending your native Kubernetes to edge(project under CNCF)
OpenYurt - Extending your native Kubernetes to edge(project under CNCF) - openyurtio/openyurt
👍3
Forwarded from AWS Notes (Roman Siewko)
🔥 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
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
🔥3
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/
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
https://hackernoon.com/beyond-high-availability-disaster-recovery-architectures-that-keep-running-when-ha-fails
Hackernoon
Beyond High Availability: Disaster Recovery Architectures That Keep Running When HA Fails
High Availability is not Disaster Recovery. This in-depth guide explores real-world Disaster Recovery architectures.
❤🔥3❤2
DevOps & SRE notes
Cloudflare, again
Will the "Code Orange" help Cloudflare?
https://blog.cloudflare.com/fail-small-resilience-plan/
https://blog.cloudflare.com/fail-small-resilience-plan/
The Cloudflare Blog
Code Orange: Fail Small — our resilience plan following recent incidents
We have declared “Code Orange: Fail Small” to focus everyone at Cloudflare on a set of high-priority workstreams with one simple goal: ensure that the cause of our last two global outages never happens again.
🤣4👍2🔥1
A set of modern Grafana dashboards for Kubernetes.
https://github.com/dotdc/grafana-dashboards-kubernetes
https://github.com/dotdc/grafana-dashboards-kubernetes
GitHub
GitHub - dotdc/grafana-dashboards-kubernetes: A set of modern Grafana dashboards for Kubernetes.
A set of modern Grafana dashboards for Kubernetes. - dotdc/grafana-dashboards-kubernetes
👍7💩1
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
https://terrateam.io/blog/build-vs-buy-terraflow-case-study
Terrateam
function noscript(pageContext) {
const { post } = pageContext.data;
return (post == null ? void 0 : post.seoTitle) || (post ==…
const { post } = pageContext.data;
return (post == null ? void 0 : post.seoTitle) || (post ==…
function denoscription(pageContext) {
const { post } = pageContext.data;
return (post == null ? void 0 : post.denoscription) || "Blog post from Terrateam";
}
const { post } = pageContext.data;
return (post == null ? void 0 : post.denoscription) || "Blog post from Terrateam";
}
👍4❤2
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/
https://fatihkoc.net/posts/opentelemetry-kubernetes-pipeline/
Fatih Koç
Building a Unified OpenTelemetry Pipeline in Kubernetes
Deploy OpenTelemetry Collector in Kubernetes to unify metrics, logs, and traces with correlation, smart sampling, and insights for faster incident resolution.
👍5
This documentation demystifies the structure of Kubernetes YAML files by breaking them down into their three core components:
https://medium.com/@thisara.weerakoon2001/demystifying-kubernetes-yaml-ef9e92acf3df
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
Medium
Demystifying Kubernetes YAML
In the world of Kubernetes, YAML files are the bread and butter. They are the declarative way you tell Kubernetes what you want your…
👍3
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
https://medium.com/doubleverify-engineering/a-case-study-in-synchronizing-database-schema-updates-between-projects-and-environments-a69a3cc38985
Medium
A Case Study in Synchronizing Database Schema Updates between Projects and Environments
Written By: Chaim Leichman
👍3❤2
eBPF based cloud-native load-balancer for Kubernetes|Edge|Telco|IoT|XaaS.
https://github.com/loxilb-io/loxilb
https://github.com/loxilb-io/loxilb
GitHub
GitHub - loxilb-io/loxilb: eBPF based cloud-native load-balancer for Kubernetes|Edge|Telco|IoT|XaaS.
eBPF based cloud-native load-balancer for Kubernetes|Edge|Telco|IoT|XaaS. - loxilb-io/loxilb
👍2🔥1
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.
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.
👍5🔥3👏2