PROJECT DOSSIER // [BERNSTEIN]VIEW SOURCE BACK TO PROJECTS →

01 // PROJECT AT A GLANCE

BERNSTEIN

YAML

Moving from containers you launch to a cluster that keeps them alive by itself.

A direct sequel to the previous project, with a paradigm shift: instead of describing how to launch containers, you describe the desired state of the system and the cluster takes care of reaching it and staying there. If a component goes down, it is restarted; if load increases, more are added. The title refers to the conductor — orchestration, precisely.

Deploying the voting application on Kubernetes: manifests for deployments, services, a Traefik ingress, configmaps, secrets, a persistent volume and cAdvisor monitoring.

PRIMARYYAML

DELIVERYTEAM RECORD

VERIFICATIONkubectl

SOURCEINSPECTOR READY

MEDIA ATTACHMENTS (Images, Photos, Videos)

02 // PROJECT SIGNALS

DATE:: 2020
PRIMARY LANG:: YAML
GRADE:: A
DURATION:: 2 weeks
SECONDARY:: —
STACK:: kubectl / Docker

03 // KEY OUTCOMES

Moving from imperative infrastructure to declarative, self-healing infrastructure
Secrets and configuration properly separated, unlike the docker-compose version
Persistence and monitoring handled in an environment of ephemeral containers

BEYOND THE BRIEF

Monitoring through cAdvisor as a daemonset, beyond simply deploying the application
Kubernetes secrets used for the database credentials rather than plaintext variables

04 // SOURCE TREE

READING SOURCE…

Loading…