As a Service Mesh user enabling side car injection, I have documentation for verifying that proxies have successfully been added using Kiali.

When enabling side car injection, add steps to verify that the proxies have successfully been added using Kiali. Point out that proxy logs and Proxy configuration can be accessed via kiali. There is a separate issue to provide instructions on kiali logs: https://issues.redhat.com/browse/OSSMDOC-337, thus don't need to reproduce here. Explain that proxy configuration is managed by the control plane, though it can be viewed via Kiali for debugging/validation purposes. Kiali also provides some explanation of the log values (some of this content could go in the troubleshooting section, but we should mention this here).

https://docs.openshift.com/container-platform/4.9/service_mesh/v2x/prepare-to-deploy-applications-ossm.html#ossm-update-app-sidecar_deploying-applications-ossm

Assembly =Enabling Sidecar Injection  (prepare-to-deploy-applications-ossm.adoc)

Add a new module - Validating the sidecar injection using Kiali. (Before Updating application pods module?)

Overview

• Explain that proxy configuration is managed by the control plane, though it can be viewed via Kiali for debugging/validation purposes.
• Kiali validations https://kiali.io/docs/features/validations/#sidecars

Graph page - Badge for missing sidecar

Istio Config page - Displays the YAML files, highlights the misconfiguration (does NOT note missing sidecar, as it's defined in the Deployment file)

Links to related upstream docs

https://kiali.io/docs/tutorials/travels/03-first-steps/

https://kiali.io/docs/features/wizards/#automatic-sidecar-injection (Workloads page)

Kiali validation for sidecars

https://kiali.io/docs/features/validations/#sidecars

NOTE - make sure to include the validation code (for example, KIA1003) as the Kiali configuration lets users set Kiali to ignore validations using their ID.