Find vulnerabilities, misconfigurations, secrets, SBOM in containers, Kubernetes, code repositories, clouds and more

https://github.com/aquasecurity/trivy

kubectl plugin to list allocations (cpu, memory, gpu,... X utilization, requested, limit, allocatable,...)

https://github.com/davidB/kubectl-view-allocations

Interesting article about working with k8s that was located on bare-metal

https://medium.com/geekculture/a-retrospective-of-working-with-bare-metal-kubernetes-or-to-there-and-back-1868c0356eff

Automatically monitor your local dev environment (services, repos, and more)

https://github.com/tylermumford/localstatus

An operator for running distributed k6 tests.

https://github.com/grafana/k6-operator

Example of using n8n platform in the incident management https://touilleio.medium.com/alertmanager-incident-response-automation-with-n8n-c61227e196e9

Comprehensive guide for RBAC in K8s https://learnk8s.io/rbac-kubernetes

Now in its fifth year, The SRE Report has become the trusted source of trends and insights for reliability-as-a-feature practices. This year in partnership with Blameless, the report contains special contributions from Adrian Cockcroft and Steve McGhee and highlights findings from a global community of reliability practitioners, including SREs, managers, architects, and executives. As ever, we found some familiar trends and some thought-provoking anti-patterns.

Key findings include:

Organizations who operate with a “just culture” are 500% more likely to be Elite performing organizations. ‍
Elite-performing organizations are 260% more likely to substantially focus on Customer Experience reliability versus Low-performing organizations.
Organizations (59%) say that maintaining innovation velocity occasionally or often impacts employee productivity or morale – 14% unsure.
Organizations (59%) say tool sprawl is a non-existent or minor problem – challenges other research which simply equates tool sprawl to, ‘how many tools are in the stack’.

kubectl plugin to dump example helper resource templates

https://github.com/trstringer/kubectl-example

EKS Node Viewer is a tool for visualizing dynamic node usage within a cluster. It was originally developed as an internal tool at AWS for demonstrating consolidation with Karpenter. It displays the scheduled pod resource requests vs the allocatable capacity on the node. It does not look at the actual pod resource usage.

https://github.com/awslabs/eks-node-viewer

Monitor a process and trigger a notification.

https://github.com/variadico/noti