- Make sure that your docker pulls from dockerhub...idk how to ensure that.
- Clone this repo and run
make initmake upto start the app, runmake endmake downto teardown the app - If you have kubernetes, kind, and helm installed:
make installto startup pods and servicemake revealto expose the service (and app) atlocalhost:6060make uninstallto teardown pod and service
- Send a request to http://localhost:6060/monkeys
- This will contact goDocker container which will return "Hi there, I love monkeys! and hello boy, 3:44PM" (or whatever current time is)
- The Go container will contact the nodeDocker container which will add logs with the time in src/log/access.log
- view the log by entering the container with
docker exec -it nodeDocker bashand navigate to the log
- view the log by entering the container with
- Made some changes to each server's docker image to make it smaller
- nodeDocker now uses node:alpine base over node:latest
- original: >1GB using node:latest
- current: ~220MB using node:alpine
- goDocker now uses multistage docker with final image just being the server as binary in alpine
- original: 700MB -> golang:onbuild
- current: 12MB -> golang:alpine to build binary in stage 1, copy binary into alpine base stage 2
- nodeDocker now uses node:alpine base over node:latest
- Added docker-compose which can be implemented with
make upand torn down withmake down - Working on running this in kubernetes
- Done:
- Deployment.yaml for
JUSTthe node app and go app - Service.yaml for
JUSTthe node app and go app Contact the app via kubectl proxy- Can I contact the app outside of kubectl proxy?
kubectl port-forward svc/go-node-kube 6060:80- This will forward the service to be exposed at
localhost:6060
- Modified GoApp so that it checks the HOST env variable to determine target URL.
localhostnodeappin Kubernetes- Moved Golang container and NodeJS container into separate pods with corresponding services
nodedockerin Docker-Compose
- Deployment.yaml for
- Done: