[Feat] Deploy backend and mongodb service to Kubernetes

[Raffone17]

No description provided.

[gmacario]

@Raffone17 thanks for your contribution.
In the next days I will give it a try on another Kubernetes cluster and will report my findings.

However for the time being would you be able to sanitize your PR and have Super-Linter pass?
It looks like most of the errors come from the Helm chart templates.
Please have a look at related #7

[gmacario]

Testing PR on cluster rfid-staging

Logged in as root@rfid-staging

mkdir -p ~/github/aquariophilie
cd ~/github/aquariophilie
git clone https://github.com/aquariophilie/node-koa-boilerplate
cd node-koa-boilerplate
git checkout feature/5-deploy-application-to-kubernetes

Result:

root@rfid-webapp-staging:~# mkdir -p ~/github/aquariophilie
root@rfid-webapp-staging:~# cd ~/github/aquariophilie/
root@rfid-webapp-staging:~/github/aquariophilie# git clone https://github.com/aquariophilie/node-koa-boilerplate
Cloning into 'node-koa-boilerplate'...
remote: Enumerating objects: 176, done.
remote: Counting objects: 100% (176/176), done.
remote: Compressing objects: 100% (145/145), done.
remote: Total 176 (delta 52), reused 117 (delta 16), pack-reused 0
Receiving objects: 100% (176/176), 155.52 KiB | 9.15 MiB/s, done.
Resolving deltas: 100% (52/52), done.
root@rfid-webapp-staging:~/github/aquariophilie# cd node-koa-boilerplate/
root@rfid-webapp-staging:~/github/aquariophilie/node-koa-boilerplate# git checkout feature/5-deploy-application-to-kubernetes
Branch 'feature/5-deploy-application-to-kubernetes' set up to track remote branch 'feature/5-deploy-application-to-kubernetes' from 'origin'.
Switched to a new branch 'feature/5-deploy-application-to-kubernetes'
root@rfid-webapp-staging:~/github/aquariophilie/node-koa-boilerplate#

Install helm

snap install helm --classic

Now follow the instructions in toplevel README.md

cd chart
helm install my-release koa-mongo-k8s

Result:

root@rfid-webapp-staging:~/github/aquariophilie/node-koa-boilerplate/chart# helm install my-release koa-mongo-k8s
NAME: my-release
LAST DEPLOYED: Thu Apr 28 18:23:47 2022
NAMESPACE: default
STATUS: deployed
REVISION: 1
NOTES:
1. Get the application URL by running these commands:
  export NODE_PORT=$(kubectl get --namespace default -o jsonpath="{.spec.ports[0].nodePort}" services my-release-koajs-k8s)
  export NODE_IP=$(kubectl get nodes --namespace default -o jsonpath="{.items[0].status.addresses[0].address}")
  echo http://$NODE_IP:$NODE_PORT
root@rfid-webapp-staging:~/github/aquariophilie/node-koa-boilerplate/chart#

Verify using k9s that service my-release-koajs-k8s is up and running

Notice that the URL (http://$NODE_IP:$NODE_PORT) returned by the commands shown in the terminal is different from what reported by k9s:

root@rfid-webapp-staging:~/github/aquariophilie/node-koa-boilerplate/chart# export NODE_PORT=$(kubectl get --namespace default -o jsonpath="{.spec.ports[0].nodePort}" services my-release-koajs-k8s)
root@rfid-webapp-staging:~/github/aquariophilie/node-koa-boilerplate/chart#   export NODE_IP=$(kubectl get nodes --namespace default -o jsonpath="{.items[0].status.addresses[0].address}")
root@rfid-webapp-staging:~/github/aquariophilie/node-koa-boilerplate/chart#   echo http://$NODE_IP:$NODE_PORT
http://10.0.0.4:32498
root@rfid-webapp-staging:~/github/aquariophilie/node-koa-boilerplate/chart#

TODO: Figure out how to publicly access the backend API URL

[gmacario]

TODO: Figure out how to publicly access the backend API URL

For The Records: I managed to access the backend API URL using Lens - The Kubernetes IDE using the following procedure:

• Launch Lens and connect to the Kubernetes cluster (in our case,"rfid-staging")

  

• Select Network > Services

  

• Click on service "my-release-koajs-k8s" and look at section "Connection"

  

• Click on the port (in our case, "4000:32498/TCP". This will open a browser tab on http://localhost:63234 which is the API endpoint forwarded to localhost

  

• You may edit the URL in the browser to access other API on the same endpoint, for instance http://localhost:6234/api/status

  

[gmacario]

@Raffone17 I believe I sorted out the problems which made Super-Linter fail, please review and merge #11

[gmacario]

I made a couple of cosmetic fixes.

Apart from that, LGTM.