Skip to content

Microservices created with Quarkus and React were communicated with Istio using the LoadBalancer, Service Mesh and Ingress Gateway features.

Notifications You must be signed in to change notification settings

KerimAksak/Quarkus-Istio-Ingress

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

9 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Quarkus-Istio-Ingress

Topology

-----------------------------------------------------

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

-----------------------------------------------------

kubectl

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

Test

-----------------------------------------------------

Ingress Gateway Information

ingress-info

Frontend

caller-ping

Backend - Caller Ping

ingress-info

Backend - Callme ping with Caller

caller-ping

About

Microservices created with Quarkus and React were communicated with Istio using the LoadBalancer, Service Mesh and Ingress Gateway features.

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published