Msstarter2

• Simple and Minimal starter 2 for spring boot microservices and angular js .
• Look for previos for more integration options
• With and without docker and kubernetes (using K3S)
• Explanation - Just picture. The rest for information read bellow
• 28-Jul-2020 Bump spring boot and cloud versions

Run options

• On local station using regular java applications
• Inside vagrant box with k8s and docker ( require some adition steps)

Build steps for local station

• For local station just create rest-st-2 in hosts file and point to 127.0.0.1 Example ** 127.0.0.2 rest-st-2 **
• The rest-st-2 used inside vagrant and for separate java apps as well
• Do following

     clone https://github.com/iazarny/msstarter2.git
     cd msstarter2
     mvn clean install
     cd springgw
     mvn install fabric8:build fabric8:push
     cd ../springrest
     mvn install fabric8:build fabric8:push

• Run both projects - spring gw and sting rest

Checks

• Rest service. Open following urls.

URL	Result
http://rest-st-2:22222/	Greetings from Spring Boot!
http://rest-st-2:22222/api	Api module presented
http://rest-st-2:22222/api/todos	[{"id":1,"title":"Have","completed":false},{"id":2,"title":" some","completed":true},{"id":3,"title":" fun","completed":false}]

• Gateway service delegates mostly all calls to rest-st-2:22222
• So need to to check

URL	Result
http://localhost:20000/api/todos	[{"id":1,"title":"Have","completed":false},{"id":2,"title":" some","completed":true},{"id":3,"title":" fun","completed":false}]

• At least on http://localhost:20000/api/todos you have to see following TODO application

Build steps for Vagrant

cd vagrant
vagrant up
vagrant ssh

sudo su -
git clone https://github.com/iazarny/msstarter2.git
cd msstarter2
mvn clean install
cd springgw
mvn install fabric8:build fabric8:push
cd ../springrest
mvn install fabric8:build fabric8:push
cd ..
kubectl create -f k8s/deploy-all.yml

Expose to external IP address

Expose service(s) on some IP addresses in our case 172.28.128.62 The ip address to access from host machine to vagrant box using tpc/ip. Actually gw-st-2 is enough, because some part it delegates, some part it handle

[root@minikube msstarter2]# kubectl get rs -A
NAMESPACE     NAME                   DESIRED   CURRENT   READY   AGE
default       gw-st-2-ddc88dd9       1         1         1       9m2s
default       rest-st-2-7b767bf688   1         1         1       9m2s
kube-system   coredns-b7464766c      1         1         1       37m
kube-system   traefik-5c79b789c5     1         1         1       36m

kubectl expose rs gw-st-2-ddc88dd9       --port=20000  --target-port=20000 --name=ext-gw-st-2    --external-ip=172.28.128.63
kubectl expose rs rest-st-2-7b767bf688   --port=22222  --target-port=22222 --name=ext-rest-st-2  --external-ip=172.28.128.63

Check steps far Vagrant

The same as for sping app from host machine

The picture shall be similar

[root@minikube springgw]# kubectl get all
NAME                             READY   STATUS    RESTARTS   AGE
pod/gw-st-2-ddc88dd9-4kcss       1/1     Running   0          15m
pod/rest-st-2-7b767bf688-z4pnb   1/1     Running   0          13h
pod/svclb-gw-st-2-85lkl          1/1     Running   0          15m
pod/svclb-rest-st-2-7zc4g        1/1     Running   0          13h

NAME                    TYPE           CLUSTER-IP      EXTERNAL-IP     PORT(S)           AGE
service/ext-gw-st-2     ClusterIP      10.43.188.203   172.28.128.63   20000/TCP         2m
service/ext-rest-st-2   ClusterIP      10.43.33.93     172.28.128.63   22222/TCP         13h
service/gw-st-2         LoadBalancer   10.43.95.218    10.0.2.15       20000:31155/TCP   15m
service/kubernetes      ClusterIP      10.43.0.1       <none>          443/TCP           13h
service/rest-st-2       LoadBalancer   10.43.215.43    10.0.2.15       22222:32079/TCP   13h

NAME                             DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR   AGE
daemonset.apps/svclb-gw-st-2     1         1         1       1            1           <none>          15m
daemonset.apps/svclb-rest-st-2   1         1         1       1            1           <none>          13h

NAME                        READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/gw-st-2     1/1     1            1           15m
deployment.apps/rest-st-2   1/1     1            1           13h

NAME                                   DESIRED   CURRENT   READY   AGE
replicaset.apps/gw-st-2-ddc88dd9       1         1         1       15m
replicaset.apps/rest-st-2-7b767bf688   1         1         1       13h
[root@minikube springgw]# kubectl get pods -A
NAMESPACE     NAME                         READY   STATUS      RESTARTS   AGE
default       gw-st-2-ddc88dd9-4kcss       1/1     Running     0          16m
default       rest-st-2-7b767bf688-z4pnb   1/1     Running     0          13h
default       svclb-gw-st-2-85lkl          1/1     Running     0          16m
default       svclb-rest-st-2-7zc4g        1/1     Running     0          13h
kube-system   coredns-b7464766c-sv56q      1/1     Running     0          13h
kube-system   helm-install-traefik-p9wtc   0/1     Completed   0          13h
kube-system   svclb-traefik-z8c8w          2/2     Running     0          13h
kube-system   traefik-5c79b789c5-pbpvp     1/1     Running     0          13h
[root@minikube springgw]#

Run with docker only

[root@dev1 ~]# docker run -d -p 22222:22222  --restart=always --name zrest localhost:5000/rest-st-2
461ffccad417d834c29abfe2a3b11c11d4cd7d8016c4e043ba37934daea49e75

[root@dev1 ~]# docker run -d -p 20000:20000  --restart=always  --link zrest:rest-st-2  --name zgw localhost:5000/gw-st-2
eeaa20b4f2772609c6855c13938c5e39cbfc22032ebc772d345912fdf17dc359