Quarkus-Istio-Ingress

Topology

Installation

Backend - Quarkus

Steps to deploy on minikube

➜  ~ cd caller/k8s
➜  ~ kubectl apply -f deployment.yml
➜  ~ kubectl apply -f istio-rule.yml
➜  ~ cd callme/k8s
➜  ~ kubectl apply -f deployment.yml
➜  ~ kubectl apply -f istio-rule.yml

Frontend - React

Steps to deploy on minikube

➜  ~ cd react-frontend/k8s
➜  ~ kubectl apply -f deployment.yml
➜  ~ kubectl apply -f istio-rule.yml
➜  ~ kubectl apply -f istio-ingress.yml

In order to use istio ingress gateway, we must use the minikube tunnel command. If the command is not run, the external-ip value of the istio-ingressgateway service (kubectl get service -n istio-system) will remain as < PENDING >

After all the steps

• kgp ➜ kubectl get pod
• k get vs ➜ kubectl get virtualservice
• k get dr ➜ kubectl get destinationrule
• kgs ➜ kubectl get service

Test

Ingress Gateway Information

Frontend

Backend - Caller Ping

Backend - Callme ping with Caller