Optional - yet recommanded:
kubectx + kubens
callable via thekubens
binaryKustomize
chromium
callable via thechromium
binary
Deploy a microservice architecture app
- redis
- api (./src/api)
- consumer (./src/pinger)
- client (./src/poller)
- Use
redis
to store pings, usingredis:latest@sha256:a89cb097693dd354de598d279c304a1c73ee550fbfff6d9ee515568e0c749cfe
to ensure these LAB's function as expected altoughlatest
should work ;) - To disable redis authentication Use
nodejs-ping
with tagno-auth
orlatest@sha256:85d7474aabdd2d01802a9957c770ec157a478db71b7ce5f8d07d1e221cc39cba
see thedocker-compose-no-auth.yml
- Pinger & Poller are just 2 clients using
latest
tag should suffice.
In order to test you have everything docker-compose build
will buid all images locally,
A functional a docker-compose up
should build/pull the required images.
1๏ธโฃ prep
k3d cluster delete nodejs-demo
k3d cluster create nodejs-demo
kubectl cluster-info
Should yield somthing like the following:
Kubernetes control plane is running at https://0.0.0.0:52951
CoreDNS is running at https://0.0.0.0:52951/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
Metrics-server is running at https://0.0.0.0:52951/api/v1/namespaces/kube-system/services/https:metrics-server:/proxy
To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
๐ next deploy - redis