Figure out Injection of Envoy SideCars with current Pods

[AnshulV98]

As Istio has been installed on Jetsream instance, it has been setup with the default namespace with auto envoy sidecar injection mode enabled such that, whenever a pod is re/deployed or re/started it would be injected with an Envoy sidecar

[AnshulV98]

The current issue is if you run

istioctl analyze

you get this result

Warn [IST0103] (Pod rabbitmq-controller-fm5rz.default) The pod is missing the Istio proxy. This can often be resolved by restarting or redeploying the workload.
Info [IST0118] (Service apigateway.default) Port name  (port: 8090, targetPort: 8090) doesn't follow the naming convention of Istio port.
Info [IST0118] (Service dataretrival.default) Port name  (port: 5001, targetPort: 5001) doesn't follow the naming convention of Istio port.
Info [IST0118] (Service frontend.default) Port name  (port: 3000, targetPort: 3000) doesn't follow the naming convention of Istio port.
Info [IST0118] (Service modelanalysis.default) Port name  (port: 5005, targetPort: 5005) doesn't follow the naming convention of Istio port.
Info [IST0118] (Service modelexecution.default) Port name  (port: 5003, targetPort: 5003) doesn't follow the naming convention of Istio port.
Info [IST0118] (Service rabbitmq-service.default) Port name  (port: 5672, targetPort: 5672) doesn't follow the naming convention of Istio port.
Info [IST0118] (Service sessionmanagement.default) Port name  (port: 7000, targetPort: 7000) doesn't follow the naming convention of Istio port.
Info [IST0118] (Service usermanagement.default) Port name  (port: 5000, targetPort: 5000) doesn't follow the naming convention of Istio port.
Error: Analyzers found issues when analyzing namespace: default.
See https://istio.io/docs/reference/config/analysis for more information about causes and resolutions.

[AnshulV98]

A possible solution for this could be to edit all the YAML files and enter a name: field inside the port: fields to name every port this could possibly resolve this issue

[ViralPrajapati]

Even that might not solve the problem because the issue seems to be with the LodeBalancer type which we are currently using instead of NodePort type for the services.

[ViralPrajapati]

Automatic sidecar injection is working perfectly, the only reason we were not able to access kiali dashboard was istio services are by default of type Loadbalancer, which needed to be changed to NodePort in the yaml file.
2dab87c