Hi,
I am learning Istio Service Mesh, and I have reached till Traffic management section.
My doubts are:
- Accessing the application from the browser. Like earlier we used to access the application with ingress IP. Now I can use Istio in place of ingress.
But not sure how will I access the application on the browser? Should I use the IP which I will get from the below command.
export INGRESS_HOST=$(kubectl get po -l istio=ingressgateway -n istio-system -o jsonpath=‘{.items[0].status.hostIP}’)
- Lets say there is already an application that is running in the cluster with version v1.
Now my team wants to do some testing with the new version. If I add another destination in the destination rule along with weight of even 1% then the customers will be getting that new version page too.
How can I make sure that only my testing team can access it and not others. Once my testing team is fine with it then I’ll increase the traffic to the new version.
- Can I use these commands all the time If I want to test the connectivity, I mean will there be any change in the command? Asking this as I am not very comfortable in Json queries.
export INGRESS_PORT=$(kubectl -n istio-system get service istio-ingressgateway -o jsonpath=‘{.spec.ports[?(@.name==“http2”)].nodePort}’)
export SECURE_INGRESS_PORT=$(kubectl -n istio-system get service istio-ingressgateway -o jsonpath=‘{.spec.ports[?(@.name==“https”)].nodePort}’)
export TCP_INGRESS_PORT=$(kubectl -n istio-system get service istio-ingressgateway -o jsonpath=‘{.spec.ports[?(@.name==“tcp”)].nodePort}’)
export INGRESS_HOST=$(kubectl get po -l istio=ingressgateway -n istio-system -o jsonpath=‘{.items[0].status.hostIP}’)