Kubernetes and the 12 factor cloud apps
0 likes•254 views
The document discusses how the twelve factors of cloud applications and Kubernetes help applications evolve for cloud environments. It covers each of the twelve factors - like codebase, dependencies, configuration as code, backing services as attached resources, separating build and run stages, exporting via port binding, scaling via processes, fast startup and graceful shutdown, keeping development and production similar, treating logs as streams, and one-off admin processes. The key takeaways are to decouple infrastructure complexity, prefer managed services, keep environments similar, design applications stateless and able to scale, and monitor appropriately.
Kubernetes and the 12 factor cloud apps
- 1. Kubernetes & the 12 factors cloud applications Ana Maria Mihalceanu #JBCNConf2019
- 2. @ammbra1508#vJUG HELLO! I am Ana Technical Lead @ IBM Co-founder of Bucharest Software Craftsmanship Community
- 3. Why 12 factors & Kubernetes? @ammbra1508#vJUG
- 4. Why 12 factors & Kubernetes? @ammbra1508#vJUG Evolution Declarative formats
- 5. Why 12 factors & Kubernetes? @ammbra1508#vJUG Run at push of a button Evolution Declarative formats Scale up with minimal changes Declarative formats Scale up with minimal changes
- 6. Why 12 factors & Kubernetes? @ammbra1508#vJUG Portability Run at push of a button Evolution Declarative formats Scale up with minimal changes Clean Contract
- 7. Why 12 factors & Kubernetes? @ammbra1508#vJUG PortabilityLocal vs production Run at push of a button Evolution Declarative formats Scale up with minimal changes Clean Contract Continuous deployment
- 9. FACTOR 1 - CODEBASE @ammbra1508#vJUG One codebase tracked in revision control, with multiple deployments.
- 11. FACTOR 1 - CODEBASE @ammbra1508#vJUG HELM v2.x.y
- 13. FACTOR 2 - DEPENDENCIES @ammbra1508#vJUG Explicitly declare and isolate dependencies.
- 14. FACTOR 2 - DEPENDENCIES @ammbra1508#vJUG { "name": "fed", "version": "1.0.0", "dependencies": { "ejs": "^2.6.1", "express": "^4.16.3", "req-flash": "0.0.3", "request": "2.81.0" } }
- 15. FACTOR 2 - DEPENDENCIES @ammbra1508#vJUG apiVersion: apps/v1 kind: Deployment metadata: name: dreamhome-web labels: app: dreamhome-web tier: frontend
- 16. FACTOR 2 - DEPENDENCIES @ammbra1508#vJUG apiVersion: apps/v1 kind: Deployment metadata: name: dreamhome-web labels: app: dreamhome-web tier: frontend spec: replicas: 2 selector: matchLabels: app: dreamhome-web
- 17. FACTOR 2 - DEPENDENCIES @ammbra1508#vJUG apiVersion: apps/v1 kind: Deployment metadata: name: dreamhome-web labels: app: dreamhome-web tier: frontend spec: replicas: 2 selector: matchLabels: app: dreamhome-web template: metadata: labels: app: dreamhome-web tier: frontend implementation: nodejs
- 18. FACTOR 3 - CONFIGURATION @ammbra1508#vJUG
- 19. FACTOR 3 - CONFIGURATION @ammbra1508#vJUG Store configuration in the environment. kubectl create secret docker-registry ${SECRET_NAME} --namespace ${CLUSTER_NAMESPACE} --docker-server=${REGISTRY} --docker-username=iamapikey --docker-password=${TOKEN} [email protected]
- 20. FACTOR 3 - CONFIGURATION @ammbra1508#vJUG Store configuration in the environment. kubectl create secret docker-registry ${SECRET_NAME} --namespace ${CLUSTER_NAMESPACE} --docker-server=${REGISTRY} --docker-username=iamapikey --docker-password=${TOKEN} [email protected]
- 21. FACTOR 4 – BACKING SERVICE @ammbra1508#vJUG
- 22. Treat backing services as attached resources. FACTOR 4 – BACKING SERVICE @ammbra1508#vJUG apiVersion: v1 kind: Secret metadata: name: cloudant type: Opaque data: binding: {}
- 23. FACTOR 4 – BACKING SERVICE @ammbra1508#vJUG Treat backing services as attached resources. apiVersion: v1 kind: Secret metadata: name: cloudant type: Opaque data: binding: {}
- 24. FACTOR 4 – BACKING SERVICE @ammbra1508#vJUG Treat backing services as attached resources. apiVersion: v1 kind: Secret metadata: name: cloudant type: Opaque data: binding: {}
- 25. FACTOR 5 – BUILD, RELEASE, RUN @ammbra1508#vJUG
- 26. FACTOR 5 – BUILD, RELEASE, RUN @ammbra1508#vJUG Strictly separate build and run stages.
- 27. FACTOR 5 – BUILD, RELEASE, RUN @ammbra1508#vJUG
- 29. FACTOR 6 – PROCESSES @ammbra1508#vJUG Execute the app as one or more stateless processes. Container Filesystem Persistent VolumeVolume
- 30. FACTOR 6 – PROCESSES @ammbra1508#vJUG kubectl apply –f ${CREATE_VOLUME}.yaml kubectl apply –f ${COPY_SCRIPTS_POLLER}.yaml kubectl cp ./scripts ${POD}:/${LOCATION} kubectl apply –f ${USE_SCRIPTS}.yaml
- 31. FACTOR 7 – PORT BINDING @ammbra1508#vJUG kubectl apply –f ${FILE}
- 32. FACTOR 7 – PORT BINDING @ammbra1508#vJUG Export services via port binding.
- 33. FACTOR 7 – PORT BINDING @ammbra1508#vJUG Export services via port binding. kubectl expose deployment/${NAME} --type=”${SERVICE_TYPE}” --name=${SERVICE_NAME}
- 34. FACTOR 8 – CONCURRENCY @ammbra1508#vJUG Scale out via the process model.
- 35. FACTOR 8 – CONCURRENCY @ammbra1508#vJUG Scale out via the process model.
- 36. FACTOR 8 – CONCURRENCY @ammbra1508#vJUG kubectl autoscale deployment {$DEPLOYMENT} --min=${MIN_PODS} --max=${MAX_PODS} --cpu-percent=${CPU} --namespace=${NAMESPACE}
- 37. FACTOR 8 – CONCURRENCY @ammbra1508#vJUG kubectl autoscale deployment {$DEPLOYMENT} --min=${MIN_PODS} --max=${MAX_PODS} --cpu-percent=${CPU} --namespace=${NAMESPACE} 𝐝𝐞𝐬𝐢𝐫𝐞𝐝𝐑𝐞𝐩𝐥𝐢𝐜𝐚𝐬 = ceil(currentReplicas × currentMetricValue 𝐝𝐞𝐬𝐢𝐫𝐞𝐝𝐌𝐞𝐭𝐫𝐢𝐜𝐕𝐚𝐥𝐮𝐞 )
- 38. FACTOR 9 – DISPOSABILITY @ammbra1508#vJUG Fast startup Graceful shutdown Maximize robustness with
- 39. FACTOR 9 – DISPOSABILITY @ammbra1508#vJUG Application boot time
- 40. FACTOR 9 – DISPOSABILITY @ammbra1508#vJUG Rolling update one after another
- 42. FACTOR 10 – DEV PROD PARITY @ammbra1508#vJUG Time People Tools
- 43. FACTOR 10 – DEV PROD PARITY @ammbra1508#vJUG Keep development, staging and production as similar as possible. kubectl create namespace ${NAMESPACE}
- 44. FACTOR 11 – LOGS @ammbra1508#vJUG
- 45. FACTOR 11 – LOGS @ammbra1508#vJUG Treat logs as event streams. kubectl create secret generic logdna-agent-key --from-literal=logdna-agent-key=<ingestion_key> kubectl create -f https://repo.logdna.com/ibm/prod/logdna-agent-ds- us-south.yaml
- 46. FACTOR 12 – ADMIN PROCESSES @ammbra1508#vJUG Run admin/management tasks as one-off processes. kubectl create configmap ${CONFIG} --from-file=scripts/ -o yaml kubectl apply –f ${ONE_TIME_JOB_CONFIGURATION}
- 48. @ammbra1508#vJUG TAKEAWAYS Decouple Decouple infrastructure complexity from your application code. Managed Services Prefer managed services in matters involving persistency. Environment Parity Keep your environments as similar as possible.
- 49. @ammbra1508#vJUG TAKEAWAYS Stateless Design your application as stateless. Scale Your application should be able to process diverse workloads. Monitor Use appropriate logging in application code and implement cluster-level logging.
- 50. @ammbra1508#vJUG The strongest factor for success is self-esteem. Believing you can do it, believing you deserve it, believing you will get it. Anonymous “ “