<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Clusters on Layer5 Documentation</title><link>/tags/clusters/</link><description>Recent content in Clusters on Layer5 Documentation</description><generator>Hugo</generator><language>en</language><atom:link href="/tags/clusters/index.xml" rel="self" type="application/rss+xml"/><item><title>Operator</title><link>/kanvas/concepts/operator/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/kanvas/concepts/operator/</guid><description>&lt;p&gt;Operator mode is Kanvas&amp;rsquo;s view of what is running. Designer mode works on what you intend to run. Operator draws the Kubernetes resources found in your connected clusters on the same canvas, shows each one&amp;rsquo;s recorded state, and gives you actions against the live workloads: open a shell, follow logs, run a load test, or jump back to the design that produced a resource.&lt;/p&gt;
&lt;figure&gt;
 &lt;img src="images/operator-no-context.png" alt="Operator mode before any Kubernetes cluster is selected, showing an empty canvas and a prompt to select clusters" /&gt;
 &lt;figcaption&gt;Operator with no Kubernetes context selected. Choose one or more clusters to draw resources.&lt;/figcaption&gt;
&lt;/figure&gt;

&lt;h2 id="where-operator-data-comes-from" class="heading-link"&gt;
 Where Operator data comes from
 &lt;a href="#where-operator-data-comes-from" class="heading-anchor" aria-label="Permalink to this heading"&gt;🔗&lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;Kanvas does not talk to your clusters directly. Four pieces sit between a cluster and the canvas:&lt;/p&gt;</description></item></channel></rss>