Ajin Ibrahim

⚠️ The ESO (External Secrets Operator) for #Kubernetes project is on hold. No new releases. No patches. No container images. Why? Because the maintainer team is too small and burned out. Only one active maintainer is left. When he was on vacation, nothing moved forward. The project still accepts community PRs, but there is no official support. No Slack. No GitHub Discussions. And NO new versions until at least five active maintainers step up. If your company uses External Secrets in production, now is the time to contribute. Do not just think about money or donations. What matters more is time. Ask your company if you can contribute during work hours. This is not just someone else’s problem. ESO is one of the standard tools to get secrets from stores like AWS Secrets Manager, Azure Key Vault or HashiCorp Vault into a Kubernetes cluster. Without more people, the project might move into maintenance mode or even be archived. The message from the maintainers is clear: Either we grow the team or we scale back expectations. What do you think? Does your company rely on External Secrets? Would you or your team be ready to help maintain it? Repost this to increase the reach of this important message. 👉 Follow the thread on GitHub: https://lnkd.in/dFT5RXJx 👉 Ready to contribute? Fill out the google forms here: https://lnkd.in/dq8ubA7r If you ask why I cannot help here: I already contribute my free available time as maintainer to the #Prometheus and #Grafana community.

1.777

106 Kommentare

Most Kubernetes outages aren’t complex. They’re just dumb. So I built a 𝗞𝘂𝗯𝗲𝗿𝗻𝗲𝘁𝗲𝘀 𝗦𝗮𝗻𝗶𝘁𝘆 𝗣𝗮𝗰𝗸 with 10 𝗼𝗻𝗲-𝗹𝗶𝗻𝗲𝗿𝘀 that instantly catch the dumb stuff before it nukes your app. Here’s your checklist. I run these before every war room. 1. Find crash loops fast kubectl get pods --all-namespaces | grep CrashLoopBackOff 2. What’s spamming your event logs? kubectl get events --sort-by='.lastTimestamp' | tail -n 20 3. App down? Maybe your probe is misfiring. kubectl describe pod <pod-name> | grep -i "probe" 4. Service with no backing pods = silent fail kubectl get endpoints -A | grep -v "ENDPOINTS" 5. Spot stuck deployments kubectl rollout status deployment/<name> --watch 6. Find restarts > 3 (your quiet troublemakers) kubectl get pods --all-namespaces --field-selector=status.phase=Running | awk '$5 > 3' 7. Is the node low on disk or memory? kubectl describe node <node-name> | grep -A5 "Non-terminated Pods:" 8. What killed your pod? kubectl describe pod <pod-name> | grep -A10 "State:" 9. Secret or configmap typo? Check the mounts. kubectl describe pod <pod-name> | grep -i "Volumes:" 10. Most common one: bad image pull. kubectl get pods | grep ImagePullBackOff Run this once a week. Or better, automate it. Most of these catch issues before Prometheus alerts even fire. What’s your go-to one-liner that saved your a** on a Friday night deploy?

110

7 Kommentare

🔥 Most people using Kubernetes don't actually understand how it works. They write YAML and run kubectl apply, but when things break, they're lost. The secret? Controllers are the beating heart of K8s. This video breaks down how they really work 👇 https://lnkd.in/dYxw2dxg

217

7 Kommentare

Do you need to use Alpha features of Kubernetes on #GKE? You can create an Alpha Cluster with the --enable-kubernetes-alpha flag for gcloud. This is not new! What is new is the ability to enable only certain alpha features! With the --alpha-cluster-feature-gates flag, you can decide which alpha features to enable depending on your needs. This can help you ensure the stability of the cluster and test upcoming #Kubernetes features. https://lnkd.in/efWQqt7U https://lnkd.in/eUtx5jVG

40