<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>External Services on Kiali</title><link>https://staging--kiali.netlify.app/docs/configuration/external-services/</link><description>Recent content in External Services on Kiali</description><generator>Hugo</generator><language>en</language><atom:link href="https://staging--kiali.netlify.app/docs/configuration/external-services/index.xml" rel="self" type="application/rss+xml"/><item><title>TLS Configuration</title><link>https://staging--kiali.netlify.app/docs/configuration/external-services/tls-configuration/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://staging--kiali.netlify.app/docs/configuration/external-services/tls-configuration/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;&#10;&lt;p&gt;When Kiali connects to external services (Prometheus, Grafana, Jaeger/Tempo, Perses) over HTTPS, it needs to verify the TLS certificates presented by those services. By default, Kiali trusts the system certificate authorities (CAs) that are built into the container image.&lt;/p&gt;&#10;&lt;p&gt;If your external services use certificates issued by a private CA (such as an internal corporate CA, a service mesh CA, or self-signed certificates), you need to configure Kiali to trust those additional CAs.&lt;/p&gt;</description></item></channel></rss>