<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Installation on Kiali</title><link>https://staging--kiali.netlify.app/docs/installation/</link><description>Recent content in Installation on Kiali</description><generator>Hugo</generator><language>en</language><atom:link href="https://staging--kiali.netlify.app/docs/installation/index.xml" rel="self" type="application/rss+xml"/><item><title>Quick Start</title><link>https://staging--kiali.netlify.app/docs/installation/quick-start/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://staging--kiali.netlify.app/docs/installation/quick-start/</guid><description>&lt;h2 id="run-kiali-locally"&gt;Run Kiali locally&lt;/h2&gt;&#10;&lt;p&gt;Kiali can be run directly on your machine without being installed into a Kubernetes cluster. It uses your kubeconfig to connect to your cluster(s). If needed, it can port-forward into the cluster to connect to your external services (prometheus, tracing, istio, grafana).&lt;/p&gt;&#10;&lt;div class="alert alert-info" role="alert"&gt;&#10;&lt;p&gt;Running Kiali locally is currently experimental. Functionality may change between releases.&lt;/p&gt;&#10;&lt;/div&gt;&#10;&lt;p&gt;Download the Kiali binary from the &lt;a href="https://github.com/kiali/kiali/releases/latest"&gt;Kiali GitHub releases page&lt;/a&gt; for your OS and Arch.&lt;/p&gt;</description></item><item><title>Deployment Options</title><link>https://staging--kiali.netlify.app/docs/installation/deployment-options/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://staging--kiali.netlify.app/docs/installation/deployment-options/</guid><description>&lt;p&gt;There are other, more complex deployment settings, described in dedicated pages:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;a href="https://staging--kiali.netlify.app/docs/configuration/authentication/"&gt;Authentication&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://staging--kiali.netlify.app/docs/installation/installation-guide/accessing-kiali/#ingress-access"&gt;Customization of the Ingress resource&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://staging--kiali.netlify.app/docs/installation/installation-guide/accessing-kiali/#accessing-kiali-through-a-loadbalancer-or-a-nodeport"&gt;Customization of the service type (LoadBalancer or&#10;NodePort)&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://staging--kiali.netlify.app/docs/configuration/namespace-management/"&gt;Namespace management (configuring namespaces accessible and visible to&#10;Kiali)&lt;/a&gt;&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;div class="alert alert-success" role="alert"&gt;&#10;&lt;p&gt;All examples on this page are focused&#10;on the Kiali CR (when installing via the Kiali operator). Remember&#10;that Helm charts mirror all these configurations.&lt;/p&gt;&#10;&lt;/div&gt;&#10;&lt;h2 id="kiali-and-istio-installation-namespaces"&gt;Kiali and Istio installation namespaces&lt;/h2&gt;&#10;&lt;p&gt;By default, the Kiali operator installs Kiali in the same namespace where the Kiali CR is created. However, it is possible to specify a different namespace for installation:&lt;/p&gt;</description></item></channel></rss>