[Summary, full note in Shaarli]
Approach: a startup taint plus the Node Readiness Controller (https://github.com/kubernetes-sigs/node-readiness-controller). No fixed sleep; keep NodeReady separate from workload initialization.
Limits: NoSchedule doesn't evict running workloads (needs a separate policy). Docs: https://node-readiness-controller.sigs.k8s.io/user-guide/getting-started.html , https://karpenter.sh/docs/concepts/nodepools/
via martinho
I had no idea such cache exists, very interesting!
[Summary, full note in Shaarli]
Notice AWS : migration PodSecurityPolicy (PSP) avant EKS / Kubernetes 1.25.
Réfs :
https://docs.aws.amazon.com/eks/latest/userguide/pod-security-policy-removal-faq.html
https://kubernetes.io/docs/concepts/security/pod-security-standards/
https://kubernetes.io/docs/concepts/security/pod-security-admission/
https://kubernetes.io/docs/tasks/configure-pod-container/migrate-from-psp/
https://aws.github.io/aws-eks-best-practices/security/docs/pods/#pod-security-standards-pss-and-pod-security-admission-psa
https://aws.github.io/aws-eks-best-practices/security/docs/pods/#policy-as-code-pac
https://aws.amazon.com/blogs/containers/implementing-pod-security-standards-in-amazon-eks/
https://kubernetes.io/blog/2021/04/06/podsecuritypolicy-deprecation-past-present-and-future/
https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#securitycontext-v1-core
https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#podsecuritycontext-v1-core
https://github.com/open-policy-agent/gatekeeper/
https://www.openpolicyagent.org/docs/latest/kubernetes-tutorial/
Karpenter vs Cluster Autoscaler very well explained in 7minutes
Alternative to helmfile
Server Side apply VS Client Side apply
via Edwin
Un Operator qui :
- crée des CRDs pour chaque resource AWS existante (s3, ec2, rds.....)
- crée les controler associés
Du coup on peut créer des resources AWS avec kube (on peut se passer de terraform, on peut utiliser une CI/CD adaptée à déployer dans Kube)
https://medium.com/omio-engineering/cpu-limits-and-aggressive-throttling-in-kubernetes-c5b20bd8a718
https://blog.turbonomic.com/kubernetes-cpu-throttling-the-silent-killer-of-response-time-and-what-to-do-about-it
https://erickhun.com/posts/kubernetes-faster-services-no-cpu-limits/
https://engineering.indeedblog.com/blog/2019/12/unthrottled-fixing-cpu-limits-in-the-cloud/
https://www.youtube.com/watch?v=UE7QX98-kO0
Petit point vocabulaire : un "Operator" est un "controller" qui va surveiller des CRD (Custom Resource Definition) pour faire des actions
Un Operator = 1 deployment = x Pods qui écoutent via l'API de Kube les events sur une CRD et va faire des actions en conséquence
Gérer des resources aws avec un controller kube fourni par aws