Running Microservices on Kubernetes – Best Practices

on YouTube ↗28m

" summary

Recommends using managed Kubernetes like EKS/AKS/GKE or on‑prem OpenShift/Rancher, enforcing namespaces with resource quotas and RBAC, and preferring one container per pod except for injected sidecars. Specifies health checks: liveness/readiness/startup probes (use different endpoints to avoid restart loops and add shutdown delay), set sensible CPU/memory requests and limits, and spread replicas with anti‑affinity. Advocates shifting security left with image scans (Black Duck/Checkmarx), runtime secrets (CyberArk) and private registries (JFrog Artifactory), and using HPA + Prometheus and service mesh (Linkerd) for observability and scaling.

AI-written summary · about

" related talks

• 49mDeveloping microservices applications on the Kubernetes platformShahid Iqbal · NDC Sydney 2018
• 19mKube Me This! Kubernetes Ideas and Best PracticesKarthik Gaekwad · Agile India 2020
• 57mMicroservices with KubernetesFernando Guerra · Kubernetes Community Days Guatemala 2021
• 59mA DevOps State of Mind: Managing Microservices + Databases with KubernetesChris Van Tuin · Windcity DevFest 2019
• 44mTop 5 container and Kubernetes best practicesGrace Andrews · AWS re:Invent 2019
• 35mAdvanced Microservices ArchitecturesChin Hong Hua · FOSSASIA Summit 2020
• 37mKnee Deep in MicroservicesÁdám Sándor · MesosCon Europe 2017
• 45mKube Me This! Kubernetes Ideas and Best PracticesKarthik Gaekwad · Oracle Code One 2018