Comments on: Service mesh on Kubernetes with Istio and Spring Boot

By: piotr.minkowski

piotr.minkowski — Fri, 18 Nov 2022 10:14:43 +0000

In reply to Eitan Suez. Yes, the main goal of that article is to show the basics around istio.

By: Eitan Suez

Eitan Suez — Thu, 17 Nov 2022 21:53:23 +0000

Thanks for your writeup. The article does not have a summary section where one typically draws some conclusions or makes observations. I’m trying to understand what is the point that the exercise is trying to make. Perhaps just to understand how to use these two technologies in combination. Is it perhaps to show that with Istio, a spring boot application no longer needs the litany of spring cloud projects? That you can sort of “go back to basics” with spring and simplify your app to just deal with business logic and that istio just takes care of the rest? Thanks in advance for your thoughts on my questions.

By: piotr.minkowski

piotr.minkowski — Mon, 12 Jul 2021 10:45:59 +0000

In reply to Deb. Thanks :)

By: Deb

Deb — Thu, 08 Jul 2021 14:39:52 +0000

Hello Piotr

This is an excellent article, looking forward to more like this. extra ordinary.

By: piotr.minkowski

piotr.minkowski — Sat, 22 Aug 2020 12:21:17 +0000

In reply to Deepu Keloth. In my opinion, you should just run that database on Kubernetes. If not it depends on your local Kubernetes cluster configuration. For example if you use the same Docker daemon for running database and Kubernetes?

By: Deepu Keloth

Deepu Keloth — Mon, 10 Aug 2020 15:26:35 +0000

Hi Piotr , i have another question related to accessing the database from kubernetes Pod running in windows10 machine.
I am running the docker database container in my local and i would like to access this docker database container from the Pod. Could you suggest a way?

By: Piotr Mińkowski

Piotr Mińkowski — Fri, 24 Jul 2020 12:35:12 +0000

In reply to Deepu Keloth.

Hi.
1. Well, there is virtualservice defined for callme-service…
2. No, because this name is overidden by Istio virtualservice
3. The traffic is handled by Istio sidecar proxy.

By: Deepu Keloth

Deepu Keloth — Thu, 23 Jul 2020 15:22:01 +0000

Thank you very much Piotr for this post.
I have a question regarding the VirtualService created for callme-service. In order to access the callme-service from caller-service, caller-service is using the code: restTemplate.getForObject(“http://callme-service:8080/callme/ping”, String.class);
But I don’t see any mention of istio config yaml of virtualservice for “callme-service” running on port 8080.
(1) So if no mention of the virtualservice port then is 8080 the default port?
(2) But i see that “Kubernetes Service” of “callme-service” is running on port 8080. So in the code:restTemplate.getForObject(“http://callme-service:8080/callme/ping”, String.class); is it refering to “Kubernetes Service” of “callme-service”
(3) If it is refering to “Kubernetes Service” of “callme-service”, then how is it that the network routing rule of “callme-service” virtualservice is applied?

By: Asim

Asim — Tue, 14 Jul 2020 22:20:52 +0000

From istio.io | Note that istioctl install and istioctl manifest apply are exactly the same command. In Istio 1.6, the simpler install command replaces manifest apply, which is deprecated and will be removed in 1.7.

By: Piotr Mińkowski

Piotr Mińkowski — Tue, 14 Jul 2020 20:23:12 +0000

In reply to Asim. Ok. Thanks for that clarification