Skip to content

Latest commit

 

History

History
213 lines (149 loc) · 5.13 KB

DEPLOY_TO_MINIKUBE.md

File metadata and controls

213 lines (149 loc) · 5.13 KB
Raw

Deploy to Minikube

First, Give minikube driver(docker, virtualbox, ...) enough resources.

Launch Minikube

Run the following script to start minikube.

tools/scripts $ minikube-start.sh

The dirver, system resources, etc. are specified in minikube-start.sh, so modify them to suit your preferences (but be sure to reserve the resources required by Deployment).

Change the Docker client connection to minikube.

tools/scripts $ eval $(minikube docker-env default)

Push the Docker Image

Please push the image to docker registry on minikube.

tools/scripts $ ./sbt-publish-local.sh

Edit the Configuration file of Helmfile

tools/scripts $ vi ../config/environments/${PREFIX}-${APPLICATION_NAME}-local.yaml
adceet-root # tools/config/environments/${PREFIX}-${APPLICATION_NAME}-local.yaml

Notice the tag value displayed in the console; reflect it in xxx.image.tag. Please set the following items in the yaml file appropriately

  • writeApi.writeApiServer.frontend.image.repository
  • writeApi.writeApiServer.frontend.image.tag
  • writeApi.writeApiServer.backend.image.repository
  • writeApi.writeApiServer.backend.image.tag

Set the following items in the yaml file appropriately(if you use Read API Server)

  • readModelUpdater.image.repository
  • readModelUpdater.image.tag
  • readApiServer.image.repository
  • readApiServer.image.tag

NOTE

All components can be deployed with a single command below, but it is recommended that you run each step at least once to get a feel for the process.

tools/scripts $ ./helmfile-apply-local-all.sh

Prepare DynamoDB tabels

Next deploy dynamodb local.

tools/scripts $ ./helmfile-apply-local-dynamodb.sh

Create the necessary tables.

tools/scripts $ ./helmfile-apply-local-dynamodb-setup.sh

Open http://127.0.0.1:31567/ if you want to use DynamoDB Admin.

Prepare MySQL tabels

Next deploy mysql.

tools/scripts $ ./helmfile-apply-local-mysql.sh

Create the necessary tables.

tools/scripts $ ./helmfile-apply-local-flyway.sh

About akka-cluster roles

Deploy the Backend role

Next deploy the backend roles.

tools/scripts $ ./helmfile-apply-local-backend.sh

Wait a few moments for the cluster to form. Make sure there are no errors in the log.

$ stern 'write-api-server-backend-*' -n adceet

Make sure all pods are in Ready status.

Deploy the Frontend role

if choose the configuration 1, deploy the frontend role.(if choose the configuration 2, Do not run this command)

tools/scripts $ ./helmfile-apply-local-frontend.sh

Wait a few moments for the cluster to form. Make sure there are no errors in the log.

$ stern 'write-api-server-frontend-*' -n adceet

Make sure all pods are in Ready status.

Deploy Read Model Updater (if you need)

Next deploy Read Model Updater.

tools/scripts $ ./helmfile-apply-local-rmu.sh

Wait a few moments. Make sure there are no errors in the log.

$ stern 'read-model-updater-*' -n adceet

Deploy Read API Server (if you need)

Next deploy Read API Server

tools/scripts $ ./helmfile-apply-local-read-api.sh

Wait a few moments. Make sure there are no errors in the log.

$ stern 'read-api-server-*' -n adceet

Check the applications

After frontend is started, check the operation with the following commands.

$ curl -X GET http://127.0.0.1:30031/hello
Say hello to akka-http

Call API to check operation.

$ curl -v -X POST -H "Content-Type: application/json" -d "{ \"accountId\": \"01G41J1A2GVT5HE45AH7GP711P\" }" http://127.0.0.1:30031/threads
Note: Unnecessary use of -X or --request, POST is already inferred.
*   Trying 127.0.0.1:30031...
* Connected to localhost (127.0.0.1) port 30031 (#0)
> POST /threads HTTP/1.1
> Host: localhost:30031
> User-Agent: curl/7.79.1
> Accept: */*
> Content-Type: application/json
> Content-Length: 45
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Server: akka-http/10.2.9
< Date: Fri, 26 Aug 2022 08:42:39 GMT
< Content-Type: application/json
< Content-Length: 41
<
* Connection #0 to host localhost left intact
{"threadId":"01GBCN25M496HB4PK9EWQMH28J"}

NOTE: In a local environment, the first event may not consume well. If this is the case, try sending the command again.

Execute the following command if you use RMU and Read API Server.

$ curl -v -H "Content-Type: application/json" http://127.0.0.1:30033/threads?owner_id=01G41J1A2GVT5HE45AH7GP711P
*   Trying 127.0.0.1:30033...
* Connected to localhost (127.0.0.1) port 30033 (#0)
> GET /threads?owner_id=01G41J1A2GVT5HE45AH7GP711P HTTP/1.1
> Host: localhost:30033
> User-Agent: curl/7.79.1
> Accept: */*
> Content-Type: application/json
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Server: akka-http/10.2.9
< Date: Tue, 25 Oct 2022 07:59:31 GMT
< Content-Type: application/json
< Content-Length: 123
<
* Connection #0 to host localhost left intact
[{"id":"01GG72CT9B62DRMH31F8SQX3H9","owner_id":"01G41J1A2GVT5HE45AH7GP711P","created_at":"2022-10-25T07:58:31.096808590Z"}]%