Hi Venat, Everywhere what i see is how to setup istio or s sample app, but it would be good if you can add a video that would tell how to setup graphs and alerts for the sample app installed and not the defaults. Thanks.
Hi Dinesh, thanks for watching this video. The main focus of all my Istio related videos is to cover the core topic which is the service mesh capability. I was just showing that you can add Grafana to the service mesh stack. If I get some time, I will look into custom graphs and alerts. Cheers.
Hello Venkat, your video's are simply knowledgable. I got a question. Once the Envoy side car getting all the data and sending to control plane. From there using grafana or other dashboard s we see the status. Could you please aware how this is working. From what sources the data is getting displayed in grafana. Mainly the control plane Dashboard in grafana. Thanks for your video S again
Hey Venkat I assume you install Grafana manually ? bcoz it's not in same package as bookinfo app, correct me if I am wrong ? I new to devOps and learning with your video they are like training materials for me :)
Hi, Thanks for watching this video. Yes we have service in k8s at pod level. But Istio is a layer on top of it that abstracts the networking through service. As explained in the intro video to Istio, the application is accesses through a sidecar which forwards the requests to the actual pod service. So we got to use either load balancer or nodeport to access the ingress gateway of Istio to access any of the application in the cluster. Thanks.
Great k8s series Venkat! Can you please help me to understand why we need metalLB despite already having the istio ingress lb? In the previous video you accessed the application successfully with ingress external IP, so why do need metalLb? Thanks again for such a wonderful series!
Hi Nagender, thanks for watching. Istio's ingress gateway is exposed as load balancer type by default so we need metallb (as we are using bare-metals). You can also use node port for ingress gateway. It is through that istio ingress gateway you expose all your applications.
Hi again Venkat! Hope you could clear one more doubt. :) If I have multiple applications already running in my EKS setup and exposed publicly using ingress LBs, if I want to implement istio here then how should I go about this? You stated earlier in your videos that enabling istio in existing environment would not affect the existing environment. However, what should I use to expose my k8s services (eks)? Shall I keep the existing LBs or use the istio ingress to expose them and remove the old LBs? Sorry if this seems a strange question, very confused on this point as I have just started exploring istio. And again, amazing videos... please keep them coming!! Thanks!
Hi Nagender, thanks for watching. You don't have to change your application. Currently your apps are exposed using Kubernetes standard service of type load balancer. You will have to make use of virtual service and istio ingress gateway. Istio is enabled per namespace. As your apps are already running and I guess you enabled istio at a later time, you need to inject sidecars to your deployments.
@@justmeandopensource Thank you for clearing that up Venkat! Just one follow up question, when I create istio ingress gateway in EKS, will it create an AWS load balancer automatically? I remember you had metalLB ready for this for your non-cloud setup. Thanks again for responding to all my queries! Cheers!
@@nagendersingh35 Yes. Since you are running managed kubernetes service, anytime you create a service of type loadbalancer, a load balancer will get created for your automatically. Cheers.
Hi Venkat, i have some problème to connect my pods grafana et kiali, i configure nodeport, my pods grafana expose 3000:31383/TCP, and kiali expose 20001:31734/TCP, but i can't connect via ip or telnet with my cluster ip? u have any idea pls?
root@clasyn-pa01-ci:/srv/synapps/git/istio-1.3.1# kubectl -n istio-system get svc grafana NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE grafana NodePort 10.43.249.40 3000:31383/TCP 144m root@clasyn-pa01-ci:/srv/synapps/git/istio-1.3.1# kubectl -n istio-system get svc kiali NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE kiali NodePort 10.43.108.227 20001:31734/TCP 24h
Hi Siva, In this video, I used port-forwarding on grafana pod so that I can access the grafana dashboard using localhost:3000. As you tried, you can also access it using NodePort service. I see you already edited the grafana service. $ kubectl -n istio-system edit svc grafana and specify the type as NodePort. Now to access this nodeport service, you have to use the ip address of one of the worker nodes and not the cluster ip. Say for example, you have the below ip address for your nodes. 172.42.42.100 kmaster 172.42.42.101 kworker1 172.42.42.102 kworker2 And the node port is 31383, then the url for dashboard will be 172.42.42.101:31383 or 172.42.42.102:31383 You can get the ip address details of nodes using the below command. $ kubectl get nodes -o wide. Thanks.
Hi Venkat..can you create a video how to configure side car/proxy by taking 2 microservices. And how they communicate using side car(envoy). Thank you and God Bless you..
Hi Amit, thanks for watching this video. I have loads of topic to cover in Kubernetes. I have got a huge list and will definitely add kubevirt to that list. Thanks for suggesting this topic. Cheers.
First thing things, its a great video. I only got one question, how do i enable grafana on an existing istio name space? Based on 6 min and 59 sec of the video.
@@justmeandopensource You might not know, but I been following your videos for the last few weeks and working on on every single lab on my laptop. Thank you very much!!! Please keep up the great work!
Do you have video for this explanation? I would love to watch. As you mentioned we should not deploy pod on Master node but when I deploy new pods I'm not sure which node it goes.
Hi Venkat, I've installed Prometheus in Istio using instioctl and it is working fine, do you know how to add a job in prometheus after the istio installed? Thanks
Hi Luiz, thanks for watching. I haven't spent much time exploring that. But I think it might be something like a configmap containing prometheus configuration with all the jobs. And you just keep updating the configmap for any change.
Will you be making a video to describe how to integrate the prometheus and grafana created by Istio to kube-prometheus-stack (github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack)?
![[ Kube 53 ] Kiali - Visualize your Istio Service Mesh](http://i.ytimg.com/vi/dpb_q42uzy4/mqdefault.jpg)
![[ Kube 53 ] Kiali - Visualize your Istio Service Mesh](/img/tr.png)
![[ Kube 26 ] Prometheus monitoring for Kubernetes Cluster and Grafana visualization](http://i.ytimg.com/vi/CmPdyvgmw-A/mqdefault.jpg)
Hi Venkat, thanks a lot for the grafana video it's clear explaination waiting for the kiali visualization video
Hi Mukhtar, thanks for watching this video.
Hi Venat, Everywhere what i see is how to setup istio or s sample app, but it would be good if you can add a video that would tell how to setup graphs and alerts for the sample app installed and not the defaults. Thanks.
Hi Dinesh, thanks for watching this video. The main focus of all my Istio related videos is to cover the core topic which is the service mesh capability. I was just showing that you can add Grafana to the service mesh stack. If I get some time, I will look into custom graphs and alerts. Cheers.
Hello Venkat, your video's are simply knowledgable.
I got a question. Once the Envoy side car getting all the data and sending to control plane. From there using grafana or other dashboard s we see the status. Could you please aware how this is working. From what sources the data is getting displayed in grafana. Mainly the control plane Dashboard in grafana. Thanks for your video S again
Hey Venkat I assume you install Grafana manually ? bcoz it's not in same package as bookinfo app, correct me if I am wrong ? I new to devOps and learning with your video they are like training materials for me :)
Hi , thanks for the video. Cant we add a service in ingress and access the grafana service?
Hi Justin, thanks for watching. Yes you could. Did you give it a try?
Hi Venkat, Why do we need load balancer metallb or bare metal separately ,Because we already have service in k8s in pod level.
Hi, Thanks for watching this video. Yes we have service in k8s at pod level. But Istio is a layer on top of it that abstracts the networking through service. As explained in the intro video to Istio, the application is accesses through a sidecar which forwards the requests to the actual pod service.
So we got to use either load balancer or nodeport to access the ingress gateway of Istio to access any of the application in the cluster.
Thanks.
Great k8s series Venkat!
Can you please help me to understand why we need metalLB despite already having the istio ingress lb? In the previous video you accessed the application successfully with ingress external IP, so why do need metalLb?
Thanks again for such a wonderful series!
Hi Nagender, thanks for watching. Istio's ingress gateway is exposed as load balancer type by default so we need metallb (as we are using bare-metals). You can also use node port for ingress gateway. It is through that istio ingress gateway you expose all your applications.
@@justmeandopensource Got it Venkat. Thanks.
@@nagendersingh35 Cool.
Can u share how to create node port for these app
Hi again Venkat!
Hope you could clear one more doubt. :)
If I have multiple applications already running in my EKS setup and exposed publicly using ingress LBs, if I want to implement istio here then how should I go about this?
You stated earlier in your videos that enabling istio in existing environment would not affect the existing environment. However, what should I use to expose my k8s services (eks)? Shall I keep the existing LBs or use the istio ingress to expose them and remove the old LBs?
Sorry if this seems a strange question, very confused on this point as I have just started exploring istio.
And again, amazing videos... please keep them coming!!
Thanks!
Hi Nagender, thanks for watching. You don't have to change your application. Currently your apps are exposed using Kubernetes standard service of type load balancer. You will have to make use of virtual service and istio ingress gateway. Istio is enabled per namespace. As your apps are already running and I guess you enabled istio at a later time, you need to inject sidecars to your deployments.
@@justmeandopensource Thank you for clearing that up Venkat!
Just one follow up question, when I create istio ingress gateway in EKS, will it create an AWS load balancer automatically?
I remember you had metalLB ready for this for your non-cloud setup.
Thanks again for responding to all my queries!
Cheers!
@@nagendersingh35 Yes. Since you are running managed kubernetes service, anytime you create a service of type loadbalancer, a load balancer will get created for your automatically. Cheers.
@@justmeandopensource Got it Venkat.
Thanks!
Hi Venkat, i have some problème to connect my pods grafana et kiali, i configure nodeport, my pods grafana expose 3000:31383/TCP, and kiali expose 20001:31734/TCP, but i can't connect via ip or telnet with my cluster ip? u have any idea pls?
root@clasyn-pa01-ci:/srv/synapps/git/istio-1.3.1# kubectl -n istio-system get svc grafana
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
grafana NodePort 10.43.249.40 3000:31383/TCP 144m
root@clasyn-pa01-ci:/srv/synapps/git/istio-1.3.1# kubectl -n istio-system get svc kiali
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kiali NodePort 10.43.108.227 20001:31734/TCP 24h
Hi Siva, In this video, I used port-forwarding on grafana pod so that I can access the grafana dashboard using localhost:3000.
As you tried, you can also access it using NodePort service. I see you already edited the grafana service.
$ kubectl -n istio-system edit svc grafana
and specify the type as NodePort.
Now to access this nodeport service, you have to use the ip address of one of the worker nodes and not the cluster ip.
Say for example, you have the below ip address for your nodes.
172.42.42.100 kmaster
172.42.42.101 kworker1
172.42.42.102 kworker2
And the node port is 31383, then the url for dashboard will be
172.42.42.101:31383 or 172.42.42.102:31383
You can get the ip address details of nodes using the below command.
$ kubectl get nodes -o wide.
Thanks.
Venkat, thanks a lot for ur help. I’ll try tomorrow and get back to you. Can I contact with another way pls? LinkedIn or telegram pls???
@@sivaguruvinayagam7779 I would be happy to answer all your queries in YoutTube as that would help others as well. Thanks.
Hi Siva, Just opened a channel and a discussion group in telegram if you want to join.
t.me/justmeandopensource
t.me/justmeandopensourcegroup
Thanks.
Hi Venkat..can you create a video how to configure side car/proxy by taking 2 microservices. And how they communicate using side car(envoy). Thank you and God Bless you..
Hi Venkat , can you make a video on kubevirt?
Hi Amit, thanks for watching this video. I have loads of topic to cover in Kubernetes. I have got a huge list and will definitely add kubevirt to that list. Thanks for suggesting this topic. Cheers.
Plz explain how grafana visitation can work??
Hi Amrendra, were you not able to see the graphs or data in grafana dashboard?
First thing things, its a great video. I only got one question, how do i enable grafana on an existing istio name space? Based on 6 min and 59 sec of the video.
Hi, thanks for watching this video. I just got to bed. I will check and let you know tomorrow. Cheers.
@@justmeandopensource You might not know, but I been following your videos for the last few weeks and working on on every single lab on my laptop. Thank you very much!!! Please keep up the great work!
@@derpherp1000 Ahh. Thats great to hear. Thanks for following my series.
Hi, thank you so much for clear explanation and examples. I got a question, when you run istio-init, Did all pods are created in nodes or master host?
Hi Pete, thanks for watching. In my setup, the pods were created only in the worker nodes as the master node has "NoSchedule" taint.
Do you have video for this explanation? I would love to watch. As you mentioned we should not deploy pod on Master node but when I deploy new pods I'm not sure which node it goes.
To see which node the pods are scheduled, you can use the -o wide option to kubectl.
$ kubectl get pods -o wide
Hi Venkat, how i can delete grafana pls?
HI Siva, find the deployment in the istio namespace and delete it.
@@justmeandopensource thank u so much
No worries. You are always welcome.
Hi Venkat, I've installed Prometheus in Istio using instioctl and it is working fine, do you know how to add a job in prometheus after the istio installed?
Thanks
Hi Luiz, thanks for watching. I haven't spent much time exploring that. But I think it might be something like a configmap containing prometheus configuration with all the jobs. And you just keep updating the configmap for any change.
Will you be making a video to describe how to integrate the prometheus and grafana created by Istio to kube-prometheus-stack (github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack)?