<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>StormForge Documentation</title>
		<link>/</link>
		<description>Recent content on StormForge Documentation</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<atom:link href="/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>StormForge architecture</title>
				<link>/docs/concepts/architecture/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/concepts/architecture/</guid>
				<description>&lt;p&gt;The following components run in a dedicated namespace (by default, &lt;code&gt;stormforge-system&lt;/code&gt;) &lt;strong&gt;on your Kubernetes cluster&lt;/strong&gt;:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;StormForge Agent&lt;/li&gt;&#xA;&lt;li&gt;StormForge Applier&lt;/li&gt;&#xA;&lt;li&gt;StormForge Forwarder&lt;/li&gt;&#xA;&lt;li&gt;StormForge Node Agent (optional)&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;The following components exist &lt;strong&gt;outside of your cluster&lt;/strong&gt;:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The StormForge cloud&lt;/li&gt;&#xA;&lt;li&gt;The &lt;code&gt;stormforge&lt;/code&gt; &lt;a href=&#34;/docs/stormforge-cli/&#34;&gt;CLI tool&lt;/a&gt; (optional)&lt;/li&gt;&#xA;&lt;li&gt;The StormForge UI (web application)&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Or, shown diagrammatically: &lt;br&gt;&#xA;&lt;a href=&#34;/img/docs/stormforge-architecture.png&#34;&gt;&lt;img src=&#34;/img/docs/stormforge-architecture.png&#34; alt=&#34;StormForge architecture&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;The StormForge Agent is a Kubernetes Pod with an application written in Go. The Agent discovers and reports on workloads in the namespaces in the cluster. You can restrict access to namespaces by using an allowNamespaces or a denyNamespaces list.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Quickstart</title>
				<link>/docs/get-started/quickstart/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/get-started/quickstart/</guid>
				<description>&lt;p&gt;This quickstart installs StormForge on your Kubernetes cluster with a single Helm command. StormForge starts generating preliminary recommendations within 10 minutes. Complete, actionable recommendations are ready after a 7-day learning period.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-youll-need&#34;&gt;What you&amp;rsquo;ll need&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#what-youll-need&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;A Kubernetes cluster (EKS, AKS, GKE, minikube, kind, or any other distribution)&lt;/li&gt;&#xA;&lt;li&gt;A StormForge account — sign up for free at &lt;strong&gt;&lt;a href=&#34;https://app.stormforge.io/signup&#34;&gt;app.stormforge.io/signup&lt;/a&gt;&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;helm&lt;/code&gt; installed locally&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;install-stormforge&#34;&gt;Install StormForge&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#install-stormforge&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Log in to &lt;strong&gt;&lt;a href=&#34;https://app.stormforge.io/&#34;&gt;app.stormforge.io&lt;/a&gt;&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;p&gt;If this is your first time, you&amp;rsquo;ll be taken directly to the &lt;strong&gt;Add Cluster&lt;/strong&gt; page.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Click &lt;strong&gt;Clusters&lt;/strong&gt; in the left navigation, then click &lt;strong&gt;Add Cluster&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Give your cluster a name and click &lt;strong&gt;Continue&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;p&gt;The cluster name can&amp;rsquo;t exceed 63 characters, can&amp;rsquo;t start or end with a dash (&lt;code&gt;-&lt;/code&gt;), and must follow the &lt;a href=&#34;https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#dns-label-names&#34;&gt;RFC 1123 DNS label standard&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Copy and run the generated &lt;code&gt;helm install&lt;/code&gt; command. It looks like this (with your credentials in place of &lt;code&gt;CLIENT_ID&lt;/code&gt; and &lt;code&gt;CLIENT_SECRET&lt;/code&gt;):&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-shell&#34; data-lang=&#34;shell&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;helm install stormforge oci://registry.stormforge.io/library/stormforge &lt;span style=&#34;color:#ae81ff&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  --create-namespace --namespace stormforge-system &lt;span style=&#34;color:#ae81ff&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  --set clusterName&lt;span style=&#34;color:#f92672&#34;&gt;=&lt;/span&gt;&lt;span style=&#34;color:#e6db74&#34;&gt;&amp;#34;my-cluster&amp;#34;&lt;/span&gt; &lt;span style=&#34;color:#ae81ff&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  --set authorization.clientID&lt;span style=&#34;color:#f92672&#34;&gt;=&lt;/span&gt;&lt;span style=&#34;color:#e6db74&#34;&gt;&amp;#34;CLIENT_ID&amp;#34;&lt;/span&gt; &lt;span style=&#34;color:#ae81ff&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  --set authorization.clientSecret&lt;span style=&#34;color:#f92672&#34;&gt;=&lt;/span&gt;&lt;span style=&#34;color:#e6db74&#34;&gt;&amp;#34;CLIENT_SECRET&amp;#34;&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/li&gt;&#xA;&lt;/ol&gt;</description>
			</item>
			<item>
				<title>Getting started with configuring StormForge</title>
				<link>/docs/configure/configure-opt-settings/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/configure/configure-opt-settings/</guid>
				<description>&lt;h2 id=&#34;getting-started&#34;&gt;Getting started&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#getting-started&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;StormForge performs best when it is properly configured with goals, constraints, and requirements appropriate for the workloads it is optimizing. One of the first steps you should take when deploying StormForge is to &lt;strong&gt;review the available configuration options, and adjust settings as needed to suit your organization’s requirements.&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Optimization settings can be applied as cluster-scoped defaults, namespace-scoped defaults, or directly to individual workloads. Making sure your cluster-scoped default values are aligned with your organization’s requirements first provides the most return for your effort. You can carve out exceptions to these settings for particular namespaces or workloads later.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Configure optimization defaults for the cluster</title>
				<link>/docs/configure/cluster-defaults/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/configure/cluster-defaults/</guid>
				<description>&lt;p&gt;The purpose of this topic is to describe how to use the &lt;code&gt;cluster-defaults&lt;/code&gt; ConfigMap to configure default optimization settings for a cluster.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Topics:&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#configure-defaults&#34;&gt;Configure default optimization settings for all workloads in the cluster&lt;/a&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#defaults-using-kubectl-apply&#34;&gt;Using &lt;code&gt;kubectl apply&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#defaults-using-kubectl-edit&#34;&gt;Using &lt;code&gt;kubectl edit&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;configure-defaults&#34;&gt;Configure default optimization settings for all workloads in the cluster&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#configure-defaults&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;Cluster-level defaults:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Define the default optimization settings for all workloads in a cluster&lt;/li&gt;&#xA;&lt;li&gt;Are specified in a ConfigMap named &lt;code&gt;cluster-defaults&lt;/code&gt; in the &lt;code&gt;stormforge-system&lt;/code&gt; namespace&lt;/li&gt;&#xA;&lt;li&gt;Have the lowest configuration precedence and can be overridden by namespace annotations or by annotations on individual workload resources&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;defaults-using-kubectl-apply&#34;&gt;Setting cluster default values using &lt;code&gt;kubectl apply&lt;/code&gt;&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#defaults-using-kubectl-apply&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Create a YAML file that defines a ConfigMap called &lt;code&gt;cluster-defaults&lt;/code&gt;, with a &lt;code&gt;cluster-defaults.yaml&lt;/code&gt; data key, and the settings you want to set in annotation syntax.&lt;/p&gt;&#xA;&lt;p&gt;For a complete list of annotations for StormForge settings, see the &lt;a href=&#34;/docs/configure/settings/&#34;&gt;Optimization settings and descriptions&lt;/a&gt; topic.&lt;/p&gt;&#xA;&lt;p&gt;Your file will look something like this:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-yaml&#34; data-lang=&#34;yaml&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#f92672&#34;&gt;apiVersion&lt;/span&gt;: &lt;span style=&#34;color:#ae81ff&#34;&gt;v1&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#f92672&#34;&gt;kind&lt;/span&gt;: &lt;span style=&#34;color:#ae81ff&#34;&gt;ConfigMap&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#f92672&#34;&gt;metadata&lt;/span&gt;:&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  &lt;span style=&#34;color:#f92672&#34;&gt;name&lt;/span&gt;: &lt;span style=&#34;color:#ae81ff&#34;&gt;cluster-defaults&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  &lt;span style=&#34;color:#f92672&#34;&gt;namespace&lt;/span&gt;: &lt;span style=&#34;color:#ae81ff&#34;&gt;stormforge-system&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#f92672&#34;&gt;data&lt;/span&gt;:&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  &lt;span style=&#34;color:#f92672&#34;&gt;cluster-defaults.yaml&lt;/span&gt;: |&lt;span style=&#34;color:#e6db74&#34;&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#e6db74&#34;&gt;    live.stormforge.io/schedule: &amp;#34;P1D&amp;#34;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#e6db74&#34;&gt;    live.stormforge.io/auto-deploy: &amp;#34;Disabled&amp;#34;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#e6db74&#34;&gt;    live.stormforge.io/containers.cpu.requests.min: &amp;#34;10m&amp;#34;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#e6db74&#34;&gt;    live.stormforge.io/containers.cpu.requests.max: &amp;#34;16000m&amp;#34;&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;...&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Apply the file:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-shell&#34; data-lang=&#34;shell&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;kubectl apply -f FILENAME -n stormforge-system&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Restart the StormForge Agent:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-shell&#34; data-lang=&#34;shell&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;kubectl rollout restart deployment stormforge-cluster-agent -n stormforge-system&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;To check the status of the restart, run:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-sh&#34; data-lang=&#34;sh&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;kubectl rollout status deployment stormforge-cluster-agent -n stormforge-system -w&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Any previous cluster-level default values are now removed, and your new defaults are in effect unless they are overridden at the namespace or workload level.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Optional: Confirm your changes by running the following command and then reviewing the &lt;code&gt;cluster-defaults.yaml&lt;/code&gt; item in the &lt;strong&gt;Data&lt;/strong&gt; section of the output:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-shell&#34; data-lang=&#34;shell&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;kubectl describe configmap cluster-defaults -n stormforge-system &#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/li&gt;&#xA;&lt;/ol&gt;</description>
			</item>
			<item>
				<title>Annotations</title>
				<link>/docs/configure/settings/annotations/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/configure/settings/annotations/</guid>
				<description>&lt;h2 id=&#34;goal&#34;&gt;&lt;a href=&#34;/docs/configure/settings/goal/&#34;&gt;Goal&lt;/a&gt;&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#goal&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;&lt;code&gt;live.stormforge.io/cpu.optimization-goal: &amp;quot;Balanced&amp;quot;&lt;/code&gt;&lt;br&gt;&#xA;&lt;code&gt;live.stormforge.io/memory.optimization-goal: &amp;quot;Balanced&amp;quot;&lt;/code&gt;&lt;/p&gt;&#xA;&lt;h2 id=&#34;schedule&#34;&gt;&lt;a href=&#34;/docs/configure/settings/schedule/&#34;&gt;Schedule&lt;/a&gt;&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#schedule&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;&lt;code&gt;live.stormforge.io/schedule: &amp;quot;@daily&amp;quot;&lt;/code&gt;&lt;br&gt;&#xA;&lt;code&gt;live.stormforge.io/schedule.timezone: &amp;quot;UTC&amp;quot;&lt;/code&gt;&lt;br&gt;&#xA;&lt;code&gt;live.stormforge.io/validity-period: &amp;quot;&amp;quot;&lt;/code&gt;&lt;/p&gt;&#xA;&lt;h2 id=&#34;apply-settings&#34;&gt;&lt;a href=&#34;/docs/configure/settings/apply-settings/&#34;&gt;Apply settings&lt;/a&gt;&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#apply-settings&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;&lt;code&gt;live.stormforge.io/auto-deploy: &amp;quot;Disabled&amp;quot;&lt;/code&gt;&lt;br&gt;&#xA;&lt;code&gt;live.stormforge.io/learning-period: &amp;quot;P7D&amp;quot;&lt;/code&gt;&lt;br&gt;&#xA;&lt;code&gt;live.stormforge.io/auto-deploy.thresholds.cpu.percent: &amp;quot;&amp;quot;&lt;/code&gt;&lt;br&gt;&#xA;&lt;code&gt;live.stormforge.io/auto-deploy.thresholds.memory.percent: &amp;quot;&amp;quot;&lt;/code&gt;&lt;br&gt;&#xA;&lt;code&gt;live.stormforge.io/auto-deploy.thresholds.cpu.unit: &amp;quot;&amp;quot;&lt;/code&gt;&lt;br&gt;&#xA;&lt;code&gt;live.stormforge.io/auto-deploy.thresholds.memory.unit: &amp;quot;&amp;quot;&lt;/code&gt;&lt;br&gt;&#xA;&lt;code&gt;live.stormforge.io/apply.method: &amp;quot;PatchImmediateRollout&amp;quot;&lt;/code&gt;&lt;br&gt;&#xA;&lt;code&gt;live.stormforge.io/apply.max-percent-increase: &amp;quot;&amp;quot;&lt;/code&gt;&lt;br&gt;&#xA;&lt;code&gt;live.stormforge.io/apply.max-percent-decrease: &amp;quot;&amp;quot;&lt;/code&gt;&lt;br&gt;&#xA;&lt;code&gt;live.stormforge.io/pod-template.metadata.patch-path: &amp;quot;&amp;quot;&lt;/code&gt;&lt;br&gt;&#xA;&lt;code&gt;live.stormforge.io/pod-template.metadata.patch-format: &amp;quot;&amp;quot;&lt;/code&gt;&lt;/p&gt;&#xA;&lt;h2 id=&#34;reliability&#34;&gt;&lt;a href=&#34;/docs/configure/settings/reliability/&#34;&gt;Reliability&lt;/a&gt;&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#reliability&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;&lt;code&gt;live.stormforge.io/reliability.oom.memory-bump-up.enabled: &amp;quot;False&amp;quot;&lt;/code&gt;&lt;br&gt;&#xA;&lt;code&gt;live.stormforge.io/reliability.oom.memory-bump-up.period: &amp;quot;P4D&amp;quot;&lt;/code&gt;&lt;br&gt;&#xA;&lt;code&gt;live.stormforge.io/reliability.oom.memory-bump-up.percent: &amp;quot;0&amp;quot;&lt;/code&gt;&lt;br&gt;&#xA;&lt;code&gt;live.stormforge.io/reliability.oom.memory-bump-up.min: &amp;quot;0Mi&amp;quot;&lt;/code&gt;&lt;br&gt;&#xA;&lt;code&gt;live.stormforge.io/reliability.oom.memory-bump-up.max: &amp;quot;2Gi&amp;quot;&lt;/code&gt;&lt;br&gt;&#xA;&lt;code&gt;live.stormforge.io/reliability.oom.memory-bump-up.apply-immediately: &amp;quot;Never&amp;quot;&lt;/code&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;code&gt;live.stormforge.io/reliability.cpu-pressure.cpu-bump-up.enabled: &amp;quot;False&amp;quot;&lt;/code&gt;&lt;br&gt;&#xA;&lt;code&gt;live.stormforge.io/reliability.cpu-pressure.cpu-bump-up.period: &amp;quot;P4D&amp;quot;&lt;/code&gt;&lt;br&gt;&#xA;&lt;code&gt;live.stormforge.io/reliability.cpu-pressure.cpu-bump-up.percent: &amp;quot;0&amp;quot;&lt;/code&gt;&lt;br&gt;&#xA;&lt;code&gt;live.stormforge.io/reliability.cpu-pressure.cpu-bump-up.min: &amp;quot;0m&amp;quot;&lt;/code&gt;&lt;br&gt;&#xA;&lt;code&gt;live.stormforge.io/reliability.cpu-pressure.cpu-bump-up.max: &amp;quot;500m&amp;quot;&lt;/code&gt;&lt;br&gt;&#xA;&lt;code&gt;live.stormforge.io/reliability.cpu-pressure.cpu-bump-up.apply-immediately: &amp;quot;Never&amp;quot;&lt;/code&gt;&lt;/p&gt;&#xA;&lt;h2 id=&#34;cpu-and-memory&#34;&gt;&lt;a href=&#34;/docs/configure/settings/cpu-and-memory/&#34;&gt;CPU and memory&lt;/a&gt;&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#cpu-and-memory&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;&lt;code&gt;live.stormforge.io/containers.cpu.optimization-policy: &amp;quot;RequestsRaiseLimitsIfNeeded&amp;quot;&lt;/code&gt;&lt;br&gt;&#xA;&lt;code&gt;live.stormforge.io/containers.memory.optimization-policy: &amp;quot;RequestsRaiseLimitsIfNeeded&amp;quot;&lt;/code&gt;&lt;br&gt;&#xA;&lt;code&gt;live.stormforge.io/containers.cpu.limits.limit-request-ratio: &amp;quot;2.0&amp;quot;&lt;/code&gt;&lt;br&gt;&#xA;&lt;code&gt;live.stormforge.io/containers.memory.limits.limit-request-ratio: &amp;quot;2.0&amp;quot;&lt;/code&gt;&lt;/p&gt;</description>
			</item>
			<item>
				<title>Configure optimization defaults for namespaces</title>
				<link>/docs/configure/annotate-namespaces/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/configure/annotate-namespaces/</guid>
				<description>&lt;p&gt;The purpose of this topic is to describe how to use annotations to configure optimization settings.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Topics:&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#annot-ns&#34;&gt;Configure default optimization settings for all workloads in a namespace&lt;/a&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#annot-ns-yaml&#34;&gt;Using YAML manifests&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#annot-ns-kubectl-annotate&#34;&gt;Using &lt;code&gt;kubectl annotate&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;annot-ns&#34;&gt;Configure default optimization settings for all workloads in a namespace&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#annot-ns&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;To configure settings for all workloads in a namespace, edit the Namespace definition or run &lt;code&gt;kubectl annotate&lt;/code&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Namespace-level defaults:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Define the default optimization settings for all workloads in a namespace&lt;/li&gt;&#xA;&lt;li&gt;Override any equivalent cluster-level defaults&lt;/li&gt;&#xA;&lt;li&gt;Are specified using annotations on the namespace&lt;/li&gt;&#xA;&lt;li&gt;Fill in any settings not provided by annotations on the workloads themselves&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;annot-ns-yaml&#34;&gt;Using YAML manifests&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#annot-ns-yaml&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Open the namespace definition in your favorite editor. This is commonly done using commands like these (remember to replace NAMESPACE and FILENAME with your own values):&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-shell&#34; data-lang=&#34;shell&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;kubectl get namespace NAMESPACE -o yaml &amp;gt; FILENAME &lt;span style=&#34;color:#f92672&#34;&gt;&amp;amp;&amp;amp;&lt;/span&gt; $EDITOR FILENAME&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;or:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-shell&#34; data-lang=&#34;shell&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;kubectl edit namespace NAMESPACE&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Edit the &lt;code&gt;metadata.annotations&lt;/code&gt; section to include the annotations you need. For a complete list of annotations for StormForge settings, see the &lt;a href=&#34;/docs/configure/settings/&#34;&gt;Optimization settings and descriptions&lt;/a&gt; topic.&lt;/p&gt;&#xA;&lt;p&gt;Your file will look something like this:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-yaml&#34; data-lang=&#34;yaml&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#f92672&#34;&gt;apiVersion&lt;/span&gt;: &lt;span style=&#34;color:#ae81ff&#34;&gt;v1&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#f92672&#34;&gt;kind&lt;/span&gt;: &lt;span style=&#34;color:#ae81ff&#34;&gt;Namespace&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#f92672&#34;&gt;metadata&lt;/span&gt;:&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  &lt;span style=&#34;color:#f92672&#34;&gt;name&lt;/span&gt;: &lt;span style=&#34;color:#ae81ff&#34;&gt;example-namespace-name&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  &lt;span style=&#34;color:#f92672&#34;&gt;annotations&lt;/span&gt;:&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    &lt;span style=&#34;color:#f92672&#34;&gt;live.stormforge.io/schedule&lt;/span&gt;: &lt;span style=&#34;color:#e6db74&#34;&gt;&amp;#34;@daily&amp;#34;&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    &lt;span style=&#34;color:#f92672&#34;&gt;live.stormforge.io/auto-deploy&lt;/span&gt;: &lt;span style=&#34;color:#e6db74&#34;&gt;&amp;#34;Enabled&amp;#34;&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;...&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt; &lt;div class=&#34;alert alert-info&#34; role=&#34;alert&#34;&gt;&lt;div class=&#34;h4 alert-heading&#34; role=&#34;heading&#34;&gt;Tip&lt;/div&gt;&#xA;&lt;p&gt;To save time, you can copy the complete list of annotations from the sample Namespace YAML excerpt on the &lt;strong&gt;Namespace&lt;/strong&gt; tab in the &lt;a href=&#34;/docs/configure/#quickstart-templates&#34;&gt;Copy a template&lt;/a&gt; section of the configuration topic.&lt;/p&gt;&#xA; &lt;/div&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Save your changes.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;If you chose to run the &lt;code&gt;kubectl get namespace NAMESPACE -o yaml &amp;gt; FILENAME ...&lt;/code&gt; command in step 1, apply your changes.&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-shell&#34; data-lang=&#34;shell&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;kubectl apply -f FILENAME&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Optional: Confirm your changes by running the following command and then reviewing the annotations in the &lt;code&gt;metadata.annotations&lt;/code&gt; section of the output:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-shell&#34; data-lang=&#34;shell&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;kubectl get namespace NAMESPACE -o yaml&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/li&gt;&#xA;&lt;/ol&gt;</description>
			</item>
			<item>
				<title>Configure optimization for individual workloads</title>
				<link>/docs/configure/annotate-workloads/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/configure/annotate-workloads/</guid>
				<description>&lt;p&gt;The purpose of this topic is to describe how to use annotations to configure optimization settings.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Topics:&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#annot-wl&#34;&gt;Configure optimization settings for a specific workload&lt;/a&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#annot-wl-yaml&#34;&gt;Using YAML manifests&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#annot-wl-kubectl-annotate&#34;&gt;Using &lt;code&gt;kubectl annotate&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;annot-wl&#34;&gt;Configure optimization settings for a specific workload&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#annot-wl&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;To configure settings an individual workload, edit the resource definition or run &lt;code&gt;kubectl annotate&lt;/code&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Workload optimization settings are defined by annotations in the &lt;code&gt;metadata.annotations&lt;/code&gt; section of a Deployment, StatefulSet, or other supported workload resource type.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Basic installation</title>
				<link>/docs/installation/install/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/installation/install/</guid>
				<description>&lt;h2 id=&#34;prerequisites&#34;&gt;Prerequisites&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#prerequisites&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;A Kubernetes cluster (from any Kubernetes distribution, such as EKS, AKS, GKE, minikube, or kind)&lt;/li&gt;&#xA;&lt;li&gt;A StormForge account — sign up for free at &lt;strong&gt;&lt;a href=&#34;https://app.stormforge.io/signup&#34;&gt;app.stormforge.io/signup&lt;/a&gt;&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;li&gt;In an enterprise environment, make sure a system administrator has addressed &lt;a href=&#34;/docs/installation/install-adv/#prerequisites&#34;&gt;additional prerequisites (such as firewall rules and proxies)&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;install-stormforge&#34;&gt;Install StormForge&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#install-stormforge&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Log in to &lt;strong&gt;&lt;a href=&#34;https://app.stormforge.io/&#34;&gt;app.stormforge.io&lt;/a&gt;&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;p&gt;If you are setting up StormForge for the first time, you will be automatically taken to the &lt;strong&gt;Add Cluster&lt;/strong&gt; page — continue to step 3.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Click &lt;strong&gt;Clusters&lt;/strong&gt; in the left navigation; then, on the &lt;strong&gt;Clusters&lt;/strong&gt; page, click &lt;strong&gt;Add Cluster&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Give your cluster a name and click &lt;strong&gt;Continue&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;p&gt;The name can&amp;rsquo;t exceed 63 characters, can&amp;rsquo;t start or end with a dash (&lt;code&gt;-&lt;/code&gt;), and must follow the &lt;a href=&#34;https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#dns-label-names&#34;&gt;RFC 1123 DNS label standard&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Install StormForge: Copy and run the generated &lt;code&gt;helm install&lt;/code&gt; command, which looks similar to the following (where &lt;code&gt;my-cluster&lt;/code&gt; is the name you chose for this cluster, and &lt;code&gt;CLIENT_ID&lt;/code&gt; and &lt;code&gt;CLIENT_SECRET&lt;/code&gt; are generated alphanumeric strings).&lt;/p&gt;&#xA;&lt;p&gt;This installs the Agent, Applier, and Forwarder into the &lt;code&gt;stormforge-system&lt;/code&gt; namespace. To collect GPU metrics, enable the &lt;a href=&#34;/docs/installation/node-agent-config/&#34;&gt;Node Agent&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-shell&#34; data-lang=&#34;shell&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;helm install stormforge oci://registry.stormforge.io/library/stormforge &lt;span style=&#34;color:#ae81ff&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  --create-namespace --namespace stormforge-system &lt;span style=&#34;color:#ae81ff&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  --set clusterName&lt;span style=&#34;color:#f92672&#34;&gt;=&lt;/span&gt;&lt;span style=&#34;color:#e6db74&#34;&gt;&amp;#34;my-cluster&amp;#34;&lt;/span&gt; &lt;span style=&#34;color:#ae81ff&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  --set authorization.clientID&lt;span style=&#34;color:#f92672&#34;&gt;=&lt;/span&gt;&lt;span style=&#34;color:#e6db74&#34;&gt;&amp;#34;CLIENT_ID&amp;#34;&lt;/span&gt; &lt;span style=&#34;color:#ae81ff&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  --set authorization.clientSecret&lt;span style=&#34;color:#f92672&#34;&gt;=&lt;/span&gt;&lt;span style=&#34;color:#e6db74&#34;&gt;&amp;#34;CLIENT_SECRET&amp;#34;&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;To install without the Applier, add &lt;code&gt;--set applier.enabled=false&lt;/code&gt; to the command.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ol&gt;</description>
			</item>
			<item>
				<title>Best practices</title>
				<link>/docs/reference/best-practices/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/reference/best-practices/</guid>
				<description>&lt;p&gt;Get the most value out of StormForge and minimize unexpected results by following these best practices.&lt;/p&gt;&#xA;&lt;div class=&#34;alert alert-info&#34; role=&#34;alert&#34;&gt;&lt;div class=&#34;h4 alert-heading&#34; role=&#34;heading&#34;&gt;If you&#39;re getting started... &lt;/div&gt;&#xA;&lt;p&gt;Check out the &lt;a href=&#34;/docs/configure/configure-opt-settings/&#34;&gt;Getting started with configuring StormForge&lt;/a&gt; guide, which discusses the five most important settings and whether you need to consider adjusting them to suit your organization&amp;rsquo;s requirements.&lt;/p&gt;&#xA;&lt;/div&gt;&#xA;&lt;h2 id=&#34;workload-settings&#34;&gt;Workload settings&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#workload-settings&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;h3 id=&#34;generate-recommendations-once-daily&#34;&gt;Generate recommendations once daily&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#generate-recommendations-once-daily&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;p&gt;A once-daily recommendation schedule is considered a best practice in stable or production environments (this is the default schedule when you roll out StormForge). For details about this setting, see &lt;a href=&#34;/docs/configure/settings/schedule/&#34;&gt;Recommendation schedule&lt;/a&gt; in the Schedule topic.&lt;/p&gt;</description>
			</item>
			<item>
				<title>ClusterOptimizationConfiguration reference</title>
				<link>/docs/reference/crds/clusteroptimizationconfiguration/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/reference/crds/clusteroptimizationconfiguration/</guid>
				<description>&lt;p&gt;&lt;code&gt;apiVersion: optimize.stormforge.io/v2&lt;/code&gt;&lt;/p&gt;&#xA;&lt;p&gt;Scope: Cluster.&lt;/p&gt;&#xA;&lt;p&gt;For usage and examples, see &lt;a href=&#34;/docs/configure/optimization-configurations/&#34;&gt;Configure optimization using CRDs&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Fields marked &lt;strong&gt;*&lt;/strong&gt; are required.&lt;/p&gt;&#xA;&lt;h2 id=&#34;ClusterOptimizationConfiguration&#34;&gt;ClusterOptimizationConfiguration&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#ClusterOptimizationConfiguration&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;ClusterOptimizationConfiguration is the Schema for the ClusterOptimizationConfiguration API.&lt;/p&gt;&#xA;&lt;div class=&#34;table-scroll&#34;&gt;&#xA;&lt;div class=&#34;table-responsive&#34;&gt;&#xA;&lt;table&gt;&#xA;  &lt;thead&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;th&gt;Field&lt;/th&gt;&#xA;          &lt;th&gt;Description&lt;/th&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/thead&gt;&#xA;  &lt;tbody&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;apiVersion&lt;/code&gt;&lt;br&gt;&lt;em&gt;string&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;&lt;code&gt;optimize.stormforge.io/v2&lt;/code&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;kind&lt;/code&gt;&lt;br&gt;&lt;em&gt;string&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;&lt;code&gt;ClusterOptimizationConfiguration&lt;/code&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;metadata&lt;/code&gt;&lt;br&gt;&lt;em&gt;&lt;a href=&#34;https://kubernetes.io/docs/reference/kubernetes-api/definitions/object-meta-v1-meta/#ObjectMeta&#34;&gt;ObjectMeta&lt;/a&gt;&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;Standard object metadata.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;spec&lt;/code&gt;&lt;br&gt;&lt;em&gt;&lt;a href=&#34;#ClusterOptimizationConfigurationSpec&#34;&gt;ClusterOptimizationConfigurationSpec&lt;/a&gt;&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;ClusterOptimizationConfigurationSpec defines the desired state of ClusterOptimizationConfiguration.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/tbody&gt;&#xA;&lt;/table&gt;&#xA;&lt;/div&gt;&#xA;&lt;/div&gt;&#xA;&lt;h2 id=&#34;ClusterOptimizationConfigurationSpec&#34;&gt;ClusterOptimizationConfigurationSpec&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#ClusterOptimizationConfigurationSpec&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;ClusterOptimizationConfigurationSpec defines the desired state of ClusterOptimizationConfiguration.&lt;/p&gt;&#xA;&lt;div class=&#34;table-scroll&#34;&gt;&#xA;&lt;div class=&#34;table-responsive&#34;&gt;&#xA;&lt;table&gt;&#xA;  &lt;thead&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;th&gt;Field&lt;/th&gt;&#xA;          &lt;th&gt;Description&lt;/th&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/thead&gt;&#xA;  &lt;tbody&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;match&lt;/code&gt;&lt;br&gt;&lt;em&gt;object&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;Gating applied to every rule in this configuration. Rules may narrow further with their own match.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;match.anyOf&lt;/code&gt;&lt;br&gt;&lt;em&gt;object array&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;Terms that are OR-ed together, of which at least one must match. Each term&amp;rsquo;s own criteria are AND-ed within the term. A null or empty term matches no objects. Must contain at least 1 item.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;match.anyOf.expression&lt;/code&gt;&lt;br&gt;&lt;em&gt;string&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;CEL expression evaluated against the workload via the &lt;code&gt;object&lt;/code&gt; variable.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;match.anyOf.namespaceSelector&lt;/code&gt;&lt;br&gt;&lt;em&gt;string&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;Selector applied to the labels of the workload&amp;rsquo;s namespace.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;match.anyOf.objectSelector&lt;/code&gt;&lt;br&gt;&lt;em&gt;string&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;Selector applied to the labels of the workload. Named to align with the CEL &lt;code&gt;object&lt;/code&gt; variable.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;match.expression&lt;/code&gt;&lt;br&gt;&lt;em&gt;string&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;CEL expression evaluated against the workload via the &lt;code&gt;object&lt;/code&gt; variable.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;match.namespaceSelector&lt;/code&gt;&lt;br&gt;&lt;em&gt;string&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;Selector applied to the labels of the workload&amp;rsquo;s namespace.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;match.objectSelector&lt;/code&gt;&lt;br&gt;&lt;em&gt;string&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;Selector applied to the labels of the workload. Named to align with the CEL &lt;code&gt;object&lt;/code&gt; variable.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;order&lt;/code&gt;&lt;br&gt;&lt;em&gt;integer&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;Defaults to &lt;code&gt;0&lt;/code&gt;. Value must be an integer between -1000 and 1000.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;rules&lt;/code&gt;&lt;br&gt;&lt;em&gt;object array&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;ClusterOptimizationConfig defines a single optimization configuration entry. Entries are keyed on &lt;code&gt;name&lt;/code&gt;.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;rules.match&lt;/code&gt;&lt;br&gt;&lt;em&gt;object&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;ClusterMatch is the cluster-scoped counterpart of Match, combining its terms the same way. An empty ClusterMatch matches every workload.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;rules.match.anyOf&lt;/code&gt;&lt;br&gt;&lt;em&gt;object array&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;Terms that are OR-ed together, of which at least one must match. Each term&amp;rsquo;s own criteria are AND-ed within the term. A null or empty term matches no objects. Must contain at least 1 item.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;rules.match.anyOf.expression&lt;/code&gt;&lt;br&gt;&lt;em&gt;string&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;CEL expression evaluated against the workload via the &lt;code&gt;object&lt;/code&gt; variable.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;rules.match.anyOf.namespaceSelector&lt;/code&gt;&lt;br&gt;&lt;em&gt;string&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;Selector applied to the labels of the workload&amp;rsquo;s namespace.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;rules.match.anyOf.objectSelector&lt;/code&gt;&lt;br&gt;&lt;em&gt;string&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;Selector applied to the labels of the workload. Named to align with the CEL &lt;code&gt;object&lt;/code&gt; variable.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;rules.match.expression&lt;/code&gt;&lt;br&gt;&lt;em&gt;string&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;CEL expression evaluated against the workload via the &lt;code&gt;object&lt;/code&gt; variable.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;rules.match.namespaceSelector&lt;/code&gt;&lt;br&gt;&lt;em&gt;string&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;Selector applied to the labels of the workload&amp;rsquo;s namespace.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;rules.match.objectSelector&lt;/code&gt;&lt;br&gt;&lt;em&gt;string&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;Selector applied to the labels of the workload. Named to align with the CEL &lt;code&gt;object&lt;/code&gt; variable.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;rules.name&lt;/code&gt; &lt;strong&gt;*&lt;/strong&gt;&lt;br&gt;&lt;em&gt;string&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;rules.settings&lt;/code&gt; &lt;strong&gt;*&lt;/strong&gt;&lt;br&gt;&lt;em&gt;object array&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;ConfigItem represents a single configuration entry with a name and one or more values. Entries are keyed on &lt;code&gt;name&lt;/code&gt;. Either value or values must be set, but not both.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;rules.settings.name&lt;/code&gt; &lt;strong&gt;*&lt;/strong&gt;&lt;br&gt;&lt;em&gt;string&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;rules.settings.value&lt;/code&gt;&lt;br&gt;&lt;em&gt;string&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;rules.settings.values&lt;/code&gt;&lt;br&gt;&lt;em&gt;string array&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/tbody&gt;&#xA;&lt;/table&gt;&#xA;&lt;/div&gt;&#xA;&lt;/div&gt;</description>
			</item>
			<item>
				<title>Common StormForge CLI workflows</title>
				<link>/docs/stormforge-cli/common-cli-workflows/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/stormforge-cli/common-cli-workflows/</guid>
				<description>&lt;p&gt;The StormForge CLI lets you interact with StormForge to inspect workloads, view optimization data, and manage recommendations.&lt;/p&gt;&#xA;&lt;p&gt;This guide covers common workflows:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Authenticate and configure the CLI&lt;/li&gt;&#xA;&lt;li&gt;Explore clusters and workloads&lt;/li&gt;&#xA;&lt;li&gt;Find workloads with auto-deploy enabled&lt;/li&gt;&#xA;&lt;li&gt;View and generate recommendations&lt;/li&gt;&#xA;&lt;li&gt;Query recommendation data&lt;/li&gt;&#xA;&lt;li&gt;Apply recommendations to workloads&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Typical workflow:&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;Identify workload → Inspect recommendation → Apply recommendation&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Common workflow commands:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-sh&#34; data-lang=&#34;sh&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;stormforge get workloads --cluster &amp;lt;cluster&amp;gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;stormforge get recommendations --cluster &amp;lt;cluster&amp;gt; --namespace &amp;lt;namespace&amp;gt; --name &amp;lt;workload&amp;gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;stormforge apply --cluster &amp;lt;cluster&amp;gt; --namespace &amp;lt;namespace&amp;gt; --resource &amp;lt;resource-type&amp;gt; --name &amp;lt;workload&amp;gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;hr&gt;&#xA;&lt;h2 id=&#34;in-this-guide&#34;&gt;In this guide&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#in-this-guide&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#common-commands&#34;&gt;Common commands&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#get-started&#34;&gt;Get started with the CLI&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#explore&#34;&gt;Explore clusters and workloads&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#find-auto-deploy&#34;&gt;Find workloads with auto-deploy enabled&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#view-recs&#34;&gt;View and generate recommendations&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#query-recs&#34;&gt;Query recommendation data&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#apply-recs&#34;&gt;Apply recommendations&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;common-commands&#34;&gt;Common commands&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#common-commands&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;div class=&#34;table-scroll&#34;&gt;&#xA;&lt;div class=&#34;table-responsive&#34;&gt;&#xA;&lt;table&gt;&#xA;  &lt;thead&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;th&gt;Task&lt;/th&gt;&#xA;          &lt;th&gt;Command&lt;/th&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/thead&gt;&#xA;  &lt;tbody&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;Authenticate&lt;/td&gt;&#xA;          &lt;td&gt;&lt;a href=&#34;/docs/stormforge-cli/reference/#stormforge-login&#34;&gt;&lt;code&gt;stormforge login&lt;/code&gt;&lt;/a&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;List clusters&lt;/td&gt;&#xA;          &lt;td&gt;&lt;a href=&#34;/docs/stormforge-cli/reference/#stormforge-get-clusters&#34;&gt;&lt;code&gt;stormforge get clusters&lt;/code&gt;&lt;/a&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;List workloads&lt;/td&gt;&#xA;          &lt;td&gt;&lt;a href=&#34;/docs/stormforge-cli/reference/#stormforge-get-workloads&#34;&gt;&lt;code&gt;stormforge get workloads&lt;/code&gt;&lt;/a&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;View workloads&lt;/td&gt;&#xA;          &lt;td&gt;&lt;a href=&#34;/docs/stormforge-cli/reference/#stormforge-view-workloads&#34;&gt;&lt;code&gt;stormforge view workloads&lt;/code&gt;&lt;/a&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;List recommendations&lt;/td&gt;&#xA;          &lt;td&gt;&lt;a href=&#34;/docs/stormforge-cli/reference/#stormforge-get-recommendations&#34;&gt;&lt;code&gt;stormforge get recommendations&lt;/code&gt;&lt;/a&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;Create recommendation&lt;/td&gt;&#xA;          &lt;td&gt;&lt;a href=&#34;/docs/stormforge-cli/reference/#stormforge-create-recommendation&#34;&gt;&lt;code&gt;stormforge create recommendation&lt;/code&gt;&lt;/a&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;Apply recommendations&lt;/td&gt;&#xA;          &lt;td&gt;&lt;a href=&#34;/docs/stormforge-cli/reference/#stormforge-apply&#34;&gt;&lt;code&gt;stormforge apply&lt;/code&gt;&lt;/a&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/tbody&gt;&#xA;&lt;/table&gt;&#xA;&lt;/div&gt;&#xA;&lt;/div&gt;&#xA;&lt;div class=&#34;alert alert-info&#34; role=&#34;alert&#34;&gt;&lt;div class=&#34;h4 alert-heading&#34; role=&#34;heading&#34;&gt;Using command help in the CLI&lt;/div&gt;&#xA;&lt;p&gt;Use the &lt;code&gt;--help&lt;/code&gt; flag with any command for more information.&lt;/p&gt;&#xA;&lt;/div&gt;</description>
			</item>
			<item>
				<title>Optimization goal</title>
				<link>/docs/configure/settings/goal/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/configure/settings/goal/</guid>
				<description>&lt;p&gt;StormForge always recommends values that minimally satisfy both savings and reliability, but you can set goals to shift the balance in favor of one or the other based on your risk tolerance and optimization goals.&lt;/p&gt;&#xA;&lt;p&gt;The optimization goal applies to the entire workload.&lt;/p&gt;&#xA;&lt;h2 id=&#34;opt-goal&#34;&gt;Optimization goal&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#opt-goal&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;Used in determining recommended values based on your goals and risk tolerance.&lt;/p&gt;&#xA;&lt;div class=&#34;table-scroll&#34;&gt;&#xA;&lt;div class=&#34;table-responsive&#34;&gt;&#xA;&lt;table&gt;&#xA;  &lt;thead&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;th&gt;Annotation&lt;/th&gt;&#xA;          &lt;th&gt;Default value&lt;/th&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/thead&gt;&#xA;  &lt;tbody&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;live.stormforge.io/cpu.optimization-goal&lt;/code&gt;&lt;/td&gt;&#xA;          &lt;td&gt;&lt;code&gt;&amp;quot;Balanced&amp;quot;&lt;/code&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;live.stormforge.io/memory.optimization-goal&lt;/code&gt;&lt;/td&gt;&#xA;          &lt;td&gt;&lt;code&gt;&amp;quot;Balanced&amp;quot;&lt;/code&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/tbody&gt;&#xA;&lt;/table&gt;&#xA;&lt;/div&gt;&#xA;&lt;/div&gt;&#xA;&lt;h3 id=&#34;opt-goal-description&#34;&gt;Description&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#opt-goal-description&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;p&gt;The optimization goal for a resource indicates which of two competing criteria to maximize when computing recommended request values: cost savings or workload reliability. StormForge will always produce values that minimally satisfy both criteria, but the goal setting can be used to shift the balance in favor of one or the other.&lt;/p&gt;</description>
			</item>
			<item>
				<title>OptimizationConfiguration reference</title>
				<link>/docs/reference/crds/optimizationconfiguration/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/reference/crds/optimizationconfiguration/</guid>
				<description>&lt;p&gt;&lt;code&gt;apiVersion: optimize.stormforge.io/v2&lt;/code&gt;&lt;/p&gt;&#xA;&lt;p&gt;Scope: Namespaced.&lt;/p&gt;&#xA;&lt;p&gt;For usage and examples, see &lt;a href=&#34;/docs/configure/optimization-configurations/&#34;&gt;Configure optimization using CRDs&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Fields marked &lt;strong&gt;*&lt;/strong&gt; are required.&lt;/p&gt;&#xA;&lt;h2 id=&#34;OptimizationConfiguration&#34;&gt;OptimizationConfiguration&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#OptimizationConfiguration&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;OptimizationConfiguration is the Schema for the OptimizationConfiguration API.&lt;/p&gt;&#xA;&lt;div class=&#34;table-scroll&#34;&gt;&#xA;&lt;div class=&#34;table-responsive&#34;&gt;&#xA;&lt;table&gt;&#xA;  &lt;thead&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;th&gt;Field&lt;/th&gt;&#xA;          &lt;th&gt;Description&lt;/th&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/thead&gt;&#xA;  &lt;tbody&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;apiVersion&lt;/code&gt;&lt;br&gt;&lt;em&gt;string&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;&lt;code&gt;optimize.stormforge.io/v2&lt;/code&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;kind&lt;/code&gt;&lt;br&gt;&lt;em&gt;string&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;&lt;code&gt;OptimizationConfiguration&lt;/code&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;metadata&lt;/code&gt;&lt;br&gt;&lt;em&gt;&lt;a href=&#34;https://kubernetes.io/docs/reference/kubernetes-api/definitions/object-meta-v1-meta/#ObjectMeta&#34;&gt;ObjectMeta&lt;/a&gt;&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;Standard object metadata.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;spec&lt;/code&gt;&lt;br&gt;&lt;em&gt;&lt;a href=&#34;#OptimizationConfigurationSpec&#34;&gt;OptimizationConfigurationSpec&lt;/a&gt;&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;OptimizationConfigurationSpec defines the desired state of OptimizationConfiguration.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/tbody&gt;&#xA;&lt;/table&gt;&#xA;&lt;/div&gt;&#xA;&lt;/div&gt;&#xA;&lt;h2 id=&#34;OptimizationConfigurationSpec&#34;&gt;OptimizationConfigurationSpec&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#OptimizationConfigurationSpec&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;OptimizationConfigurationSpec defines the desired state of OptimizationConfiguration.&lt;/p&gt;&#xA;&lt;div class=&#34;table-scroll&#34;&gt;&#xA;&lt;div class=&#34;table-responsive&#34;&gt;&#xA;&lt;table&gt;&#xA;  &lt;thead&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;th&gt;Field&lt;/th&gt;&#xA;          &lt;th&gt;Description&lt;/th&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/thead&gt;&#xA;  &lt;tbody&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;match&lt;/code&gt;&lt;br&gt;&lt;em&gt;object&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;Gating applied to every rule in this configuration. Rules may narrow further with their own match.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;match.anyOf&lt;/code&gt;&lt;br&gt;&lt;em&gt;object array&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;Terms that are OR-ed together, of which at least one must match. Each term&amp;rsquo;s own criteria are AND-ed within the term. A null or empty term matches no objects. Must contain at least 1 item.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;match.anyOf.expression&lt;/code&gt;&lt;br&gt;&lt;em&gt;string&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;CEL expression evaluated against the workload via the &lt;code&gt;object&lt;/code&gt; variable.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;match.anyOf.objectSelector&lt;/code&gt;&lt;br&gt;&lt;em&gt;string&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;Selector applied to the labels of the workload. Named to align with the CEL &lt;code&gt;object&lt;/code&gt; variable.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;match.expression&lt;/code&gt;&lt;br&gt;&lt;em&gt;string&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;CEL expression evaluated against the workload via the &lt;code&gt;object&lt;/code&gt; variable.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;match.objectSelector&lt;/code&gt;&lt;br&gt;&lt;em&gt;string&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;Selector applied to the labels of the workload. Named to align with the CEL &lt;code&gt;object&lt;/code&gt; variable.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;order&lt;/code&gt;&lt;br&gt;&lt;em&gt;integer&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;Defaults to &lt;code&gt;0&lt;/code&gt;. Value must be an integer between -1000 and 1000.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;rules&lt;/code&gt;&lt;br&gt;&lt;em&gt;object array&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;OptimizationConfig defines a single optimization configuration entry. Entries are keyed on &lt;code&gt;name&lt;/code&gt;.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;rules.match&lt;/code&gt;&lt;br&gt;&lt;em&gt;object&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;Match selects the workloads a configuration applies to. The inlined MatchTerm criteria are AND-ed together, and an empty Match matches every workload. When AnyOf is also set at least one of its terms must match, and that result is AND-ed with the inlined criteria.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;rules.match.anyOf&lt;/code&gt;&lt;br&gt;&lt;em&gt;object array&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;Terms that are OR-ed together, of which at least one must match. Each term&amp;rsquo;s own criteria are AND-ed within the term. A null or empty term matches no objects. Must contain at least 1 item.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;rules.match.anyOf.expression&lt;/code&gt;&lt;br&gt;&lt;em&gt;string&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;CEL expression evaluated against the workload via the &lt;code&gt;object&lt;/code&gt; variable.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;rules.match.anyOf.objectSelector&lt;/code&gt;&lt;br&gt;&lt;em&gt;string&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;Selector applied to the labels of the workload. Named to align with the CEL &lt;code&gt;object&lt;/code&gt; variable.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;rules.match.expression&lt;/code&gt;&lt;br&gt;&lt;em&gt;string&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;CEL expression evaluated against the workload via the &lt;code&gt;object&lt;/code&gt; variable.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;rules.match.objectSelector&lt;/code&gt;&lt;br&gt;&lt;em&gt;string&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;Selector applied to the labels of the workload. Named to align with the CEL &lt;code&gt;object&lt;/code&gt; variable.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;rules.name&lt;/code&gt; &lt;strong&gt;*&lt;/strong&gt;&lt;br&gt;&lt;em&gt;string&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;rules.settings&lt;/code&gt; &lt;strong&gt;*&lt;/strong&gt;&lt;br&gt;&lt;em&gt;object array&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;ConfigItem represents a single configuration entry with a name and one or more values. Entries are keyed on &lt;code&gt;name&lt;/code&gt;. Either value or values must be set, but not both.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;rules.settings.name&lt;/code&gt; &lt;strong&gt;*&lt;/strong&gt;&lt;br&gt;&lt;em&gt;string&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;rules.settings.value&lt;/code&gt;&lt;br&gt;&lt;em&gt;string&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;rules.settings.values&lt;/code&gt;&lt;br&gt;&lt;em&gt;string array&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/tbody&gt;&#xA;&lt;/table&gt;&#xA;&lt;/div&gt;&#xA;&lt;/div&gt;</description>
			</item>
			<item>
				<title>Requests and limits</title>
				<link>/docs/recommendations/requests-and-limits/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/recommendations/requests-and-limits/</guid>
				<description>&lt;p&gt;Every StormForge recommendation includes CPU and memory requests that the machine learning has determined to be optimal for each container in a workload.&lt;/p&gt;&#xA;&lt;p&gt;StormForge generates CPU and memory recommendations using our patent pending machine learning. Our machine learning examines each container&amp;rsquo;s resource usage metrics, and monitors usage patterns and scaling behavior to come up with the optimal CPU and memory resource settings.&lt;/p&gt;&#xA;&lt;h2 id=&#34;requests&#34;&gt;Requests&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#requests&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;Request recommendations for CPU and memory are based on observed resource usage, constrained by optimization settings. After the machine learning generates recommendation candidates, an effective recommendation is created by:&lt;/p&gt;</description>
			</item>
			<item>
				<title>Try a sample application on your own cluster</title>
				<link>/docs/guides/showcase-app/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/guides/showcase-app/</guid>
				<description>&lt;p&gt;The Showcase application is a sample application we developed to create load, enabling you to experiment with StormForge on your own cluster: generate, view, and apply recommendations, observe how our machine learning rightsizes workloads, and set values to generate recommendations based on your organizational needs.&lt;/p&gt;&#xA;&lt;p&gt;This application creates a single Kubernetes Deployment (workload) that generates variable load using one CPU core for 24 hours. StormForge collects metrics on this workload and generates recommendations to rightsize it.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Connect AI agents to StormForge with MCP</title>
				<link>/docs/guides/mcp-server/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/guides/mcp-server/</guid>
				<description>&lt;p&gt;StormForge runs a hosted &lt;a href=&#34;https://modelcontextprotocol.io/&#34;&gt;Model Context Protocol (MCP)&lt;/a&gt; server, so AI agents such as Claude Code can answer questions about your clusters, workloads, and recommendations. The hosted server is read-only by default, and you connect to it with your StormForge account.&lt;/p&gt;&#xA;&lt;p&gt;The StormForge CLI also includes a &lt;a href=&#34;#use-the-local-mcp-server&#34;&gt;local MCP server&lt;/a&gt; for MCP clients that can&amp;rsquo;t connect to the hosted server.&lt;/p&gt;&#xA;&lt;h2 id=&#34;hosted-server-url&#34;&gt;Hosted server URL&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#hosted-server-url&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-text&#34; data-lang=&#34;text&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;https://api.stormforge.io/mcp&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;The server uses streamable HTTP transport. Your AI agent signs you in through your browser the first time it connects; there are no API keys to create or store.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Advanced installation</title>
				<link>/docs/installation/install-adv/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/installation/install-adv/</guid>
				<description>&lt;h2 id=&#34;prerequisites&#34;&gt;Prerequisites&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#prerequisites&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;A &lt;a href=&#34;https://app.stormforge.io/&#34;&gt;StormForge Account&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;Kubernetes version 1.24 or later&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;helm&lt;/code&gt; version 3.14.0 or later&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;kubectl&lt;/code&gt; configured with access to your cluster&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;cluster-admin&lt;/code&gt; access (for installation only)&lt;/li&gt;&#xA;&lt;li&gt;A Kubernetes cluster and a name to identify it in StormForge.&lt;br&gt;&#xA;The name cannot exceed 63 characters, cannot start or end with a dash (&lt;code&gt;-&lt;/code&gt;), and must follow the &lt;a href=&#34;https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#dns-label-names&#34;&gt;RFC 1123 DNS label standard&lt;/a&gt;.&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#if-you-have-a-proxy-server&#34;&gt;Configure a proxy&lt;/a&gt;, if needed&lt;/li&gt;&#xA;&lt;li&gt;If you use a private container registry, &lt;a href=&#34;#if-you-have-a-private-container-registry&#34;&gt;import the required containers&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;Configure firewall rules, including granting Kubernetes clusters access to these StormForge service endpoints on port 443:&#xA;&lt;ul&gt;&#xA;&lt;li&gt;api.stormforge.io&lt;/li&gt;&#xA;&lt;li&gt;in.stormforge.io&lt;/li&gt;&#xA;&lt;li&gt;registry.stormforge.io*&lt;br&gt;&#xA;&lt;em&gt;(*If you configure the Agent to use an internal registry, you don&amp;rsquo;t need to grant cluster access to this endpoint)&lt;/em&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;set-up-the-stormforge-cli&#34;&gt;Set up the StormForge CLI&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#set-up-the-stormforge-cli&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;The StormForge CLI is used to authenticate, retrieve credentials, and register StormForge on your Kubernetes cluster.&lt;/p&gt;</description>
			</item>
			<item>
				<title>ClusterOptimizationConfiguration v1 reference</title>
				<link>/docs/reference/crds/clusteroptimizationconfiguration-v1/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/reference/crds/clusteroptimizationconfiguration-v1/</guid>
				<description>&lt;div class=&#34;alert alert-warning&#34; role=&#34;alert&#34;&gt;&lt;div class=&#34;h4 alert-heading&#34; role=&#34;heading&#34;&gt;Deprecated&lt;/div&gt;&#xA;&lt;p&gt;optimize.stormforge.io/v1 is deprecated; use v2. The v1 representation is reconstructed and is not preserved if the object is modified at v2.&#xA;See the &lt;a href=&#34;/docs/reference/crds/clusteroptimizationconfiguration/&#34;&gt;ClusterOptimizationConfiguration reference&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;/div&gt;&#xA;&lt;p&gt;&lt;code&gt;apiVersion: optimize.stormforge.io/v1&lt;/code&gt;&lt;/p&gt;&#xA;&lt;p&gt;Scope: Cluster.&lt;/p&gt;&#xA;&lt;p&gt;For usage and examples, see &lt;a href=&#34;/docs/configure/optimization-configurations/&#34;&gt;Configure optimization using CRDs&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Fields marked &lt;strong&gt;*&lt;/strong&gt; are required.&lt;/p&gt;&#xA;&lt;h2 id=&#34;ClusterOptimizationConfiguration&#34;&gt;ClusterOptimizationConfiguration&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#ClusterOptimizationConfiguration&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;ClusterOptimizationConfiguration is the Schema for the ClusterOptimizationConfiguration API.&lt;/p&gt;&#xA;&lt;div class=&#34;table-scroll&#34;&gt;&#xA;&lt;div class=&#34;table-responsive&#34;&gt;&#xA;&lt;table&gt;&#xA;  &lt;thead&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;th&gt;Field&lt;/th&gt;&#xA;          &lt;th&gt;Description&lt;/th&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/thead&gt;&#xA;  &lt;tbody&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;apiVersion&lt;/code&gt;&lt;br&gt;&lt;em&gt;string&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;&lt;code&gt;optimize.stormforge.io/v1&lt;/code&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;kind&lt;/code&gt;&lt;br&gt;&lt;em&gt;string&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;&lt;code&gt;ClusterOptimizationConfiguration&lt;/code&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;metadata&lt;/code&gt;&lt;br&gt;&lt;em&gt;&lt;a href=&#34;https://kubernetes.io/docs/reference/kubernetes-api/definitions/object-meta-v1-meta/#ObjectMeta&#34;&gt;ObjectMeta&lt;/a&gt;&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;Standard object metadata.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;spec&lt;/code&gt;&lt;br&gt;&lt;em&gt;&lt;a href=&#34;#ClusterOptimizationConfigurationSpec&#34;&gt;ClusterOptimizationConfigurationSpec&lt;/a&gt;&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;ClusterOptimizationConfigurationSpec defines the desired state of ClusterOptimizationConfiguration.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/tbody&gt;&#xA;&lt;/table&gt;&#xA;&lt;/div&gt;&#xA;&lt;/div&gt;&#xA;&lt;h2 id=&#34;ClusterOptimizationConfigurationSpec&#34;&gt;ClusterOptimizationConfigurationSpec&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#ClusterOptimizationConfigurationSpec&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;ClusterOptimizationConfigurationSpec defines the desired state of ClusterOptimizationConfiguration.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Java heap size</title>
				<link>/docs/recommendations/java/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/recommendations/java/</guid>
				<description>&lt;p&gt;StormForge recommendations can optionally include the Java max heap size that the machine learning has determined to be optimal for each Java container in a workload.&lt;/p&gt;&#xA;&lt;p&gt;When configured, StormForge automatically analyzes critical Java metrics—such as heap and non-heap usage, as well as garbage collection data—and provides tailored recommendations for heap size adjustments alongside its recommendations for the container&amp;rsquo;s requests and limits.&lt;/p&gt;&#xA;&lt;h2 id=&#34;enabling-heap-size-recommendations&#34;&gt;Enabling heap size recommendations&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#enabling-heap-size-recommendations&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;To create Java Heap size recommendations, the StormForge Agent must be configured to collect JMX metrics. Use the &lt;code&gt;jvmWorkloadConfigs&lt;/code&gt; Helm parameter to accomplish this.&lt;/p&gt;</description>
			</item>
			<item>
				<title>OptimizationConfiguration v1 reference</title>
				<link>/docs/reference/crds/optimizationconfiguration-v1/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/reference/crds/optimizationconfiguration-v1/</guid>
				<description>&lt;div class=&#34;alert alert-warning&#34; role=&#34;alert&#34;&gt;&lt;div class=&#34;h4 alert-heading&#34; role=&#34;heading&#34;&gt;Deprecated&lt;/div&gt;&#xA;&lt;p&gt;optimize.stormforge.io/v1 is deprecated; use v2. The v1 representation is reconstructed and is not preserved if the object is modified at v2.&#xA;See the &lt;a href=&#34;/docs/reference/crds/optimizationconfiguration/&#34;&gt;OptimizationConfiguration reference&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;/div&gt;&#xA;&lt;p&gt;&lt;code&gt;apiVersion: optimize.stormforge.io/v1&lt;/code&gt;&lt;/p&gt;&#xA;&lt;p&gt;Scope: Namespaced.&lt;/p&gt;&#xA;&lt;p&gt;For usage and examples, see &lt;a href=&#34;/docs/configure/optimization-configurations/&#34;&gt;Configure optimization using CRDs&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Fields marked &lt;strong&gt;*&lt;/strong&gt; are required.&lt;/p&gt;&#xA;&lt;h2 id=&#34;OptimizationConfiguration&#34;&gt;OptimizationConfiguration&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#OptimizationConfiguration&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;OptimizationConfiguration is the Schema for the OptimizationConfiguration API.&lt;/p&gt;&#xA;&lt;div class=&#34;table-scroll&#34;&gt;&#xA;&lt;div class=&#34;table-responsive&#34;&gt;&#xA;&lt;table&gt;&#xA;  &lt;thead&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;th&gt;Field&lt;/th&gt;&#xA;          &lt;th&gt;Description&lt;/th&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/thead&gt;&#xA;  &lt;tbody&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;apiVersion&lt;/code&gt;&lt;br&gt;&lt;em&gt;string&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;&lt;code&gt;optimize.stormforge.io/v1&lt;/code&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;kind&lt;/code&gt;&lt;br&gt;&lt;em&gt;string&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;&lt;code&gt;OptimizationConfiguration&lt;/code&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;metadata&lt;/code&gt;&lt;br&gt;&lt;em&gt;&lt;a href=&#34;https://kubernetes.io/docs/reference/kubernetes-api/definitions/object-meta-v1-meta/#ObjectMeta&#34;&gt;ObjectMeta&lt;/a&gt;&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;Standard object metadata.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;spec&lt;/code&gt;&lt;br&gt;&lt;em&gt;&lt;a href=&#34;#OptimizationConfigurationSpec&#34;&gt;OptimizationConfigurationSpec&lt;/a&gt;&lt;/em&gt;&lt;/td&gt;&#xA;          &lt;td&gt;OptimizationConfigurationSpec defines the desired state of OptimizationConfiguration.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/tbody&gt;&#xA;&lt;/table&gt;&#xA;&lt;/div&gt;&#xA;&lt;/div&gt;&#xA;&lt;h2 id=&#34;OptimizationConfigurationSpec&#34;&gt;OptimizationConfigurationSpec&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#OptimizationConfigurationSpec&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;OptimizationConfigurationSpec defines the desired state of OptimizationConfiguration.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Schedule</title>
				<link>/docs/configure/settings/schedule/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/configure/settings/schedule/</guid>
				<description>&lt;p&gt;Following the &lt;em&gt;learning period&lt;/em&gt;, StormForge generates recommendations at the interval defined by the &lt;em&gt;schedule&lt;/em&gt;. An optional recommendation &lt;em&gt;validity period&lt;/em&gt; can be configured independently from the recommendation schedule.&lt;/p&gt;&#xA;&lt;p&gt;For more details and examples showing how these settings are related, see the &lt;a href=&#34;/docs/concepts/#schedule&#34;&gt;Schedule&lt;/a&gt;, &lt;a href=&#34;/docs/concepts/#validity-period&#34;&gt;Validity period&lt;/a&gt;, &lt;a href=&#34;/docs/concepts/#learning-period&#34;&gt;Learning period&lt;/a&gt;, and &lt;a href=&#34;/docs/recommendations/#prel-recs-concepts&#34;&gt;Preliminary recommendations&lt;/a&gt; sections in the Concepts topic.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Recommendation settings:&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#schedule&#34;&gt;Recommendation schedule&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#validity-period&#34;&gt;Validity period&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;schedule&#34;&gt;Schedule&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#schedule&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;The schedule on which StormForge generates new recommendations for a workload.&lt;/p&gt;&#xA;&lt;div class=&#34;table-scroll&#34;&gt;&#xA;&lt;div class=&#34;table-responsive&#34;&gt;&#xA;&lt;table&gt;&#xA;  &lt;thead&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;th&gt;Annotation&lt;/th&gt;&#xA;          &lt;th&gt;Default value&lt;/th&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/thead&gt;&#xA;  &lt;tbody&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;live.stormforge.io/schedule&lt;/code&gt;&lt;/td&gt;&#xA;          &lt;td&gt;&lt;code&gt;&amp;quot;@daily&amp;quot;&lt;/code&gt; (equivalent to &lt;code&gt;P1D&lt;/code&gt;)&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/tbody&gt;&#xA;&lt;/table&gt;&#xA;&lt;/div&gt;&#xA;&lt;/div&gt;&#xA;&lt;h3 id=&#34;schedule-description&#34;&gt;Description&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#schedule-description&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;p&gt;Recommendations are generated automatically for workloads on a schedule, defined by a schedule string. The shortest valid recommendation schedule is once an hour.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Try the StormForge sandbox</title>
				<link>/docs/guides/sandbox/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/guides/sandbox/</guid>
				<description>&lt;p&gt;If you don&amp;rsquo;t have a cluster of your own, you can check out StormForge running in a view-only sandbox.&lt;/p&gt;&#xA;&lt;p&gt;The sandbox contains two clusters, each running the same simulated e-commerce application.&lt;/p&gt;&#xA;&lt;p&gt;This guide walks you through a comparison of optimized and non-optimized workloads, showing you how StormForge machine learning rightsizes your workloads based on the metrics it collects.&lt;/p&gt;&#xA;&lt;h2 id=&#34;access-the-sandbox&#34;&gt;Access the sandbox&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#access-the-sandbox&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;To preview StormForge with view-only privileges, without installing anything, fill out the &lt;a href=&#34;https://www.cloudbolt.io/stormforge-sandbox-signup&#34;&gt;&lt;strong&gt;StormForge sandbox sign-up form&lt;/strong&gt;&lt;/a&gt; for instant access.&lt;/p&gt;</description>
			</item>
			<item>
				<title>User roles</title>
				<link>/docs/reference/user-roles/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/reference/user-roles/</guid>
				<description>&lt;p&gt;StormForge uses role-based access control. Each user in your organization is assigned one of the following roles.&lt;/p&gt;&#xA;&lt;div class=&#34;table-scroll&#34;&gt;&#xA;&lt;div class=&#34;table-responsive&#34;&gt;&#xA;&lt;table class=&#34;td-initial table&#34;&gt;&#xA;  &lt;thead&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;th&gt;Role&lt;/th&gt;&#xA;          &lt;th&gt;Permissions&lt;/th&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/thead&gt;&#xA;  &lt;tbody&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;strong&gt;Viewer&lt;/strong&gt;&lt;/td&gt;&#xA;          &lt;td&gt;View optimization data and export recommendations&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;strong&gt;Operator&lt;/strong&gt;&lt;/td&gt;&#xA;          &lt;td&gt;Apply and export recommendations; configure workloads&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;strong&gt;Manager&lt;/strong&gt;&lt;/td&gt;&#xA;          &lt;td&gt;Invite users (not suspend); all Operator permissions&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;strong&gt;Administrator&lt;/strong&gt;&lt;/td&gt;&#xA;          &lt;td&gt;Invite and suspend users; configure global settings&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/tbody&gt;&#xA;&lt;/table&gt;&#xA;&lt;/div&gt;&#xA;&lt;/div&gt;&#xA;&lt;p&gt;Operators, Managers, and Administrators can also add and revoke Access Credentials under &lt;strong&gt;Settings &amp;gt; Access Credentials&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;h2 id=&#34;role-comparison&#34;&gt;Role comparison&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#role-comparison&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;div class=&#34;table-scroll&#34;&gt;&#xA;&lt;div class=&#34;table-responsive&#34;&gt;&#xA;&lt;table class=&#34;td-initial table&#34;&gt;&#xA;  &lt;thead&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;th&gt;Action&lt;/th&gt;&#xA;          &lt;th style=&#34;text-align: center&#34;&gt;Viewer&lt;/th&gt;&#xA;          &lt;th style=&#34;text-align: center&#34;&gt;Operator&lt;/th&gt;&#xA;          &lt;th style=&#34;text-align: center&#34;&gt;Manager&lt;/th&gt;&#xA;          &lt;th style=&#34;text-align: center&#34;&gt;Administrator&lt;/th&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/thead&gt;&#xA;  &lt;tbody&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;View optimization data&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: center&#34;&gt;✓&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: center&#34;&gt;✓&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: center&#34;&gt;✓&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: center&#34;&gt;✓&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;Export recommendations&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: center&#34;&gt;✓&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: center&#34;&gt;✓&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: center&#34;&gt;✓&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: center&#34;&gt;✓&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;Apply recommendations&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: center&#34;&gt;&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: center&#34;&gt;✓&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: center&#34;&gt;✓&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: center&#34;&gt;✓&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;Configure workloads&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: center&#34;&gt;&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: center&#34;&gt;✓&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: center&#34;&gt;✓&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: center&#34;&gt;✓&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;Add/revoke Access Credentials&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: center&#34;&gt;&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: center&#34;&gt;✓&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: center&#34;&gt;✓&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: center&#34;&gt;✓&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;Invite users&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: center&#34;&gt;&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: center&#34;&gt;&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: center&#34;&gt;✓&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: center&#34;&gt;✓&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;Suspend users&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: center&#34;&gt;&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: center&#34;&gt;&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: center&#34;&gt;&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: center&#34;&gt;✓&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;Configure global settings&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: center&#34;&gt;&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: center&#34;&gt;&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: center&#34;&gt;&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: center&#34;&gt;✓&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/tbody&gt;&#xA;&lt;/table&gt;&#xA;&lt;/div&gt;&#xA;&lt;/div&gt;</description>
			</item>
			<item>
				<title>Agent configuration</title>
				<link>/docs/installation/cluster-agent-config/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/installation/cluster-agent-config/</guid>
				<description>&lt;p&gt;This topic describes the additional parameters available for configuring the StormForge Agent, as well as shared top-level parameters that apply to all StormForge components. For parameters that apply to the StormForge Applier, see the &lt;a href=&#34;/docs/installation/applier-config/&#34;&gt;Applier configuration&lt;/a&gt; topic.&lt;/p&gt;&#xA;&lt;h2 id=&#34;applying-these-settings&#34;&gt;Applying these settings&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#applying-these-settings&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;These are Helm values for the &lt;code&gt;stormforge&lt;/code&gt; chart. Add them to a YAML values file (for example, &lt;code&gt;values.yaml&lt;/code&gt;) and pass it to your Helm command.&lt;/p&gt;&#xA;&lt;p&gt;At install time:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-shell&#34; data-lang=&#34;shell&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;helm install stormforge oci://registry.stormforge.io/library/stormforge &lt;span style=&#34;color:#ae81ff&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  --namespace stormforge-system &lt;span style=&#34;color:#ae81ff&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  -f values.yaml&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;To apply changes after installation:&lt;/p&gt;</description>
			</item>
			<item>
				<title>Apply settings</title>
				<link>/docs/configure/settings/apply-settings/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/configure/settings/apply-settings/</guid>
				<description>&lt;p&gt;Define how StormForge deploys generated recommendations.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Apply settings:&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#auto-deploy&#34;&gt;Auto-deploy&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#learning-period&#34;&gt;Learning period&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#thresholds&#34;&gt;Auto-deploy thresholds&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#apply-method&#34;&gt;Apply method&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#pod-template-metadata&#34;&gt;Pod template metadata&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#incremental-rollout&#34;&gt;Incremental rollout&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;hr&gt;&#xA;&lt;h2 id=&#34;deploy-recommendations-automatically&#34;&gt;Deploy recommendations automatically&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#deploy-recommendations-automatically&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;These settings define whether StormForge deploys new recommendations automatically.&lt;/p&gt;&#xA;&lt;h3 id=&#34;auto-deploy&#34;&gt;Auto-deploy&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#auto-deploy&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;p&gt;When &lt;code&gt;&amp;quot;Enabled&amp;quot;&lt;/code&gt;, StormForge automatically applies new recommendations when they are generated on the configured &lt;a href=&#34;/docs/configure/settings/schedule/#schedule&#34;&gt;schedule&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;div class=&#34;table-scroll&#34;&gt;&#xA;&lt;div class=&#34;table-responsive&#34;&gt;&#xA;&lt;table&gt;&#xA;  &lt;thead&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;th&gt;Annotation&lt;/th&gt;&#xA;          &lt;th&gt;Default value&lt;/th&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/thead&gt;&#xA;  &lt;tbody&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;live.stormforge.io/auto-deploy&lt;/code&gt;&lt;/td&gt;&#xA;          &lt;td&gt;&lt;code&gt;&amp;quot;Disabled&amp;quot;&lt;/code&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/tbody&gt;&#xA;&lt;/table&gt;&#xA;&lt;/div&gt;&#xA;&lt;/div&gt;&#xA;&lt;h4 id=&#34;auto-deploy-description&#34;&gt;Description&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#auto-deploy-description&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h4&gt;&#xA;&lt;p&gt;When auto-deploy is enabled (see &lt;a href=&#34;#auto-deploy-examples&#34;&gt;Examples&lt;/a&gt; below), StormForge automatically applies new recommended settings when they are generated on the configured &lt;a href=&#34;/docs/configure/settings/schedule/#schedule&#34;&gt;schedule&lt;/a&gt;.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Configure optimization using CRDs</title>
				<link>/docs/configure/optimization-configurations/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/configure/optimization-configurations/</guid>
				<description>&lt;p&gt;StormForge&amp;rsquo;s optimization configuration options ensure consistent right-sizing across workloads and give teams control over their work.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Platform teams&lt;/strong&gt; can set organization-wide default optimization values&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Platform teams&lt;/strong&gt; can provide different default optimization values for all workloads matching a type or label selector&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Development teams&lt;/strong&gt; can fine-tune settings further for workloads in their namespaces, or for those matching specific label selectors&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Optimization configurations are Custom Resource Definitions (CRDs) consisting of &lt;a href=&#34;#rules&#34;&gt;rules&lt;/a&gt; evaluated and applied to workloads in definition order.&lt;/p&gt;</description>
			</item>
			<item>
				<title>HPA reconciliation</title>
				<link>/docs/preview/hpa-reconciliation/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/preview/hpa-reconciliation/</guid>
				<description>&lt;p&gt;The applier has a reconciliation mode in which it will watch objects associated with workloads that have recommendations applied, and automatically reconcile changes to keep workload settings in sync with the applied recommendations after events such as &lt;code&gt;helm upgrade&lt;/code&gt;.&lt;/p&gt;&#xA;&lt;p&gt;When using the webhook to apply recommendations, the only resource type that needs reconciliation is the HPA. The latest applier supports enabling reconciliation for individual resource types.&lt;/p&gt;&#xA;&lt;p&gt;To enable reconciliation for HPA resources only, use the following Helm values when installing or upgrading the applier:&lt;/p&gt;</description>
			</item>
			<item>
				<title>Manage workloads</title>
				<link>/docs/guides/workload-management/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/guides/workload-management/</guid>
				<description>&lt;p&gt;&lt;strong&gt;Topics:&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#add-workloads&#34;&gt;Adding workloads&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#delete-workloads&#34;&gt;Deleting workloads&lt;/a&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#restore-workloads&#34;&gt;Restoring workloads&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#stop-optimization&#34;&gt;Excluding a workload from optimization&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;add-workloads&#34;&gt;Adding workloads&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#add-workloads&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;StormForge automatically detects when the following types are added to a cluster:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Any Kubernetes Workload object (CronJob, DaemonSet, Deployment, ReplicaSet, StatefulSet) and HPA&lt;/li&gt;&#xA;&lt;li&gt;Workloads scaled by a KEDA-owned HPA (ScaledObjects in &lt;code&gt;keda.sh&lt;/code&gt; apiGroup)&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;When StormForge detects a new workload:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Within about 2 minutes, StormForge starts generating preliminary recommendations for the workload and updating the UI with workload and recommendation details. Preliminary recommendations cannot be applied automatically, but can be applied on demand.&#xA;StormForge generates these preliminary recommendations for the duration of the workload&amp;rsquo;s learning period.&lt;/li&gt;&#xA;&lt;li&gt;When a workload&amp;rsquo;s learning period is complete, StormForge generates recommendations that can be deployed either automatically or on demand.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Related information:&lt;/p&gt;</description>
			</item>
			<item>
				<title>Pod scheduling</title>
				<link>/docs/recommendations/pod-scheduling/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/recommendations/pod-scheduling/</guid>
				<description>&lt;p&gt;StormForge recommendations can optionally include node affinity, hard or soft, that influences the scheduler to place workloads on specific kinds of nodes.&lt;/p&gt;&#xA;&lt;p&gt;The goal of this feature is to provide better node utilization and bin packing by placing workloads on nodes that match their CPU and memory characteristics. StormForge categorizes every workload according to its &lt;code&gt;CPU:Memory&lt;/code&gt; request ratio, then adds node affinity for node types with similar &lt;code&gt;CPU:Memory&lt;/code&gt; resource ratios.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Workload recommendation statuses</title>
				<link>/docs/reference/statuses/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/reference/statuses/</guid>
				<description>&lt;p&gt;You can view workload recommendation status details in these locations:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;In workload lists on the Overview and Workloads pages&lt;/li&gt;&#xA;&lt;li&gt;On the Workloads Summary page: Click  &lt;strong&gt;View Summary&lt;/strong&gt; on the Workloads page and drill down by status, error, or warning&lt;/li&gt;&#xA;&lt;li&gt;In the &lt;strong&gt;Recommendation&lt;/strong&gt; section of the workload details page header&#xA; &lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;div class=&#34;table-scroll&#34;&gt;&#xA;&lt;div class=&#34;table-responsive&#34;&gt;&#xA;&lt;table&gt;&#xA;  &lt;thead&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;th&gt;Icon&lt;/th&gt;&#xA;          &lt;th&gt;Status&lt;/th&gt;&#xA;          &lt;th&gt;Description&lt;/th&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/thead&gt;&#xA;  &lt;tbody&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;img src=&#34;/img/docs/ol-status-wl-learning.png&#34; alt=&#34;&#34;&gt;&lt;/td&gt;&#xA;          &lt;td&gt;Learning&lt;/td&gt;&#xA;          &lt;td&gt;Indicates one of the following: &lt;strong&gt;Preliminary recommendations are available&lt;/strong&gt; based on data collected so far; complete recommendations will be available when the workload&amp;rsquo;s &lt;a href=&#34;/docs/configure/settings/apply-settings/#learning-period&#34;&gt;learning period&lt;/a&gt; is complete. &lt;strong&gt;Waiting for Data&lt;/strong&gt;: A workload (typically a CronJob) has not run yet and StormForge is waiting for data. No action required.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;img src=&#34;/img/docs/ol-status-wl-ready.png&#34; alt=&#34;&#34;&gt;&lt;/td&gt;&#xA;          &lt;td&gt;Ready&lt;/td&gt;&#xA;          &lt;td&gt;A recommendation is available to apply to this workload and will be applied if auto-deployment is enabled; otherwise, you can it apply manually.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;img src=&#34;/img/docs/ol-status-wl-info.png&#34; alt=&#34;&#34;&gt;&lt;/td&gt;&#xA;          &lt;td&gt;Informational&lt;/td&gt;&#xA;          &lt;td&gt;Provides additional details about a recommendation, for example, the recommendation was constrained by bounds, HPA is at min or max replicas. See the banner on the workload page for details. No action required.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;img src=&#34;/img/docs/ol-status-wl-unsup.png&#34; alt=&#34;&#34;&gt;&lt;/td&gt;&#xA;          &lt;td&gt;Unsupported&lt;/td&gt;&#xA;          &lt;td&gt;Recommendations are not provided in these scenarios: corrupt usage data; &lt;code&gt;batch/v1&lt;/code&gt; Jobs that run for less than 10 minutes; when an HPA oscillates between min and max replicas, scales on &amp;gt;1 resource or containerResource metric, or has a &lt;code&gt;target.averageUtilization&lt;/code&gt; &amp;gt;=100. Typically, no action is required. For details see the &lt;a href=&#34;/docs/reference/troubleshooting/#unsup&#34;&gt;Unsupported workloads&lt;/a&gt; section of the Troubleshooting topic.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;img src=&#34;/img/docs/warning_amber.png&#34; width=&#34;32&#34;&gt;&lt;/td&gt;&#xA;          &lt;td&gt;Warning&lt;/td&gt;&#xA;          &lt;td&gt;Warning types include scaled to zero, invalid workload annotation, high resource usage variance, and missing patch path configuration. For details and troubleshooting steps, see the &lt;a href=&#34;/docs/reference/troubleshooting/#errors-warnings&#34;&gt;Errors and warnings&lt;/a&gt; section of the Troubleshooting topic.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;img src=&#34;/img/docs/ol-status-wl-error.png&#34; alt=&#34;&#34;&gt;&lt;/td&gt;&#xA;          &lt;td&gt;Error&lt;/td&gt;&#xA;          &lt;td&gt;Error types include recommendation failure, missing data, expired recommendations, and applier failure. For details and troubleshooting steps, see the &lt;a href=&#34;/docs/reference/troubleshooting/#errors-warnings&#34;&gt;Errors and warnings&lt;/a&gt; section of the Troubleshooting topic.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/tbody&gt;&#xA;&lt;/table&gt;&#xA;&lt;/div&gt;&#xA;&lt;/div&gt;&#xA;&lt;div class=&#34;section-index related-topics&#34;&gt;&#xA;    &#xA;    &lt;hr class=&#34;panel-line&#34;&gt;&#xA;        &lt;h4&gt;Related topics&lt;/h4&gt;&#xA;        &lt;div class=&#34;entry&#34;&gt;&#xA;                &lt;h5&gt;&#xA;                    &#xA;                    Recommendations&lt;span class=&#34;related-topics-divider&#34;&gt;/&lt;/span&gt;&lt;a href=&#34;/docs/recommendations/view/&#34;&gt;View recommendations&lt;/a&gt;&#xA;                &lt;/h5&gt;&#xA;                &lt;p&gt;View recommendations on the Workload Details page or from the command line&lt;/p&gt;&#xA;            &lt;/div&gt;&#xA;        &lt;/div&gt;</description>
			</item>
			<item>
				<title>Applier configuration</title>
				<link>/docs/installation/applier-config/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/installation/applier-config/</guid>
				<description>&lt;p&gt;This topic describes the additional parameters available for configuring the StormForge Applier. For parameters that apply to the StormForge Agent, see the &lt;a href=&#34;/docs/installation/cluster-agent-config/&#34;&gt;Agent configuration&lt;/a&gt; topic.&lt;/p&gt;&#xA;&lt;div class=&#34;alert alert-info&#34; role=&#34;alert&#34;&gt;&#xA;&lt;p&gt;The Applier is enabled by default. To disable it, add &lt;code&gt;--set applier.enabled=false&lt;/code&gt; to your Helm install or upgrade command.&lt;/p&gt;&#xA;&lt;/div&gt;&#xA;&lt;h2 id=&#34;applying-these-settings&#34;&gt;Applying these settings&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#applying-these-settings&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;These are Helm values for the &lt;code&gt;stormforge&lt;/code&gt; chart. Add them to a YAML values file (for example, &lt;code&gt;values.yaml&lt;/code&gt;) and pass it to your Helm command.&lt;/p&gt;</description>
			</item>
			<item>
				<title>GPU optimization</title>
				<link>/docs/recommendations/gpu/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/recommendations/gpu/</guid>
				<description>&lt;p&gt;StormForge can collect GPU metrics for workloads that use NVIDIA GPUs and show each workload&amp;rsquo;s own GPU usage alongside its CPU and memory usage. The Node Agent collects these metrics. See &lt;a href=&#34;/docs/installation/node-agent-config/&#34;&gt;Node Agent configuration&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;div class=&#34;alert alert-info&#34; role=&#34;alert&#34;&gt;&lt;div class=&#34;h4 alert-heading&#34; role=&#34;heading&#34;&gt;Early access feature&lt;/div&gt;&#xA;&lt;p&gt;To share feedback on GPU optimization, &lt;a href=&#34;https://www.cloudbolt.io/company/contact-us/&#34;&gt;contact StormForge support&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;/div&gt;&#xA;&lt;h2 id=&#34;what-stormforge-shows-for-gpu-workloads&#34;&gt;What StormForge shows for GPU workloads&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#what-stormforge-shows-for-gpu-workloads&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;When a workload uses GPUs, the workload details page adds the following.&lt;/p&gt;&#xA;&lt;div class=&#34;table-scroll&#34;&gt;&#xA;&lt;div class=&#34;table-responsive&#34;&gt;&#xA;&lt;table&gt;&#xA;  &lt;thead&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;th&gt;Tab&lt;/th&gt;&#xA;          &lt;th&gt;What it shows&lt;/th&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/thead&gt;&#xA;  &lt;tbody&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;strong&gt;Summary&lt;/strong&gt;&lt;/td&gt;&#xA;          &lt;td&gt;A GPU attribute indicator, a GPU row in the resource table with per-pod and total GPU requests, and a Per-Pod GPU Memory chart plotting Usage against device memory Capacity.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;strong&gt;Recommendation&lt;/strong&gt;&lt;/td&gt;&#xA;          &lt;td&gt;A GPU column in Container Values showing the current per-container GPU count, and a GPU Memory usage chart alongside CPU and Memory showing per-container usage.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;strong&gt;GPU&lt;/strong&gt;&lt;/td&gt;&#xA;          &lt;td&gt;Aggregated GPU Device Activity for the specific GPU devices the workload ran on. Aggregation is broken down by GPU Model.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/tbody&gt;&#xA;&lt;/table&gt;&#xA;&lt;/div&gt;&#xA;&lt;/div&gt;&#xA;&lt;p&gt;The Summary and Recommendation tabs show &lt;em&gt;per-pod&lt;/em&gt; data: they show GPU information specifically attributable to the workload&amp;rsquo;s own containers. The GPU tab is &lt;em&gt;device-level&lt;/em&gt;: it shows total activity across whole GPU devices the workload was allocated, which other workloads may also be contributing to when devices are shared. The GPU tab&amp;rsquo;s Allocated GPUs line counts the distinct physical GPUs the workload&amp;rsquo;s pods hold: &lt;a href=&#34;https://docs.nvidia.com/datacenter/tesla/mig-user-guide/&#34;&gt;MIG&lt;/a&gt; devices and shared GPUs count as their physical GPU, and each physical GPU counts once.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Forwarder configuration</title>
				<link>/docs/installation/forwarder-config/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/installation/forwarder-config/</guid>
				<description>&lt;p&gt;The Forwarder collects workload metrics and forwards them to StormForge. This topic covers the additional configuration parameters available.&lt;/p&gt;&#xA;&lt;h2 id=&#34;applying-these-settings&#34;&gt;Applying these settings&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#applying-these-settings&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;These are Helm values for the &lt;code&gt;stormforge&lt;/code&gt; chart. Add them to a YAML values file (for example, &lt;code&gt;values.yaml&lt;/code&gt;) and pass it to your Helm command.&lt;/p&gt;&#xA;&lt;p&gt;At install time:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-shell&#34; data-lang=&#34;shell&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;helm install stormforge oci://registry.stormforge.io/library/stormforge &lt;span style=&#34;color:#ae81ff&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  --namespace stormforge-system &lt;span style=&#34;color:#ae81ff&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  -f values.yaml&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;To apply changes after installation:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-shell&#34; data-lang=&#34;shell&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;helm upgrade stormforge oci://registry.stormforge.io/library/stormforge &lt;span style=&#34;color:#ae81ff&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  --namespace stormforge-system &lt;span style=&#34;color:#ae81ff&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  --reset-then-reuse-values &lt;span style=&#34;color:#ae81ff&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  -f values.yaml&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;hr&gt;&#xA;&#xA;&lt;p&gt;&lt;strong&gt;Forwarder parameters:&lt;/strong&gt;&lt;/p&gt;</description>
			</item>
			<item>
				<title>Optimize job-type workloads</title>
				<link>/docs/guides/optimize-job-workloads/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/guides/optimize-job-workloads/</guid>
				<description>&lt;p&gt;If you run CronJobs, Jobs, or Spark applications, StormForge doesn&amp;rsquo;t recognize them as workloads until you declare them in &lt;code&gt;workloadResourceKinds&lt;/code&gt;. The Agent doesn&amp;rsquo;t watch these kinds by default, because job-type workloads have requirements beyond those of long-running workloads. You can declare four kinds: Kubernetes CronJobs and Jobs, and the Spark operator&amp;rsquo;s ScheduledSparkApplications and SparkApplications.&lt;/p&gt;&#xA;&lt;p&gt;StormForge generates recommendations for all four kinds, but the Applier applies them only to the scheduled kinds: CronJobs and ScheduledSparkApplications. For the one-off kinds, Jobs and SparkApplications, you apply the recommended values yourself.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Reliability response</title>
				<link>/docs/configure/settings/reliability/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/configure/settings/reliability/</guid>
				<description>&lt;p&gt;As it collects metrics, StormForge detects and reports reliability events on your workloads. You can configure StormForge to respond to an event by adding a temporary bump-up to the affected container&amp;rsquo;s resource requests.&lt;/p&gt;&#xA;&lt;p&gt;Every reliability response follows the same model:&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;StormForge detects an event on a workload, such as an OOMKill or CPU pressure on the node running the workload.&lt;/li&gt;&#xA;&lt;li&gt;StormForge generates a recommendation that includes a bump-up to the affected container&amp;rsquo;s requests, and applies it out of band if you configure it to do so.&lt;/li&gt;&#xA;&lt;li&gt;For the length of the bump-up period, subsequent scheduled recommendations keep the bump-up in place rather than returning the container to its observed usage.&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;p&gt;Bump-ups are configured per workload, at the &lt;a href=&#34;/docs/configure/cluster-defaults/&#34;&gt;cluster&lt;/a&gt;, &lt;a href=&#34;/docs/configure/annotate-namespaces/&#34;&gt;namespace&lt;/a&gt;, or &lt;a href=&#34;/docs/configure/annotate-workloads/&#34;&gt;workload&lt;/a&gt; level, and are disabled by default. Leaving them disabled does not stop StormForge reporting the underlying events.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Workload groups</title>
				<link>/docs/recommendations/workload-groups/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/recommendations/workload-groups/</guid>
				<description>&lt;p&gt;Workload groups let you aggregate usage metrics from related workloads, so StormForge generates appropriate recommendations even when a workload has temporarily low or split traffic.&lt;/p&gt;&#xA;&lt;h2 id=&#34;overview&#34;&gt;Overview&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#overview&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;StormForge generates recommendations based on observed resource usage. When workloads share a logical traffic pattern but run as separate deployments — blue/green pairs, canary variants, or ephemeral workloads — the inactive variants can report near-zero usage. This can lead to undersized recommendations for a variant that should align with a busier workload.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Node Agent configuration</title>
				<link>/docs/installation/node-agent-config/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/installation/node-agent-config/</guid>
				<description>&lt;p&gt;The Node Agent is an optional DaemonSet that runs on your GPU nodes and collects GPU metrics from them. It is disabled by default.&lt;/p&gt;&#xA;&lt;p&gt;This topic covers the Node Agent configuration parameters. For what the metrics are used for, see &lt;a href=&#34;/docs/recommendations/gpu/&#34;&gt;GPU optimization&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;h2 id=&#34;applying-these-settings&#34;&gt;Applying these settings&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#applying-these-settings&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;These are Helm values for the &lt;code&gt;stormforge&lt;/code&gt; chart. Add them to a YAML values file (for example, &lt;code&gt;values.yaml&lt;/code&gt;) and pass it to your Helm command.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Webhook configuration</title>
				<link>/docs/installation/webhook-config/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/installation/webhook-config/</guid>
				<description>&lt;p&gt;This topic covers the configuration parameters available for the StormForge webhook.&lt;/p&gt;&#xA;&lt;h2 id=&#34;applying-these-settings&#34;&gt;Applying these settings&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#applying-these-settings&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;These are Helm values for the &lt;code&gt;stormforge&lt;/code&gt; chart. Add them to a YAML values file (for example, &lt;code&gt;values.yaml&lt;/code&gt;) and pass it to your Helm command.&lt;/p&gt;&#xA;&lt;p&gt;At install time:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-shell&#34; data-lang=&#34;shell&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;helm install stormforge oci://registry.stormforge.io/library/stormforge &lt;span style=&#34;color:#ae81ff&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  --namespace stormforge-system &lt;span style=&#34;color:#ae81ff&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  -f values.yaml&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;To apply changes after installation:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-shell&#34; data-lang=&#34;shell&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;helm upgrade stormforge oci://registry.stormforge.io/library/stormforge &lt;span style=&#34;color:#ae81ff&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  --namespace stormforge-system &lt;span style=&#34;color:#ae81ff&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  --reset-then-reuse-values &lt;span style=&#34;color:#ae81ff&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  -f values.yaml&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;hr&gt;&#xA;&#xA;&lt;p&gt;&lt;strong&gt;Webhook parameters:&lt;/strong&gt;&lt;/p&gt;</description>
			</item>
			<item>
				<title>Cluster defaults templates</title>
				<link>/docs/installation/cluster-defaults-templates/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/installation/cluster-defaults-templates/</guid>
				<description>&lt;p&gt;The StormForge Agent reads cluster-level optimization defaults from a ConfigMap named &lt;code&gt;cluster-defaults&lt;/code&gt; in the &lt;code&gt;stormforge-system&lt;/code&gt; namespace. You can create and manage this ConfigMap using &lt;code&gt;kubectl&lt;/code&gt; or your GitOps tool. For full management details, see &lt;a href=&#34;/docs/configure/cluster-defaults/&#34;&gt;Configure optimization defaults for the cluster&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;h2 id=&#34;check-current-cluster-defaults&#34;&gt;Check current cluster defaults&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#check-current-cluster-defaults&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;To check whether any defaults are already set:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-shell&#34; data-lang=&#34;shell&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;kubectl describe configmap cluster-defaults -n stormforge-system&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;If you see &lt;code&gt;Error from server (NotFound): configmaps &amp;quot;cluster-defaults&amp;quot; not found&lt;/code&gt;, no cluster-level defaults are set.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Applier Kubernetes events</title>
				<link>/docs/reference/applier-events/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/reference/applier-events/</guid>
				<description>&lt;p&gt;The StormForge Applier emits standard Kubernetes Events. If your team uses &lt;code&gt;kubectl&lt;/code&gt;, Lens, k9s, or a cluster event exporter to track cluster activity, you can track Applier activity without any additional configuration.&lt;/p&gt;&#xA;&lt;div class=&#34;alert alert-info&#34; role=&#34;alert&#34;&gt;&#xA;&lt;p&gt;For push-based notifications when the Applier applies a recommendation, see &lt;a href=&#34;/docs/guides/applier-alerts/&#34;&gt;Configure applier alerts&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;/div&gt;&#xA;&lt;h2 id=&#34;view-events&#34;&gt;View events&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#view-events&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;Use &lt;code&gt;kubectl&lt;/code&gt; to query events on any Applier-managed workload:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-sh&#34; data-lang=&#34;sh&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#75715e&#34;&gt;# Events on a specific workload&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;kubectl get events -n &amp;lt;namespace&amp;gt; --field-selector involvedObject.name&lt;span style=&#34;color:#f92672&#34;&gt;=&lt;/span&gt;&amp;lt;workload-name&amp;gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#75715e&#34;&gt;# Filter by event reason (substitute any reason from the reference below)&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;kubectl get events -n &amp;lt;namespace&amp;gt; --field-selector reason&lt;span style=&#34;color:#f92672&#34;&gt;=&lt;/span&gt;RecommendationApplied&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#75715e&#34;&gt;# Watch for a specific reason in real time&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;kubectl get events -n &amp;lt;namespace&amp;gt; -w --field-selector reason&lt;span style=&#34;color:#f92672&#34;&gt;=&lt;/span&gt;RecommendationApplied&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Events also appear in &lt;code&gt;kubectl describe deployment &amp;lt;name&amp;gt;&lt;/code&gt; (or &lt;code&gt;statefulset&lt;/code&gt;, &lt;code&gt;daemonset&lt;/code&gt;, etc.) under the &lt;code&gt;Events:&lt;/code&gt; section.&lt;/p&gt;</description>
			</item>
			<item>
				<title>CPU and memory</title>
				<link>/docs/configure/settings/cpu-and-memory/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/configure/settings/cpu-and-memory/</guid>
				<description>&lt;p&gt;CPU and memory settings are applied at the container level. The configuration used can vary from container to container within a workload.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;CPU and memory settings:&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#opt-policy&#34;&gt;Optimization policy&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#lrr&#34;&gt;Limit-to-request ratio&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#requests-min-max&#34;&gt;Min and max for requests&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#limits-min-max&#34;&gt;Min and max for limits&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#patch-path&#34;&gt;Patch paths&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;For details about how to set these values using annotations, see one of these topics: &lt;a href=&#34;/docs/configure/cluster-defaults/&#34;&gt;Configure clusters&lt;/a&gt;, &lt;a href=&#34;/docs/configure/annotate-namespaces/&#34;&gt;Configure namespaces&lt;/a&gt;, or &lt;a href=&#34;/docs/configure/annotate-workloads/&#34;&gt;Configure workloads&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;h2 id=&#34;container-level-settings-syntax&#34;&gt;Container-level settings syntax&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#container-level-settings-syntax&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;When specifying configuration values for CPU and memory settings, you can specify a default value for all containers, one or more values for specific named containers, or a comma-separated list.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Generate recommendations on demand</title>
				<link>/docs/recommendations/generate/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/recommendations/generate/</guid>
				<description>&lt;p&gt;This feature is helpful when you are experimenting with settings and want to see the results as you go.&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;In the left navigation, click &lt;strong&gt;Workloads&lt;/strong&gt;, then find and click the name of the workload you want to work with.&lt;/li&gt;&#xA;&lt;li&gt;On the workload details page, in the &lt;strong&gt;Recommendation&lt;/strong&gt; section of the page header, click &lt;strong&gt;Regenerate&lt;/strong&gt;.&lt;/li&gt;&#xA;&lt;li&gt;Optional: To apply the recommendation, complete one of the following steps:&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Click &lt;strong&gt;Apply Now&lt;/strong&gt;.&lt;/li&gt;&#xA;&lt;li&gt;Apply the recommendation as patch: On the &lt;strong&gt;Patches&lt;/strong&gt; tab of the workload details page, download the patch and then copy and run the generated &lt;code&gt;kubectl apply&lt;/code&gt; command.&lt;/li&gt;&#xA;&lt;li&gt;Run &lt;code&gt;stormforge apply --name WORKLOAD_NAME&lt;/code&gt; from the command line, replacing WORKLOAD_NAME with the name of the workload. (Note: The optional StormForge CLI tool must be &lt;a href=&#34;/docs/installation/install-adv/#install-the-stormforge-cli-tool&#34;&gt;installed&lt;/a&gt;.)&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;div class=&#34;section-index related-topics&#34;&gt;&#xA;    &#xA;    &lt;hr class=&#34;panel-line&#34;&gt;&#xA;        &lt;h4&gt;Related topics&lt;/h4&gt;&#xA;        &lt;div class=&#34;entry&#34;&gt;&#xA;                &lt;h5&gt;&#xA;                    &#xA;                    Installation&lt;span class=&#34;related-topics-divider&#34;&gt;/&lt;/span&gt;&lt;a href=&#34;/docs/installation/install-adv/&#34;&gt;Advanced installation&lt;/a&gt;&#xA;                &lt;/h5&gt;&#xA;                &lt;p&gt;Installation behind a proxy server or from a private container registry&lt;/p&gt;&#xA;            &lt;/div&gt;&#xA;        &lt;div class=&#34;entry&#34;&gt;&#xA;                &lt;h5&gt;&#xA;                    &#xA;                    Recommendations&lt;span class=&#34;related-topics-divider&#34;&gt;/&lt;/span&gt;&lt;a href=&#34;/docs/recommendations/apply/&#34;&gt;Apply recommendations&lt;/a&gt;&#xA;                &lt;/h5&gt;&#xA;                &lt;p&gt;Apply recommendations using the method that suits your environment&lt;/p&gt;&#xA;            &lt;/div&gt;&#xA;        &lt;div class=&#34;entry&#34;&gt;&#xA;                &lt;h5&gt;&#xA;                    &#xA;                    Recommendations&lt;span class=&#34;related-topics-divider&#34;&gt;/&lt;/span&gt;&lt;a href=&#34;/docs/recommendations/view/&#34;&gt;View recommendations&lt;/a&gt;&#xA;                &lt;/h5&gt;&#xA;                &lt;p&gt;View recommendations on the Workload Details page or from the command line&lt;/p&gt;&#xA;            &lt;/div&gt;&#xA;        &lt;/div&gt;</description>
			</item>
			<item>
				<title>Install StormForge as an EKS add-on</title>
				<link>/docs/installation/install-eks-addon/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/installation/install-eks-addon/</guid>
				<description>&lt;p&gt;If you&amp;rsquo;re running an Amazon EKS cluster, you can install StormForge as an EKS add-on in one of two ways:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#eks-ui&#34;&gt;Using the EKS UI and StormForge UI&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#eks-cli&#34;&gt;Using the EKS CLI and StormForge UI&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;prerequisites&#34;&gt;Prerequisites&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#prerequisites&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;An Amazon EKS cluster&lt;/li&gt;&#xA;&lt;li&gt;A StormForge account — &lt;a href=&#34;https://stormforge.io/signup&#34;&gt;sign up for a free trial&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;eks-ui&#34;&gt;Install using the EKS UI and StormForge UI&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#eks-ui&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;h3 id=&#34;install-the-add-on&#34;&gt;Install the add-on&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#install-the-add-on&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Open two browser windows side by side.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;In one window, navigate to and log in to your Amazon EKS cluster.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;On the cluster page, add the &lt;strong&gt;Add-ons&lt;/strong&gt; tab, and then click &lt;strong&gt;Get more add-ons&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;On the &lt;strong&gt;Select add-ons&lt;/strong&gt; page, scroll to the &lt;strong&gt;AWS Marketplace add-ons&lt;/strong&gt; section.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;From the &lt;strong&gt;Any category&lt;/strong&gt; menu, select &lt;strong&gt;cost-management&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;On the StormForge add-on card, select the check box in the upper right (see below); then, click &lt;strong&gt;Next&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;/img/docs/ol-eks-install-costmg-card.png&#34;&gt;&lt;img src=&#34;/img/docs/ol-eks-install-costmg-card.png&#34; alt=&#34;EKS cost management card&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;On the &lt;strong&gt;Configure selected add-ons&lt;/strong&gt; settings page, expand the &lt;strong&gt;Optional configuration settings&lt;/strong&gt; section.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;In the &lt;strong&gt;Add-on configuration schema&lt;/strong&gt; section, you can customize your installation the same way you can customize a Helm install.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Copy the following placeholder text into the &lt;strong&gt;Configuration values&lt;/strong&gt; text area. In a later step, you&amp;rsquo;ll replace this text with the values generated on the StormForge Access Credentials page.&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-yaml&#34; data-lang=&#34;yaml&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#f92672&#34;&gt;authorization&lt;/span&gt;:&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  &lt;span style=&#34;color:#f92672&#34;&gt;issuer&lt;/span&gt;:&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  &lt;span style=&#34;color:#f92672&#34;&gt;clientID&lt;/span&gt;:&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  &lt;span style=&#34;color:#f92672&#34;&gt;clientSecret&lt;/span&gt;:&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#f92672&#34;&gt;standbyMode&lt;/span&gt;: &lt;span style=&#34;color:#66d9ef&#34;&gt;false&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/li&gt;&#xA;&lt;/ol&gt;</description>
			</item>
			<item>
				<title>Monitoring the health of StormForge</title>
				<link>/docs/guides/monitoring-health-optlive/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/guides/monitoring-health-optlive/</guid>
				<description>&lt;h2 id=&#34;health-and-status-metrics&#34;&gt;Health and status metrics&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#health-and-status-metrics&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;StormForge components expose health and status metrics for monitoring StormForge. Health and status metrics differ from the workload metrics StormForge needs to create request and limit recommendations. See the &lt;a href=&#34;/docs/reference/faq-security/#metrics&#34;&gt;Security FAQ&lt;/a&gt; for details on workload metrics.&lt;/p&gt;&#xA;&lt;p&gt;StormForge installs from a single &lt;code&gt;stormforge&lt;/code&gt; Helm chart and runs as separate components in your cluster. Three components deploy as their own Kubernetes Deployment:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;stormforge-cluster-agent&lt;/code&gt; — the cluster telemetry agent that processes workloads and generates recommendations&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;stormforge-forwarder&lt;/code&gt; — forwards cluster metrics to StormForge&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;stormforge-applier&lt;/code&gt; — applies recommendations to workloads&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;One optional component deploys as a DaemonSet:&lt;/p&gt;</description>
			</item>
			<item>
				<title>Install on Red Hat OpenShift Container Platform</title>
				<link>/docs/installation/install-openshift/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/installation/install-openshift/</guid>
				<description>&lt;p&gt;Red Hat OpenShift Container Platform is a Kubernetes solution for both cloud and on-premises with providers such as AWS, Google and Microsoft Azure. StormForge is compatible with OpenShift Container Platform versions 4.x and later.&lt;/p&gt;&#xA;&lt;h2 id=&#34;installation&#34;&gt;Installation&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#installation&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;To install StormForge on OpenShift, do one of the following:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;In the StormForge &lt;code&gt;values.yaml&lt;/code&gt; file, set &lt;code&gt;openshift: true&lt;/code&gt; as a top-level key-value pair, and then apply the file:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-shell&#34; data-lang=&#34;shell&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;kubectl apply -f values.yaml&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Include the &lt;code&gt;--set openshift=true&lt;/code&gt; argument when you run &lt;code&gt;helm install&lt;/code&gt;, as in this example:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Replace &lt;code&gt;CREDENTIAL_FILE&lt;/code&gt; with the file name that contains your access credential.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Replace &lt;code&gt;CLUSTER_NAME&lt;/code&gt; with the name of the cluster (lowercase, no underscore) you&amp;rsquo;re installing on.&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-shell&#34; data-lang=&#34;shell&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;helm install stormforge oci://registry.stormforge.io/library/stormforge &lt;span style=&#34;color:#ae81ff&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  --namespace stormforge-system &lt;span style=&#34;color:#ae81ff&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  --create-namespace &lt;span style=&#34;color:#ae81ff&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  --values CREDENTIAL_FILE &lt;span style=&#34;color:#ae81ff&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  --set clusterName&lt;span style=&#34;color:#f92672&#34;&gt;=&lt;/span&gt;CLUSTER_NAME &lt;span style=&#34;color:#ae81ff&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  --set openshift&lt;span style=&#34;color:#f92672&#34;&gt;=&lt;/span&gt;true&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Upgrade</title>
				<link>/docs/installation/upgrade/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/installation/upgrade/</guid>
				<description>&lt;ol&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;(Optional) Review the current Helm values:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-sh&#34; data-lang=&#34;sh&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;helm get values stormforge -n stormforge-system&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;To change any values, save the output to a &lt;code&gt;.yaml&lt;/code&gt; file and modify it as needed. When you upgrade, pass the adjusted file to Helm using the &lt;code&gt;-f&lt;/code&gt; flag.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Upgrade and reuse all current Helm values:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-sh&#34; data-lang=&#34;sh&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;helm upgrade stormforge oci://registry.stormforge.io/library/stormforge &lt;span style=&#34;color:#ae81ff&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  -n stormforge-system &lt;span style=&#34;color:#ae81ff&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  --reset-then-reuse-values&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;div class=&#34;section-index related-topics&#34;&gt;&#xA;    &#xA;    &lt;hr class=&#34;panel-line&#34;&gt;&#xA;        &lt;h4&gt;Related topics&lt;/h4&gt;&#xA;        &lt;div class=&#34;entry&#34;&gt;&#xA;                &lt;h5&gt;&#xA;                    &#xA;                    Installation&lt;span class=&#34;related-topics-divider&#34;&gt;/&lt;/span&gt;&lt;a href=&#34;/docs/installation/migration/&#34;&gt;Migrate v2 → v3&lt;/a&gt;&#xA;                &lt;/h5&gt;&#xA;                &lt;p&gt;Migrate from separate Agent and Applier Helm charts to a unified StormForge chart&lt;/p&gt;&#xA;            &lt;/div&gt;&#xA;        &lt;/div&gt;</description>
			</item>
			<item>
				<title>Configure applier alerts</title>
				<link>/docs/guides/applier-alerts/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/guides/applier-alerts/</guid>
				<description>&lt;p&gt;The StormForge Applier can send an HTTP webhook notification each time it successfully applies a recommendation to a workload. You can configure one or more endpoints to receive these alerts, with optional custom payload formatting and bearer token authentication. Use this to connect StormForge to your existing observability or incident management workflows.&lt;/p&gt;&#xA;&lt;h2 id=&#34;how-alerts-work&#34;&gt;How alerts work&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#how-alerts-work&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;When the Applier applies a patch, it sends an HTTP POST to each configured endpoint. The request includes the header &lt;code&gt;X-Event-Type: recommendation applied&lt;/code&gt;. The body contains either the full JSON recommendation object (default) or a custom payload that you can define using a Go template.&lt;/p&gt;</description>
			</item>
			<item>
				<title>HPA</title>
				<link>/docs/configure/settings/hpa/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/configure/settings/hpa/</guid>
				<description>&lt;p&gt;StormForge integrates with &lt;a href=&#34;https://kubernetes.io/docs/concepts/workloads/autoscaling/horizontal-pod-autoscale/&#34;&gt;Horizontal Pod Autoscalers&lt;/a&gt; (HPA) and can:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Generate vertical rightsizing recommendations for HPA-managed workloads&lt;/li&gt;&#xA;&lt;li&gt;Preserve HPA scaling behavior when adjusting resource requests&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;how-it-works&#34;&gt;How StormForge integrates with HPA&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#how-it-works&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;StormForge integrates with the HPA by adjusting HPA target utilization when Pod resource requests change.&lt;/p&gt;&#xA;&lt;p&gt;Because HPA scaling is based on a percentage of resource requests, changing requests without adjusting target utilization changes how a workload scales.&lt;/p&gt;&#xA;&lt;p&gt;StormForge balances vertical sizing changes with corresponding adjustments to HPA target utilization so the workload continues to scale at the same overall load level.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Security FAQ</title>
				<link>/docs/reference/faq-security/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/reference/faq-security/</guid>
				<description>&lt;p&gt;You asked:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#soc2-reports&#34;&gt;How does one access StormForge SOC 2 compliance reports?&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#how-is-stormforge-deployed&#34;&gt;How is StormForge deployed?&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#what-data-do-you-collect&#34;&gt;What data do you collect?&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#how-do-you-collect-data-and-where-is-it-stored&#34;&gt;How do you collect data and where is it stored?&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#how-long-is-data-stored-for&#34;&gt;How long is data stored for?&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#who-has-access-to-customer-data&#34;&gt;Who has access to customer data?&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#federated-sso&#34;&gt;Does StormForge support federated single sign-on?&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#which-stormforge-service-urls-must-be-on-the-organizations-allowlist&#34;&gt;Which StormForge service URLs must be on the organization&amp;rsquo;s allowlist?&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#metrics&#34;&gt;What metrics does StormForge collect?&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;soc2-reports&#34;&gt;How does one access StormForge SOC 2 compliance reports?&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#soc2-reports&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;StormForge is SOC 2 Type 2 compliant as determined by an audit completed by an accredited auditing firm. You can request access to the SOC 2 reports on the &lt;a href=&#34;https://www.cloudbolt.io/report/soc-2-compliance/&#34;&gt;SOC 2 Compliance Reports&lt;/a&gt; page.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Uninstall</title>
				<link>/docs/installation/uninstall/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/installation/uninstall/</guid>
				<description>&lt;p&gt;Uninstall StormForge when you want to stop optimizing workloads on a cluster or before you delete a cluster from StormForge:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-sh&#34; data-lang=&#34;sh&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;helm uninstall stormforge -n stormforge-system&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Uninstalling removes the StormForge components but leaves the StormForge CRDs — and any custom resources, such as optimization configurations — in place. This is expected: it ensures your optimization configuration survives a reinstall.&lt;/p&gt;</description>
			</item>
			<item>
				<title>View recommendations</title>
				<link>/docs/recommendations/view/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/recommendations/view/</guid>
				<description>&lt;p&gt;A recommendation includes the CPU and memory requests and limits values (and recommended HPA configuration, if an HPA is running) that the machine learning has determined to be optimal for each container in a workload.&lt;/p&gt;&#xA;&lt;p&gt;By default:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Recommendations are &lt;strong&gt;not applied automatically&lt;/strong&gt;, giving you the opportunity to review their projected impact on your workloads. You can configure StormForge to deploy recommendations automatically, as described later in this topic.&lt;/li&gt;&#xA;&lt;li&gt;Recommendations are applied as patches. You can choose to configure StormForge to use a mutating admission webhook to apply recommendations, as described later in this topic.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;viewing-the-overall-projected-impact-of-a-recommendation&#34;&gt;Viewing the overall projected impact of a recommendation&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#viewing-the-overall-projected-impact-of-a-recommendation&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;To understand how a recommendation will right-size a workload, review the workload details page header:&lt;/p&gt;</description>
			</item>
			<item>
				<title>Apply recommendations</title>
				<link>/docs/recommendations/apply/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/recommendations/apply/</guid>
				<description>&lt;p&gt;During a workload&amp;rsquo;s &lt;a href=&#34;/docs/configure/settings/apply-settings/#learning-period&#34;&gt;learning period&lt;/a&gt;, the preliminary recommendations generated by StormForge can be applied manually only.&lt;/p&gt;&#xA;&lt;p&gt;After the learning period, when you’re satisfied with how the generated recommendations can right-size your workloads, you can deploy them in any of the ways described below.&lt;/p&gt;&#xA;&lt;h2 id=&#34;choose-apply-method&#34;&gt;Choosing an apply method - patch or webhook?&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#choose-apply-method&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;By default StormForge applies recommendations as patches to a workload.&lt;/p&gt;&#xA;&lt;p&gt;You can choose to configure StormForge to apply recommendations directly to Pods via a mutating admission webhook. You might choose a webhook method if you use third-party tools to monitor for configuration drift or if you have many custom resources.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Migrate from v2 to v3</title>
				<link>/docs/installation/migration/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/installation/migration/</guid>
				<description>&lt;p&gt;With v3, the separate &lt;code&gt;stormforge-agent&lt;/code&gt; and &lt;code&gt;stormforge-applier&lt;/code&gt; Helm charts are combined into a single &lt;code&gt;stormforge&lt;/code&gt; chart.&lt;/p&gt;&#xA;&lt;h2 id=&#34;prerequisites&#34;&gt;Prerequisites&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#prerequisites&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;Before you begin, ensure you have:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;/docs/installation/install-adv/#set-up-the-stormforge-cli&#34;&gt;The StormForge CLI installed&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;Your current v2 values (see &lt;a href=&#34;#convert-values&#34;&gt;Convert your values&lt;/a&gt;)&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;clusterName&lt;/code&gt; and your API credentials (&lt;code&gt;authorization.clientID&lt;/code&gt; and &lt;code&gt;authorization.clientSecret&lt;/code&gt;)&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;webhook-considerations&#34;&gt;Webhook considerations&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#webhook-considerations&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;The v3 chart&amp;rsquo;s &lt;code&gt;MutatingWebhookConfiguration&lt;/code&gt; reuses the name of the v2 Applier webhook. This means:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Helm-managed installs&lt;/strong&gt;: If a v2 Applier is still installed when you run &lt;code&gt;helm install stormforge&lt;/code&gt;, Helm&amp;rsquo;s release-ownership check will refuse to install.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;GitOps users (ArgoCD, Flux, kubectl apply)&lt;/strong&gt;: There is no automatic conflict detection. You &lt;strong&gt;must&lt;/strong&gt; fully remove the v2 Applier before applying the v3 manifests. Failing to do so will result in two conflicting &lt;code&gt;MutatingWebhookConfiguration&lt;/code&gt; resources.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;crd-considerations&#34;&gt;CRD considerations&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#crd-considerations&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;When you uninstall the v2 Agent, the &lt;code&gt;optimize.stormforge.io&lt;/code&gt; CustomResourceDefinitions (CRDs) — and all associated custom resources, such as optimization configurations — remain on your cluster. This is expected, as &lt;code&gt;helm uninstall&lt;/code&gt; doesn&amp;rsquo;t remove CRDs. &lt;strong&gt;Don&amp;rsquo;t delete them manually.&lt;/strong&gt; Deleting a CRD removes every associated custom resource from the cluster.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Runtime</title>
				<link>/docs/configure/settings/runtime/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/configure/settings/runtime/</guid>
				<description>&lt;h2 id=&#34;java&#34;&gt;Java runtime&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#java&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;You can define how StormForge applies JVM max heap size recommendations to JVM containers.&lt;/p&gt;&#xA;&lt;p&gt;The Java max heap recommendation settings apply to workloads identified as JVM workloads that StormForge is able to collect JVM metrics for. For non-Java workloads, these settings will have no effect.&lt;/p&gt;&#xA;&lt;p&gt;StormForge by default assumes that Java applications use the &lt;code&gt;-XX:MaxRamPercentage&lt;/code&gt; heap size management mechanism, and that changing the container&amp;rsquo;s memory limit will therefore change the effective max heap size. StormForge will attempt to use this relationship to optimize heap size without changing any configuration for your app.&lt;/p&gt;</description>
			</item>
			<item>
				<title>How to use StormForge and Argo CD together</title>
				<link>/docs/guides/argo-cd/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/guides/argo-cd/</guid>
				<description>&lt;p&gt;How you configure &lt;a href=&#34;https://argo-cd.readthedocs.io/&#34;&gt;Argo CD&lt;/a&gt; depends on which StormForge apply method you use:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;&lt;a href=&#34;#webhook&#34;&gt;Webhook apply methods&lt;/a&gt; (recommended):&lt;/strong&gt; StormForge sets recommendations on Pods at admission time and doesn&amp;rsquo;t change the workload spec. Argo CD only needs to ignore StormForge&amp;rsquo;s changes to HPAs and ScaledObjects.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;&lt;a href=&#34;#patch&#34;&gt;Patch apply methods&lt;/a&gt;:&lt;/strong&gt; StormForge writes recommendations into the workload spec. Argo CD needs to ignore those changes and keep them when it syncs, which has some &lt;a href=&#34;#patch-known-issues&#34;&gt;known issues&lt;/a&gt;.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;webhook&#34;&gt;Webhook apply methods&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#webhook&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;The webhook apply methods are &lt;code&gt;WebhookImmediateRollout&lt;/code&gt;, &lt;code&gt;WebhookHybridRollout&lt;/code&gt;, and &lt;code&gt;WebhookDeferredRollout&lt;/code&gt;.&lt;/p&gt;</description>
			</item>
			<item>
				<title>How to use StormForge and Flux together</title>
				<link>/docs/guides/flux/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/guides/flux/</guid>
				<description>&lt;p&gt;StormForge and &lt;a href=&#34;https://fluxcd.io/&#34;&gt;Flux&lt;/a&gt; are fully compatible:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Flux-managed workloads:&lt;/strong&gt; Recommendations are injected into Pods at admission time when using a &lt;a href=&#34;/docs/installation/webhook-config/#webhook-enabled&#34;&gt;webhook-based apply method&lt;/a&gt;. This leaves Flux&amp;rsquo;s reconciliation of the parent workload resource undisturbed.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Workloads with an HPA:&lt;/strong&gt; StormForge writes directly to &lt;code&gt;spec.metrics&lt;/code&gt;. &lt;code&gt;driftDetection.ignore&lt;/code&gt; is required, otherwise Flux overwrites those changes on each reconciliation.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;configure-a-webhook-based-apply-method&#34;&gt;Configure a webhook-based apply method&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#configure-a-webhook-based-apply-method&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;Set the &lt;code&gt;live.stormforge.io/apply.method&lt;/code&gt; annotation to a webhook-based value:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-yaml&#34; data-lang=&#34;yaml&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#f92672&#34;&gt;live.stormforge.io/apply.method&lt;/span&gt;: &lt;span style=&#34;color:#ae81ff&#34;&gt;WebhookImmediateRollout&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;See &lt;a href=&#34;/docs/configure/settings/apply-settings/#apply-method&#34;&gt;Apply method&lt;/a&gt; for the full list of webhook rollout options and how to enable the webhook on the Applier.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Custom workload kinds</title>
				<link>/docs/recommendations/custom-workload-kinds/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/recommendations/custom-workload-kinds/</guid>
				<description>&lt;p&gt;StormForge optimizes Kubernetes workloads, and the Agent recognizes standard workload kinds by default — declare &lt;code&gt;workloadResourceKinds&lt;/code&gt; to tell StormForge about custom resources or operators.&lt;/p&gt;&#xA;&lt;h2 id=&#34;when-to-use&#34;&gt;When to use&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#when-to-use&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;StormForge recognizes the built-in Kubernetes workload kinds (&lt;code&gt;Deployment&lt;/code&gt;, &lt;code&gt;StatefulSet&lt;/code&gt;, &lt;code&gt;DaemonSet&lt;/code&gt;, &lt;code&gt;ReplicaSet&lt;/code&gt;) automatically, while the default-enabled &lt;code&gt;includeCommonAddOnResourceKinds&lt;/code&gt; flag adds support for common operators like Argo Rollouts, Prometheus operator, Dynatrace, and KEDA.&lt;/p&gt;&#xA;&lt;p&gt;Configure custom workload kinds if:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;You run a &lt;strong&gt;custom workload resource&lt;/strong&gt; that isn&amp;rsquo;t supported by default, such as the GitHub Actions Runner Controller (&lt;code&gt;AutoscalingRunnerSet&lt;/code&gt;) or the Spark operator (&lt;code&gt;SparkApplication&lt;/code&gt;).&lt;/li&gt;&#xA;&lt;li&gt;You run an &lt;strong&gt;operator that reconciles a standard workload&lt;/strong&gt; and reverts direct patches — StormForge must patch the operator&amp;rsquo;s custom resource instead.&lt;/li&gt;&#xA;&lt;li&gt;You run an &lt;strong&gt;in-house platform operator&lt;/strong&gt; that owns your workloads via &lt;code&gt;ownerReferences&lt;/code&gt; without managing their resource fields.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;minimal-configuration&#34;&gt;Minimal configuration&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#minimal-configuration&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;For a custom workload resource that owns its own pods, add this to your Helm values:&lt;/p&gt;</description>
			</item>
			<item>
				<title>Pod scheduling</title>
				<link>/docs/configure/settings/pod-scheduling/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/configure/settings/pod-scheduling/</guid>
				<description>&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#affinity-type&#34;&gt;Affinity type&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#affinity-weight&#34;&gt;Affinity weight&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#sched-opt-policy&#34;&gt;Scheduling optimization policy&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#patch-path&#34;&gt;Patch path&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#patch-format&#34;&gt;Patch format&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;sched-opt-policy&#34;&gt;Scheduling optimization policy&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#sched-opt-policy&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;Whether or not node affinity is included in recommendation patches depends on the optimization policy selected.&lt;/p&gt;&#xA;&lt;div class=&#34;table-scroll&#34;&gt;&#xA;&lt;div class=&#34;table-responsive&#34;&gt;&#xA;&lt;table&gt;&#xA;  &lt;thead&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;th&gt;Annotation&lt;/th&gt;&#xA;          &lt;th&gt;Default value&lt;/th&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/thead&gt;&#xA;  &lt;tbody&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;code&gt;live.stormforge.io/pod-scheduling.optimization-policy&lt;/code&gt;&lt;/td&gt;&#xA;          &lt;td&gt;&lt;code&gt;DoNotOptimize&lt;/code&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/tbody&gt;&#xA;&lt;/table&gt;&#xA;&lt;/div&gt;&#xA;&lt;/div&gt;&#xA;&lt;h3 id=&#34;sched-opt-policy-description&#34;&gt;Description&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#sched-opt-policy-description&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;p&gt;StormForge recommends an instance category for pod scheduling by default, but that recommendation will not be included in patches unless an optimization policy is configured.&lt;/p&gt;&#xA;&lt;p&gt;Instance category node affinity recommendations can be added to patches by setting the optimization policy to &lt;code&gt;InstanceCategories&lt;/code&gt;.&lt;/p&gt;</description>
			</item>
			<item>
				<title>StormForge Kustomize export</title>
				<link>/docs/guides/kustomize-export/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/guides/kustomize-export/</guid>
				<description>&lt;p&gt;For infrastructure workflows fully automated by a CI pipeline and Kustomize, an alternative option for deployment of recommended resource settings may be to incorporate StormForge’s recommendations into the CI pipeline.&lt;/p&gt;&#xA;&lt;p&gt;Because Kustomizations (&lt;code&gt;kustomization.yaml&lt;/code&gt; files) often serve as the entrypoint for application definitions in tools like Flux CD, tying into Kustomize is frequently the easiest way to automate resource settings if an organization wants or needs to do that during the CI/CD process, rather than managing these settings with a controller.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Import recommendation data into APM tools</title>
				<link>/docs/guides/apm_export/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/guides/apm_export/</guid>
				<description>&lt;p&gt;By creating a Prometheus scrape job, StormForge exports recommendation data as Prometheus metrics, which you can import into other application performance management (APM) tools.&lt;/p&gt;&#xA;&lt;p&gt;To define a scrape job to get recommendation data:&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Edit the &lt;code&gt;prometheus-server&lt;/code&gt; ConfigMap in the &lt;code&gt;prometheus&lt;/code&gt; namespace:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-sh&#34; data-lang=&#34;sh&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;kubectl edit configmap -n prometheus prometheus-server&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Add the following scrape job to the &lt;code&gt;scrape_configs:&lt;/code&gt; section of the ConfigMap.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Replace SF_CLIENT_ID with the clientID value in your cluster credential file.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Replace SF_CLIENT_SECRET with the clientSecret value in your cluster credential file.&lt;br&gt;&#xA;Alternatively, a Prometheus administrator can put the clientSecret in a file and leverage the &lt;code&gt;client_secret_file&lt;/code&gt; parameter and specify the absolute path (for example, &lt;code&gt;client_secret: /mnt/client_secret_file&lt;/code&gt;).&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-yaml&#34; data-lang=&#34;yaml&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;- &lt;span style=&#34;color:#f92672&#34;&gt;job_name&lt;/span&gt;: &lt;span style=&#34;color:#ae81ff&#34;&gt;stormforge-recommendations&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  &lt;span style=&#34;color:#f92672&#34;&gt;scrape_interval&lt;/span&gt;: &lt;span style=&#34;color:#ae81ff&#34;&gt;90s &lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  &lt;span style=&#34;color:#f92672&#34;&gt;scrape_timeout&lt;/span&gt;: &lt;span style=&#34;color:#ae81ff&#34;&gt;15s&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  &lt;span style=&#34;color:#f92672&#34;&gt;honor_labels&lt;/span&gt;: &lt;span style=&#34;color:#66d9ef&#34;&gt;true&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  &lt;span style=&#34;color:#f92672&#34;&gt;proxy_from_environment&lt;/span&gt;: &lt;span style=&#34;color:#66d9ef&#34;&gt;true&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  &lt;span style=&#34;color:#f92672&#34;&gt;scheme&lt;/span&gt;: &lt;span style=&#34;color:#ae81ff&#34;&gt;https&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  &lt;span style=&#34;color:#f92672&#34;&gt;oauth2&lt;/span&gt;:&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    &lt;span style=&#34;color:#f92672&#34;&gt;client_id&lt;/span&gt;: &lt;span style=&#34;color:#e6db74&#34;&gt;&amp;#39;SF_CLIENT_ID&amp;#39;&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    &lt;span style=&#34;color:#f92672&#34;&gt;client_secret&lt;/span&gt;: &lt;span style=&#34;color:#e6db74&#34;&gt;&amp;#39;SF_CLIENT_SECRET&amp;#39;&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    &lt;span style=&#34;color:#f92672&#34;&gt;token_url&lt;/span&gt;: &lt;span style=&#34;color:#e6db74&#34;&gt;&amp;#39;https://api.stormforge.io/oauth/token&amp;#39;&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    &lt;span style=&#34;color:#f92672&#34;&gt;endpoint_params&lt;/span&gt;:&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;        &lt;span style=&#34;color:#f92672&#34;&gt;audience&lt;/span&gt;: &lt;span style=&#34;color:#e6db74&#34;&gt;&amp;#39;https://api.stormforge.io/&amp;#39;&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  &lt;span style=&#34;color:#f92672&#34;&gt;metrics_path&lt;/span&gt;: &lt;span style=&#34;color:#ae81ff&#34;&gt;/v3/workload-metrics&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  &lt;span style=&#34;color:#f92672&#34;&gt;static_configs&lt;/span&gt;:&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  - &lt;span style=&#34;color:#f92672&#34;&gt;targets&lt;/span&gt;: [&lt;span style=&#34;color:#e6db74&#34;&gt;&amp;#34;api.stormforge.io&amp;#34;&lt;/span&gt;]&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ol&gt;</description>
			</item>
			<item>
				<title>Kubernetes cost allocation</title>
				<link>/docs/guides/kubernetes-cost-allocation/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/guides/kubernetes-cost-allocation/</guid>
				<description>&lt;p&gt;Our cost platform (CloudBolt Platform) reports what your Kubernetes clusters cost, broken down by namespace, workload, pod, and container. It builds that view from two sources:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Cloud billing data&lt;/strong&gt;: a FOCUS cost and usage export from AWS, Azure, or GCP, which provides the cost of your cluster infrastructure.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Cluster usage metrics&lt;/strong&gt;: the CPU, memory, and network metrics the StormForge Agent already collects, which show how that capacity was consumed.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;CloudBolt joins the two and attributes infrastructure cost down to the workload level, including idle capacity and overhead such as system pods.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Transparent proxy configuration</title>
				<link>/docs/guides/proxy-config/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/guides/proxy-config/</guid>
				<description>&lt;p&gt;If you use a transparent proxy, you need to configure StormForge to trust the proxy&amp;rsquo;s root certificate authority (CA). To do this, mount the proxy&amp;rsquo;s root CA certificate using a volume, then use &lt;code&gt;additionalEnvVars&lt;/code&gt; to configure StormForge to use the mounted bundle.&lt;/p&gt;&#xA;&lt;h2 id=&#34;prerequisites&#34;&gt;Prerequisites&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#prerequisites&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Helm version 3.14.0 or later (required for the &lt;code&gt;--reset-then-reuse&lt;/code&gt; parameter)&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;steps&#34;&gt;Steps&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#steps&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Copy the YAML below into a new file named, for example, &lt;code&gt;transparent-proxy-values.yaml&lt;/code&gt;. This example assumes the required root CA is available in a ConfigMap, but any &lt;code&gt;core/v1 Volumes&lt;/code&gt; type can be used (see the related link below).&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-yaml&#34; data-lang=&#34;yaml&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;---&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#75715e&#34;&gt;# Configures additional volumes that will be added to all pods&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#f92672&#34;&gt;additionalVolumes&lt;/span&gt;:&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;- &lt;span style=&#34;color:#f92672&#34;&gt;name&lt;/span&gt;: &lt;span style=&#34;color:#ae81ff&#34;&gt;corporate-root-ca&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  &lt;span style=&#34;color:#f92672&#34;&gt;configMap&lt;/span&gt;:&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    &lt;span style=&#34;color:#f92672&#34;&gt;name&lt;/span&gt;: &lt;span style=&#34;color:#ae81ff&#34;&gt;corporate-root-ca&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    &lt;span style=&#34;color:#f92672&#34;&gt;items&lt;/span&gt;:&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    - &lt;span style=&#34;color:#f92672&#34;&gt;key&lt;/span&gt;: &lt;span style=&#34;color:#ae81ff&#34;&gt;ca.crt&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;      &lt;span style=&#34;color:#f92672&#34;&gt;path&lt;/span&gt;: &lt;span style=&#34;color:#ae81ff&#34;&gt;ca.crt&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#75715e&#34;&gt;# Configures additional volume mounts that will be added to all containers&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#f92672&#34;&gt;additionalVolumeMounts&lt;/span&gt;:&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;- &lt;span style=&#34;color:#f92672&#34;&gt;name&lt;/span&gt;: &#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  &lt;span style=&#34;color:#f92672&#34;&gt;mountPath&lt;/span&gt;: &lt;span style=&#34;color:#ae81ff&#34;&gt;/etc/ssl/certs&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#75715e&#34;&gt;# Configures additional environment variables that will be added to all containers&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#f92672&#34;&gt;additionalEnvVars&lt;/span&gt;: &#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;- &lt;span style=&#34;color:#f92672&#34;&gt;name&lt;/span&gt;: &lt;span style=&#34;color:#ae81ff&#34;&gt;SSL_CERT_FILE &lt;/span&gt; &lt;span style=&#34;color:#75715e&#34;&gt;# or SSL_CERT_DIR. Configures StormForge apps to use the mounted bundle.&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  &lt;span style=&#34;color:#f92672&#34;&gt;value&lt;/span&gt;: &lt;span style=&#34;color:#ae81ff&#34;&gt;/etc/ssl/certs/ca.crt&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Run &lt;code&gt;helm upgrade&lt;/code&gt; to apply the new settings:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-sh&#34; data-lang=&#34;sh&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;helm upgrade stormforge oci://registry.stormforge.io/library/stormforge &lt;span style=&#34;color:#ae81ff&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    -n stormforge-system &lt;span style=&#34;color:#ae81ff&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    --reset-then-reuse-values &lt;span style=&#34;color:#ae81ff&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    -f transparent-proxy-values.yaml&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/li&gt;&#xA;&lt;/ol&gt;</description>
			</item>
			<item>
				<title>Manage secrets with a third-party credential manager</title>
				<link>/docs/guides/manage-secrets/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/guides/manage-secrets/</guid>
				<description>&lt;p&gt;By default, StormForge uses Helm to create and update its credentials Secret. However, if you would like to use a third-party credential manager (for example, to rotate secrets), you can choose to disable Helm management of the credentials secret.&lt;/p&gt;&#xA;&lt;p&gt;When Helm management of the credentials secret is disabled, you must:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Create the &lt;code&gt;stormforge-system&lt;/code&gt; namespace before you install the agent.&lt;/li&gt;&#xA;&lt;li&gt;Create the &lt;code&gt;stormforge-auth&lt;/code&gt; secret, and populate it with the required credentials, before you install the agent.&lt;/li&gt;&#xA;&lt;li&gt;Maintain the &lt;code&gt;stormforge-auth&lt;/code&gt; secret yourself, manually or with a third-party credential manager.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;div class=&#34;alert alert-info&#34; role=&#34;alert&#34;&gt;&lt;div class=&#34;h4 alert-heading&#34; role=&#34;heading&#34;&gt;Without a credential manager&lt;/div&gt;&#xA;&lt;p&gt;If you are &lt;strong&gt;not&lt;/strong&gt; using a third-party credential management tool, you do &lt;strong&gt;not&lt;/strong&gt; need to follow the steps in this guide. Instead, follow the steps in the &lt;a href=&#34;/docs/installation/install/&#34;&gt;Install&lt;/a&gt; topic. You still have to create an access credential (as described in the Install topic), but StormForge will create and manage the secret for you.&lt;/p&gt;&#xA;&lt;/div&gt;</description>
			</item>
			<item>
				<title>Reference</title>
				<link>/docs/stormforge-cli/reference/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/stormforge-cli/reference/</guid>
				<description>&lt;h2 id=&#34;stormforge&#34;&gt;stormforge&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#stormforge&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;StormForge Command Line Interface&lt;/p&gt;&#xA;&lt;h3 id=&#34;synopsis&#34;&gt;Synopsis&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#synopsis&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;p&gt;Automated Kubernetes Workload Rightsizing.&lt;/p&gt;&#xA;&lt;p&gt;Find more information at: &lt;a href=&#34;https://docs.stormforge.io/&#34;&gt;https://docs.stormforge.io/&lt;/a&gt;&lt;/p&gt;&#xA;&lt;h3 id=&#34;options&#34;&gt;Options&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#options&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;      --sfconfig file   configuration file to use&#xA;  -h, --help            help for stormforge&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;h3 id=&#34;see-also&#34;&gt;See also&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#see-also&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#stormforge-apply&#34;&gt;stormforge apply&lt;/a&gt;&#x9; - Apply one or more recommendations&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#stormforge-auth&#34;&gt;stormforge auth&lt;/a&gt;&#x9; - Manage non-user authorizations&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#stormforge-check&#34;&gt;stormforge check&lt;/a&gt;&#x9; - Validate StormForge components&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#stormforge-completion&#34;&gt;stormforge completion&lt;/a&gt;&#x9; - Generate the autocompletion script for the specified shell&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#stormforge-config&#34;&gt;stormforge config&lt;/a&gt;&#x9; - Show the CLI configuration&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#stormforge-create&#34;&gt;stormforge create&lt;/a&gt;&#x9; - Create a resource&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#stormforge-delete&#34;&gt;stormforge delete&lt;/a&gt;&#x9; - Delete a resource&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#stormforge-describe&#34;&gt;stormforge describe&lt;/a&gt;&#x9; - Describe a resource&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#stormforge-edit&#34;&gt;stormforge edit&lt;/a&gt;&#x9; - Edit a resource&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#stormforge-get&#34;&gt;stormforge get&lt;/a&gt;&#x9; - Fetch resources&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#stormforge-login&#34;&gt;stormforge login&lt;/a&gt;&#x9; - Authorize the CLI&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#stormforge-logout&#34;&gt;stormforge logout&lt;/a&gt;&#x9; - Revoke the CLI authorization&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#stormforge-manage&#34;&gt;stormforge manage&lt;/a&gt;&#x9; - Manage a resource&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#stormforge-mcp&#34;&gt;stormforge mcp&lt;/a&gt;&#x9; - Run an MCP server&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#stormforge-patch&#34;&gt;stormforge patch&lt;/a&gt;&#x9; - Deploy patches to a cluster or source files&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#stormforge-ping&#34;&gt;stormforge ping&lt;/a&gt;&#x9; - Connect to the StormForge server (also see &amp;lsquo;check connect&amp;rsquo;)&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#stormforge-version&#34;&gt;stormforge version&lt;/a&gt;&#x9; - Show the version information&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#stormforge-view&#34;&gt;stormforge view&lt;/a&gt;&#x9; - View pages of impact data&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;stormforge-apply&#34;&gt;stormforge apply&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#stormforge-apply&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;Apply one or more recommendations&lt;/p&gt;</description>
			</item>
			<item>
				<title>Subscribe through AWS Marketplace</title>
				<link>/docs/guides/aws_marketplace/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/guides/aws_marketplace/</guid>
				<description>&lt;p&gt;With pay-as-you-go billing, you can subscribe to StormForge and get billed through your &lt;a href=&#34;https://aws.amazon.com/&#34;&gt;AWS account&lt;/a&gt;.&#xA;Billing is based on an hourly rate, per the number of requested CPU cores for each cluster connected to your StormForge account. There is no upfront or minimum cost.&lt;/p&gt;&#xA;&lt;p&gt;See the &lt;a href=&#34;https://docs.aws.amazon.com/marketplace/latest/buyerguide/saas-subscriptions.html&#34;&gt;AWS Marketplace - Buyers Guide&lt;/a&gt;&#xA;for details on the AWS Marketplace and the &lt;a href=&#34;https://aws.amazon.com/marketplace/pp/prodview-pcp2mkraouwbk?trk=8d276e92-b310-40ce-908f-23a198ca7ffc&amp;amp;sc_channel=el&amp;amp;source=stormforge&#34;&gt;StormForge product page&lt;/a&gt; for StormForge pricing.&lt;/p&gt;&#xA;&lt;h2 id=&#34;subscribing-to-stormforge&#34;&gt;Subscribing to StormForge&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#subscribing-to-stormforge&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Navigate to the &lt;a href=&#34;https://aws.amazon.com/marketplace/pp/prodview-pcp2mkraouwbk?trk=8d276e92-b310-40ce-908f-23a198ca7ffc&amp;amp;sc_channel=el&amp;amp;source=stormforge&#34;&gt;StormForge product page&lt;/a&gt; in the AWS Marketplace.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Click &lt;strong&gt;View purchase options&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Review the terms and pricing; then, click &lt;strong&gt;Subscribe&lt;/strong&gt;.&lt;/p&gt;&#xA; &lt;div class=&#34;alert alert-info&#34; role=&#34;alert&#34;&gt;&lt;div class=&#34;h4 alert-heading&#34; role=&#34;heading&#34;&gt;Billing an existing StormForge account&lt;/div&gt;&#xA;&lt;p&gt;If you already have a StormForge account that does &lt;strong&gt;not&lt;/strong&gt; have pay-as-you-go billing, your last step is to  contact &lt;a href=&#34;https://www.cloudbolt.io/company/contact-us/&#34;&gt;StormForge Support&lt;/a&gt; and provide your AWS account ID. StormForge Support will convert your existing account to a subscription.&lt;/p&gt;&#xA; &lt;/div&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Click the &lt;strong&gt;Set up your account&lt;/strong&gt; link, which takes you to the StormForge sign up page.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Sign up for a new StormForge account by providing a username and password.&#xA;At this time, social logins (social SSO) are not supported when creating StormForge subscriptions.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Confirm your email address via the link sent to you in the welcome email.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;After logging in, confirm that the account menu shows &lt;em&gt;This account is billed through the AWS Marketplace&lt;/em&gt;:&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;/img/docs/ol-billed-through-aws-marketplace.png&#34; alt=&#34;Image showing the AWS Account menu with text indicating &amp;ldquo;This account is billed through the AWS Marketplace&amp;rdquo;&#34;&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Continue with the &lt;a href=&#34;/docs/installation/install/#install-stormforge&#34;&gt;StormForge installation&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ol&gt;</description>
			</item>
			<item>
				<title>Version 3.5.1</title>
				<link>/docs/releases/stormforge/v3.5.1/</link>
				<pubDate>Mon, 09 Nov 2026 19:13:56 +0000</pubDate>
				<guid>/docs/releases/stormforge/v3.5.1/</guid>
				<description>&lt;div class=&#34;alert alert-warning&#34; role=&#34;alert&#34;&gt;&lt;div class=&#34;h4 alert-heading&#34; role=&#34;heading&#34;&gt;Breaking change&lt;/div&gt;&#xA;&lt;p&gt;If you use your own webhook certificate (&lt;code&gt;webhook.tlsSecretName&lt;/code&gt;) and manage the CRDs yourself (&lt;code&gt;crds.enabled=false&lt;/code&gt;), the webhook configurations now need a CA. Before upgrading, set &lt;code&gt;webhook.caBundle&lt;/code&gt; or add cert-manager injection annotations. Otherwise, &lt;code&gt;helm upgrade&lt;/code&gt; fails. See &lt;a href=&#34;/docs/installation/webhook-config/#tls&#34;&gt;TLS configuration&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;/div&gt;&#xA;&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;&lt;code&gt;terminalOwner&lt;/code&gt; role for workload resource kinds&lt;/strong&gt;: Mark an owner kind in &lt;code&gt;workloadResourceKinds&lt;/code&gt; as &lt;code&gt;terminalOwner&lt;/code&gt; to have StormForge patch that kind and ignore any owners above it. See &lt;a href=&#34;/docs/recommendations/custom-workload-kinds/#roles&#34;&gt;Roles&lt;/a&gt;.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Argo CD support&lt;/strong&gt;: The common add-on kinds (&lt;code&gt;includeCommonAddOnResourceKinds&lt;/code&gt;, enabled by default) now include Argo CD, so StormForge applies recommendations for Argo CD components through their &lt;code&gt;ArgoCD&lt;/code&gt; resource, including on OpenShift GitOps.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;cert-manager CA injection for CRDs&lt;/strong&gt;: If you use your own webhook certificate, the new &lt;code&gt;crds.annotations&lt;/code&gt; value lets cert-manager inject the CA into the CRDs, instead of supplying a static &lt;code&gt;webhook.caBundle&lt;/code&gt;. Also annotate the webhook configurations through &lt;code&gt;webhook.handlers.*.webhookAnnotations&lt;/code&gt;.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Stricter CA checks for your own webhook certificate&lt;/strong&gt;: When &lt;code&gt;webhook.tlsSecretName&lt;/code&gt; is set, each webhook configuration needs a CA from &lt;code&gt;webhook.caBundle&lt;/code&gt; or a cert-manager injection annotation. Previously, the chart checked only the CRDs, so the webhooks could install without a CA and be skipped silently. Installs missing a CA now fail at &lt;code&gt;helm install&lt;/code&gt; or &lt;code&gt;helm upgrade&lt;/code&gt; with an error that names the missing value.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Mirror mode uses &lt;code&gt;spec.workloadGroup.mirror&lt;/code&gt;&lt;/strong&gt;: Set WorkloadOptimizer mirror mode with &lt;code&gt;spec.workloadGroup.mirror&lt;/code&gt;. Mirrored workloads still ignore the target&amp;rsquo;s own metrics, and now also match the group&amp;rsquo;s scaling point, for example, HPA target utilization. This includes workloads that set &lt;code&gt;excludeTarget&lt;/code&gt;.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Node label limits on &lt;code&gt;sf_node_labels&lt;/code&gt;&lt;/strong&gt;: On heavily labeled nodes, the Agent now drops lower-priority labels so the series stays within Amazon Managed Prometheus per-series limits. Cloud and topology labels are kept first, followed by your own labels without a domain prefix, such as &lt;code&gt;env&lt;/code&gt; or &lt;code&gt;team&lt;/code&gt;. A new &lt;code&gt;omitted_labels&lt;/code&gt; label shows how many were dropped.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Full label selector syntax in OptimizationConfiguration v2&lt;/strong&gt;: v2 selectors now accept the full Kubernetes label selector syntax, including &lt;code&gt;!=&lt;/code&gt;. The validating webhook no longer rejects v2 selectors that v1 can&amp;rsquo;t represent. See &lt;a href=&#34;/docs/configure/optimization-configurations/#match-workloads&#34;&gt;Match workloads&lt;/a&gt;.&lt;/li&gt;&#xA;&lt;li&gt;Dependency updates&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;deprecated&#34;&gt;Deprecated&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#deprecated&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;&lt;code&gt;spec.workloadGroup.excludeTarget&lt;/code&gt;&lt;/strong&gt;: Use &lt;code&gt;spec.workloadGroup.mirror&lt;/code&gt; instead. &lt;code&gt;excludeTarget&lt;/code&gt; still works, but only when &lt;code&gt;mirror&lt;/code&gt; is unset.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Webhook blocked by default-deny network policies&lt;/strong&gt;: With &lt;code&gt;networkPolicies.create&lt;/code&gt; enabled, the chart did not let the Kubernetes API server reach the webhook. On clusters with a default-deny ingress policy, pods were admitted without their recommendations. The chart now allows that traffic on port 9443.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Missed CPU-saturated pods&lt;/strong&gt;: Detection of CPU-saturated pods on nodes under CPU pressure no longer misses pods or reports inaccurate readings after a container restarts. See &lt;a href=&#34;/docs/configure/settings/reliability/#cpu-pressure&#34;&gt;CPU pressure response&lt;/a&gt;.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>October 2026</title>
				<link>/docs/releases/whats-new/2026-10/</link>
				<pubDate>Sat, 31 Oct 2026 00:00:00 +0000</pubDate>
				<guid>/docs/releases/whats-new/2026-10/</guid>
				<description>&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;CPU pressure response&lt;/strong&gt;&lt;br&gt;&#xA;StormForge now detects nodes under sustained CPU pressure and identifies the workloads using more CPU than they request. You can configure a temporary CPU bump-up for those workloads, the same way you configure memory bump-ups after OOM events. Requires StormForge Agent 3.3.0. Bump-ups are disabled by default. See &lt;a href=&#34;/docs/configure/settings/reliability/#cpu-pressure&#34;&gt;CPU pressure response&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;New &lt;code&gt;enabled&lt;/code&gt; setting for OOM bump-ups&lt;/strong&gt;&lt;br&gt;&#xA;Memory bump-ups after OOM events now have an &lt;code&gt;enabled&lt;/code&gt; setting. Set it to &lt;code&gt;&amp;quot;True&amp;quot;&lt;/code&gt; to turn on bump-ups with default values. Existing OOM configurations keep working: if &lt;code&gt;enabled&lt;/code&gt; is unset but &lt;code&gt;percent&lt;/code&gt; or &lt;code&gt;min&lt;/code&gt; is set, bump-ups still apply using only the values you set. See &lt;a href=&#34;/docs/configure/settings/reliability/#oom&#34;&gt;Out-of-memory events response&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Hosted MCP server&lt;/strong&gt;&lt;br&gt;&#xA;Connect Claude, ChatGPT, Codex, and VS Code to StormForge through the hosted MCP server at &lt;code&gt;https://api.stormforge.io/mcp&lt;/code&gt;. You sign in with your StormForge account, with no API keys to create, and the server is read-only by default. See &lt;a href=&#34;/docs/guides/mcp-server/&#34;&gt;Connect AI agents to StormForge with MCP&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Recommendations respect namespace LimitRanges&lt;/strong&gt;&lt;br&gt;&#xA;StormForge checks recommendations against the LimitRanges in a workload&amp;rsquo;s namespace. A recommendation that a LimitRange would reject is marked infeasible instead of being deployed, and its status names the LimitRange and the value that violates it. Requires StormForge Agent 3.3.1.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Filter clusters and workloads by cluster label&lt;/strong&gt;&lt;br&gt;&#xA;The Clusters and Workloads lists have a cluster label filter next to the search box, and a cluster&amp;rsquo;s Config tab shows its labels. Set labels with &lt;a href=&#34;/docs/installation/cluster-agent-config/#cluster-labels&#34;&gt;&lt;code&gt;clusterLabels&lt;/code&gt;&lt;/a&gt; when you install the Agent. From StormForge CLI 6.2.10, filter &lt;code&gt;stormforge view workloads&lt;/code&gt; and &lt;code&gt;stormforge view namespaces&lt;/code&gt; by cluster label with &lt;code&gt;--cluster-selector&lt;/code&gt;.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;OptimizationConfiguration v2, and v1 deprecated&lt;/strong&gt;&lt;br&gt;&#xA;StormForge Agent 3.5.0 adds a v2 schema for &lt;code&gt;OptimizationConfiguration&lt;/code&gt; and &lt;code&gt;ClusterOptimizationConfiguration&lt;/code&gt; that groups workload matching into a single &lt;code&gt;match&lt;/code&gt; object. v1 is deprecated, so migrate your manifests to v2. The CRDs now convert between versions through the StormForge webhook, which must stay enabled. See the &lt;a href=&#34;/docs/releases/stormforge/v3.5.0/&#34;&gt;Version 3.5.0&lt;/a&gt; release notes.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 3.5.0</title>
				<link>/docs/releases/stormforge/v3.5.0/</link>
				<pubDate>Wed, 28 Oct 2026 17:58:25 +0000</pubDate>
				<guid>/docs/releases/stormforge/v3.5.0/</guid>
				<description>&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;&lt;code&gt;optimize.stormforge.io/v2&lt;/code&gt; OptimizationConfiguration CRDs&lt;/strong&gt;: &lt;code&gt;OptimizationConfiguration&lt;/code&gt; and &lt;code&gt;ClusterOptimizationConfiguration&lt;/code&gt; now have a v2 schema and storage version. Workload matching moves from the flat &lt;code&gt;selector&lt;/code&gt;, &lt;code&gt;namespaceSelector&lt;/code&gt;, and &lt;code&gt;matchConditions&lt;/code&gt; fields into a single &lt;code&gt;match&lt;/code&gt; object that can be set per resource or rule. Selectors are now label-selector strings, for example &lt;code&gt;app=web&lt;/code&gt;. A workload matches when:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;It matches every criterion that is set: &lt;code&gt;objectSelector&lt;/code&gt;, &lt;code&gt;expression&lt;/code&gt; (CEL), and &lt;code&gt;namespaceSelector&lt;/code&gt; (&lt;code&gt;ClusterOptimizationConfiguration&lt;/code&gt; only).&lt;/li&gt;&#xA;&lt;li&gt;It matches at least one term in &lt;code&gt;anyOf&lt;/code&gt;, if set.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;See &lt;a href=&#34;/docs/configure/optimization-configurations/#match-workloads&#34;&gt;Match workloads&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;v2 validation&lt;/strong&gt;: The validating webhook now covers v2, rejecting v2 selectors that cannot be represented in v1.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.28.8-agent</title>
				<link>/docs/releases/stormforge/previous/v2.28.8-agent/</link>
				<pubDate>Wed, 28 Oct 2026 17:22:55 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.28.8-agent/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Improved metrics collection efficiency&lt;/li&gt;&#xA;&lt;li&gt;Dependency updates&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.15.5-applier</title>
				<link>/docs/releases/stormforge/previous/v2.15.5-applier/</link>
				<pubDate>Mon, 26 Oct 2026 19:37:34 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.15.5-applier/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependency updates&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Dependency updates&lt;/strong&gt;: Updated dependencies to address &lt;a href=&#34;https://nvd.nist.gov/vuln/detail/cve-2026-113470&#34;&gt;CVE-2026-113470&lt;/a&gt;.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 6.2.10</title>
				<link>/docs/releases/stormforge-cli/v6.2.10/</link>
				<pubDate>Mon, 26 Oct 2026 15:59:54 +0000</pubDate>
				<guid>/docs/releases/stormforge-cli/v6.2.10/</guid>
				<description>&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The &lt;code&gt;view&lt;/code&gt; command can filter by cluster labels&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Improved error messages&lt;/li&gt;&#xA;&lt;li&gt;The &lt;code&gt;edit --config&lt;/code&gt; flag has been renamed to &lt;code&gt;edit --managed&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;Dependency updates&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Homebrew installations no longer use deprecated stanzas&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 3.4.0</title>
				<link>/docs/releases/stormforge/v3.4.0/</link>
				<pubDate>Thu, 22 Oct 2026 19:58:44 +0000</pubDate>
				<guid>/docs/releases/stormforge/v3.4.0/</guid>
				<description>&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Webhook component&lt;/strong&gt;: The webhook component now runs as a stand-alone Deployment rather than in the Applier. It serves both pod admission mutation (container resource recommendations) and config/Custom Resource Definition (CRD) validation.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;CRD validation&lt;/strong&gt;: StormForge now runs a validating admission webhook for ClusterOptimizationConfiguration and OptimizationConfiguration CRDs, to help catch mistakes in setting names or values.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Pod mutation outcome metrics&lt;/strong&gt;: Each pod admission mutation outcome is now recorded in the &lt;code&gt;sf_admission_pod_mutations_total&lt;/code&gt; metric, and mutation failures have additional logging.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Network cost allocation&lt;/strong&gt;: The Agent now reports whether each pod uses the host network, to improve the accuracy of network cost allocation.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Faster node sync&lt;/strong&gt;: The Agent syncs nodes through a new incremental node API, which speeds up startup on large clusters.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Stale recommendation URLs&lt;/strong&gt;: A pod whose &lt;code&gt;recommendation-url&lt;/code&gt; annotation points to a deleted recommendation is now counted as skipped, not failed.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Dependency updates&lt;/strong&gt;: Updated dependencies to address &lt;a href=&#34;https://nvd.nist.gov/vuln/detail/cve-2026-113470&#34;&gt;CVE-2026-113470&lt;/a&gt;.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.28.7-agent</title>
				<link>/docs/releases/stormforge/previous/v2.28.7-agent/</link>
				<pubDate>Thu, 22 Oct 2026 19:12:10 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.28.7-agent/</guid>
				<description>&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Node provider ID updates&lt;/strong&gt;: The Agent now detects node updates that change only &lt;code&gt;spec.providerID&lt;/code&gt;, which happens when the cloud controller sets the provider ID after the Agent first sees the node. The Agent refreshes &lt;code&gt;sf_node_labels&lt;/code&gt; and updates the cluster record in StormForge with the new provider ID instead of keeping an empty or outdated one.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;CPU pressure recommendations&lt;/strong&gt;: When &lt;code&gt;nodeCPUPressureDetection&lt;/code&gt; is enabled, recommendations created by the node CPU pressure analyzer now use the &lt;code&gt;CPUPressureDetected&lt;/code&gt; reason. They also include a message that names the node and the number of containers in the workload that exceeded their CPU requests.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Dependency updates&lt;/strong&gt;: Updated dependencies to address &lt;a href=&#34;https://nvd.nist.gov/vuln/detail/cve-2026-113470&#34;&gt;CVE-2026-113470&lt;/a&gt;.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.15.4-applier</title>
				<link>/docs/releases/stormforge/previous/v2.15.4-applier/</link>
				<pubDate>Thu, 22 Oct 2026 19:10:23 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.15.4-applier/</guid>
				<description>&lt;h3 id=&#34;deprecated&#34;&gt;Deprecated&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#deprecated&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;v2 Applier in maintenance mode&lt;/strong&gt;: The v2 Applier receives only security fixes going forward. To get new features, move to the unified &lt;code&gt;stormforge&lt;/code&gt; Helm chart; see &lt;a href=&#34;https://docs.stormforge.io/docs/installation/migration/&#34;&gt;Migrate from v2 to v3&lt;/a&gt;.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Kubernetes libraries updated&lt;/strong&gt;: Upgraded the Kubernetes client libraries to v0.37.1 and controller-runtime to v0.25.2.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Applier events missing when the edit role is disabled&lt;/strong&gt;: The Helm chart&amp;rsquo;s ClusterRole now allows the Applier to &lt;code&gt;create&lt;/code&gt; and &lt;code&gt;patch&lt;/code&gt; events in the core and &lt;code&gt;events.k8s.io&lt;/code&gt; API groups. Previously, the Applier could only read events, so installs with &lt;code&gt;rbac.useEditRole=false&lt;/code&gt; lost every Applier event (&lt;code&gt;RecommendationApplied&lt;/code&gt;, &lt;code&gt;InPlaceResizeSucceeded&lt;/code&gt;, &lt;code&gt;WorkloadResourcesChanged&lt;/code&gt;, and the drift and rollback events), logging only a &amp;ldquo;Server rejected event&amp;rdquo; message.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 3.3.1</title>
				<link>/docs/releases/stormforge/v3.3.1/</link>
				<pubDate>Fri, 09 Oct 2026 15:24:59 +0000</pubDate>
				<guid>/docs/releases/stormforge/v3.3.1/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Dependency updates&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;LimitRange violations&lt;/strong&gt;: The Agent now detects configured LimitRanges, so recommendations that violate them are not deployed.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Go 1.27.2&lt;/strong&gt;: Updated to Go 1.27.2, which includes security fixes to the &lt;code&gt;crypto/tls&lt;/code&gt; and &lt;code&gt;net/http&lt;/code&gt; packages.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 3.3.0</title>
				<link>/docs/releases/stormforge/v3.3.0/</link>
				<pubDate>Thu, 01 Oct 2026 18:24:43 +0000</pubDate>
				<guid>/docs/releases/stormforge/v3.3.0/</guid>
				<description>&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Node CPU pressure detection&lt;/strong&gt;: The Agent detects Kubernetes nodes under sustained CPU pressure and identifies the workloads responsible. It reads each node&amp;rsquo;s Pressure Stall Information (PSI) from cAdvisor. When a node&amp;rsquo;s CPU pressure exceeds the detection threshold, the Agent finds the containers on that node using more CPU than they request, maps them to their workloads, and creates a recommendation with the &lt;code&gt;CPUPressureDetected&lt;/code&gt; reason. Each recommendation lists the node, pod, and container, and how far CPU usage exceeded the request. Detection is always on. See &lt;a href=&#34;/docs/configure/settings/reliability/#cpu-pressure&#34;&gt;CPU pressure response&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;The Agent reports these metrics for CPU pressure detection:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;sf_container_cpu_pressure_waiting_seconds_total&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;sf_container_cpu_pressure_stalled_seconds_total&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;sf_container_cpu_pressure_waiting_rate&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;sf_container_cpu_pressure_stalled_rate&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;sf_workload_event_last_timestamp_seconds&lt;/code&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>September 2026</title>
				<link>/docs/releases/whats-new/2026-09/</link>
				<pubDate>Wed, 30 Sep 2026 00:00:00 +0000</pubDate>
				<guid>/docs/releases/whats-new/2026-09/</guid>
				<description>&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;New Summary tab on the workload details page&lt;/strong&gt;&lt;br&gt;&#xA;The Summary tab replaces the Impact tab on the workload details page. It shows the workload&amp;rsquo;s attributes and status messages, a table of current and recommended requests and cost, with the impact of each change, and CPU and memory usage charts for a single pod or the whole workload.&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;/img/docs/whats-new-2026-09-summary-tab.png&#34; alt=&#34;Summary tab showing replica and HPA attributes, a status message, and a table of current and recommended per-pod and total requests and cost with the impact of each change&#34;&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;GPU optimization (early access)&lt;/strong&gt;&lt;br&gt;&#xA;StormForge now shows GPU usage for workloads that use NVIDIA GPUs: per-workload GPU memory and allocation on the Summary and Recommendation tabs, and device-level activity in a new GPU tab. Requires StormForge Agent 3.2.0 and the new Node Agent, which is disabled by default. See &lt;a href=&#34;/docs/recommendations/gpu/&#34;&gt;GPU optimization&lt;/a&gt; and &lt;a href=&#34;/docs/installation/node-agent-config/&#34;&gt;Node Agent configuration&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 3.2.0</title>
				<link>/docs/releases/stormforge/v3.2.0/</link>
				<pubDate>Mon, 21 Sep 2026 21:13:54 +0000</pubDate>
				<guid>/docs/releases/stormforge/v3.2.0/</guid>
				<description>&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;GPU optimization (early access)&lt;/strong&gt;: StormForge can now collect GPU metrics for workloads that use NVIDIA GPUs and show per-workload GPU memory usage and GPU allocation alongside device-level GPU activity. See &lt;a href=&#34;/docs/recommendations/gpu/&#34;&gt;GPU optimization&lt;/a&gt;.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;StormForge Node Agent&lt;/strong&gt;: A new optional DaemonSet, &lt;code&gt;stormforge-node-agent&lt;/code&gt;, collects the GPU metrics from GPU nodes. It is disabled by default; enable it with &lt;code&gt;--set nodeAgent.enabled=true&lt;/code&gt;. See &lt;a href=&#34;/docs/installation/node-agent-config/&#34;&gt;Node Agent configuration&lt;/a&gt;.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;GPU workload detection&lt;/strong&gt;: Workloads that request a GPU, whether through a GPU extended resource such as &lt;code&gt;nvidia.com/gpu&lt;/code&gt; or through a Dynamic Resource Allocation resource claim, are identified by StormForge. Detection needs no configuration and does not require the Node Agent.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Dependency updates&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 3.1.3</title>
				<link>/docs/releases/stormforge/v3.1.3/</link>
				<pubDate>Thu, 17 Sep 2026 23:47:13 +0000</pubDate>
				<guid>/docs/releases/stormforge/v3.1.3/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Dependency updates&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Recommendation status update conflict&lt;/strong&gt;: Resolved a conflict between the pod admission webhook and the Applier when updating recommendation status.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 3.1.2</title>
				<link>/docs/releases/stormforge/v3.1.2/</link>
				<pubDate>Wed, 09 Sep 2026 20:04:13 +0000</pubDate>
				<guid>/docs/releases/stormforge/v3.1.2/</guid>
				<description>&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Applier alerts change diffs&lt;/strong&gt;: Applier alerts sent to external endpoints when the applier applies recommendations now include full before-and-after diffs for resources that were changed.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Performance improvements&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Dependency updates&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Missing RBAC for Events&lt;/strong&gt;: The Applier now includes RBAC to allow creating and patching Events when use of the Edit role is disabled.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Stale cost metric retention&lt;/strong&gt;: The Agent now correctly removes cost-related metrics for deleted pods not owned by workload types StormForge recognizes. Previously, some of these metrics were retained until the Agent restarted.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.28.6-agent</title>
				<link>/docs/releases/stormforge/previous/v2.28.6-agent/</link>
				<pubDate>Fri, 04 Sep 2026 19:08:35 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.28.6-agent/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependency Updates&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Pod-scoped metrics retention:&lt;/strong&gt; Fixed an issue where pod-scoped metrics could leak after pod deletion&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Metrics store name collision:&lt;/strong&gt; Fixed metrics collision issue for pods with the same name, which could result in overwriting or deleting metrics&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>August 2026</title>
				<link>/docs/releases/whats-new/2026-08/</link>
				<pubDate>Mon, 31 Aug 2026 00:00:00 +0000</pubDate>
				<guid>/docs/releases/whats-new/2026-08/</guid>
				<description>&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Redesigned Recommendation tab&lt;/strong&gt;&lt;br&gt;&#xA;The Recommendation tab on the workload details page now shows current and recommended requests and limits side by side for each container, with usage sparklines and the percentage change. Expand a container for CPU and memory charts with selectable time ranges, percentile readouts, and OOMKilled and CPU throttling markers.&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;/img/docs/whats-new-2026-08-recommendation-tab.png&#34; alt=&#34;Recommendation tab showing current and recommended values for a container with CPU and memory usage charts&#34;&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 6.2.9</title>
				<link>/docs/releases/stormforge-cli/v6.2.9/</link>
				<pubDate>Mon, 24 Aug 2026 22:04:29 +0000</pubDate>
				<guid>/docs/releases/stormforge-cli/v6.2.9/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Upgrade Go to 1.26.7&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Addressed an issue where &lt;code&gt;stormforge create recommendation --auto-deploy&lt;/code&gt; reported a timeout instead of a failure&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>July 2026</title>
				<link>/docs/releases/whats-new/2026-07/</link>
				<pubDate>Fri, 31 Jul 2026 00:00:00 +0000</pubDate>
				<guid>/docs/releases/whats-new/2026-07/</guid>
				<description>&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Schedule time zone shown in workload settings&lt;/strong&gt;&lt;br&gt;&#xA;The Schedule section of a workload&amp;rsquo;s Settings tab displays the time zone its schedule expressions are evaluated in.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Workload expiration extended from 14 to 28 days&lt;/strong&gt;&lt;br&gt;&#xA;Workloads that stop reporting now remain available for 28 days before they expire, doubled from the previous 14 days.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 3.1.1</title>
				<link>/docs/releases/stormforge/v3.1.1/</link>
				<pubDate>Fri, 24 Jul 2026 17:19:36 +0000</pubDate>
				<guid>/docs/releases/stormforge/v3.1.1/</guid>
				<description>&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;OpenShift pod scheduling:&lt;/strong&gt; The consolidated v3 chart no longer applies a hardcoded pod &lt;code&gt;securityContext&lt;/code&gt; (&lt;code&gt;fsGroup&lt;/code&gt;/&lt;code&gt;runAsGroup&lt;/code&gt;/&lt;code&gt;runAsUser: 65534&lt;/code&gt;) when &lt;code&gt;openshift=true&lt;/code&gt; and &lt;code&gt;commonPodSecurityContext&lt;/code&gt; is unset.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 6.2.8</title>
				<link>/docs/releases/stormforge-cli/v6.2.8/</link>
				<pubDate>Thu, 23 Jul 2026 22:16:18 +0000</pubDate>
				<guid>/docs/releases/stormforge-cli/v6.2.8/</guid>
				<description>&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Support for GPU workload filtering&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependency updates&lt;/li&gt;&#xA;&lt;li&gt;Switched Homebrew tap to use a cask instead of a formula&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;deprecated&#34;&gt;Deprecated&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#deprecated&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The &lt;code&gt;stormforge mcp&lt;/code&gt; command. The stdio MCP server is deprecated in favor of the hosted StormForge MCP server.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Various fixes for the Agent v2 to v3 migration tool&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 3.1.0</title>
				<link>/docs/releases/stormforge/v3.1.0-agent/</link>
				<pubDate>Thu, 23 Jul 2026 20:20:18 +0000</pubDate>
				<guid>/docs/releases/stormforge/v3.1.0-agent/</guid>
				<description>&lt;div class=&#34;alert alert-info&#34; role=&#34;alert&#34;&gt;&lt;div class=&#34;h4 alert-heading&#34; role=&#34;heading&#34;&gt;Renamed chart parameters&lt;/div&gt;&#xA;&lt;p&gt;The &lt;code&gt;agent&lt;/code&gt; parameter group is renamed to &lt;code&gt;clusterAgent&lt;/code&gt;, and &lt;code&gt;exporter&lt;/code&gt; to &lt;code&gt;forwarder&lt;/code&gt;. The deprecated &lt;code&gt;agent.*&lt;/code&gt; and &lt;code&gt;exporter.*&lt;/code&gt; values still work, overriding their &lt;code&gt;clusterAgent.*&lt;/code&gt; and &lt;code&gt;forwarder.*&lt;/code&gt; equivalents, and will be removed in a future major version. Update your values when convenient.&lt;/p&gt;&#xA;&lt;/div&gt;&#xA;&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;JVM old-gen live-set metric&lt;/strong&gt;: The forwarder (formerly &lt;code&gt;exporter&lt;/code&gt;) now collects &lt;code&gt;jvm_memory_pool_collection_used_bytes&lt;/code&gt; for live data size transforms.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Chart &lt;code&gt;deepOverride&lt;/code&gt; helper&lt;/strong&gt;: Explicit-zero-preserving merge helper so intentional &lt;code&gt;0&lt;/code&gt; values in overrides are no longer dropped.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;&lt;code&gt;exporter&lt;/code&gt; component renamed to &lt;code&gt;forwarder&lt;/code&gt;&lt;/strong&gt;: The &lt;code&gt;exporter&lt;/code&gt; Helm values key is renamed to &lt;code&gt;forwarder&lt;/code&gt;. The old key is deprecated but still works (see the note above).&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;&lt;code&gt;agent&lt;/code&gt; component renamed to &lt;code&gt;cluster-agent&lt;/code&gt;&lt;/strong&gt;: The &lt;code&gt;agent&lt;/code&gt; Helm values key is renamed to &lt;code&gt;clusterAgent&lt;/code&gt;, and the agent config file to &lt;code&gt;cluster-agent.yml&lt;/code&gt;. The old key is deprecated but still works (see the note above); the config file is passed via &lt;code&gt;--config&lt;/code&gt;, so no action is needed for it.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Webhook injection scope narrowed to the applier&amp;rsquo;s own pods&lt;/strong&gt;: The mutating webhook exclusion no longer covers the entire release namespace. It now skips only pods labeled &lt;code&gt;webhook.stormforge.io/skip&lt;/code&gt; (which the applier carries). As a result:&#xA;&lt;ul&gt;&#xA;&lt;li&gt;StormForge&amp;rsquo;s own workloads in the release namespace become eligible for webhook-based apply.&lt;/li&gt;&#xA;&lt;li&gt;The release namespace may now appear in &lt;code&gt;allowNamespaces&lt;/code&gt;.&lt;/li&gt;&#xA;&lt;li&gt;Helm 4 server-side-apply upgrades work without &lt;code&gt;--force-conflicts&lt;/code&gt;.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Quieter logging&lt;/strong&gt;: Pod spec generation failures now log at debug instead of error.&lt;/li&gt;&#xA;&lt;li&gt;Dependency updates&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Applier init container fails behind a corporate CA/proxy&lt;/strong&gt;: The applier init container (&lt;code&gt;applier license-check&lt;/code&gt;, which calls the StormForge API over TLS) now mounts &lt;code&gt;additionalVolumeMounts&lt;/code&gt;. Previously it mounted no volumes, so customers injecting a corporate CA cert hit &lt;code&gt;x509: certificate signed by unknown authority&lt;/code&gt; during init and the pod never started. Restores the 2.x chart behavior and matches the &lt;code&gt;additionalVolumeMounts&lt;/code&gt; docs (&amp;ldquo;added to all containers&amp;rdquo;).&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;&lt;code&gt;SuspendState&lt;/code&gt; event silently skipped&lt;/strong&gt;: The applier Deployment now projects &lt;code&gt;POD_NAME&lt;/code&gt; / &lt;code&gt;POD_NAMESPACE&lt;/code&gt; from the downward API, so the applier can resolve its own Deployment and emit the &lt;code&gt;SuspendState&lt;/code&gt; event on startup (for example, when setting &lt;code&gt;suspend=All&lt;/code&gt;). Previously this failed with &lt;code&gt;ErrSelfPodEnvUnset&lt;/code&gt; and only logged a warning.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.28.5-agent</title>
				<link>/docs/releases/stormforge/previous/v2.28.5-agent/</link>
				<pubDate>Fri, 17 Jul 2026 15:42:32 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.28.5-agent/</guid>
				<description>&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Fixes an issue where webhook-injected sidecars (e.g. istio-proxy, linkerd-proxy, etc) could be omitted from right-sizing.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.15.3-applier</title>
				<link>/docs/releases/stormforge/previous/v2.15.3-applier/</link>
				<pubDate>Wed, 15 Jul 2026 20:06:13 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.15.3-applier/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependency Updates&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Fix suspend mode Kubernetes event emission on start-up&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.28.4-agent</title>
				<link>/docs/releases/stormforge/previous/v2.28.4-agent/</link>
				<pubDate>Wed, 15 Jul 2026 16:26:54 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.28.4-agent/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependency Updates&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Stale container requests/limits pruned&lt;/strong&gt;: request/limit metric series for containers removed from a workload&amp;rsquo;s spec no longer keep being emitted indefinitely during stuck rollouts or after agent restarts mid-rollout.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;StatefulSet revision handling&lt;/strong&gt;: pod revision checks now handle StatefulSets (controller-revision-hash label) and requeue with backoff on lookup failure instead of risking a wrong-revision pod&amp;rsquo;s spec being reported as the workload&amp;rsquo;s observed settings.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;ScheduledSparkApplication pods detected again&lt;/strong&gt;: executor pods of Spark apps launched by a ScheduledSparkApplication use a non-controller ownerRef, so the owner walk stopped early; the agent now uses the &lt;code&gt;sparkoperator.k8s.io/scheduled-app-name&lt;/code&gt; label to attribute them, restoring metrics for these workloads.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>June 2026</title>
				<link>/docs/releases/whats-new/2026-06/</link>
				<pubDate>Tue, 30 Jun 2026 00:00:00 +0000</pubDate>
				<guid>/docs/releases/whats-new/2026-06/</guid>
				<description>&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;StormForge Agent 3.0&lt;/strong&gt;&lt;br&gt;&#xA;A single &lt;code&gt;stormforge&lt;/code&gt; Helm chart now installs the Agent and Applier together, replacing the separate &lt;code&gt;stormforge-agent&lt;/code&gt; chart. Upgrading from v2 is a breaking change that requires migration. See &lt;a href=&#34;/docs/releases/stormforge/&#34;&gt;StormForge Agent releases&lt;/a&gt; and &lt;a href=&#34;/docs/installation/migration/&#34;&gt;Migrate v2 to v3&lt;/a&gt;.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 6.2.7</title>
				<link>/docs/releases/stormforge-cli/v6.2.7/</link>
				<pubDate>Mon, 15 Jun 2026 18:02:21 +0000</pubDate>
				<guid>/docs/releases/stormforge-cli/v6.2.7/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependency updates&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 3.0.0</title>
				<link>/docs/releases/stormforge/v3.0.0-agent/</link>
				<pubDate>Wed, 10 Jun 2026 19:16:36 +0000</pubDate>
				<guid>/docs/releases/stormforge/v3.0.0-agent/</guid>
				<description>&lt;div class=&#34;alert alert-warning&#34; role=&#34;alert&#34;&gt;&lt;div class=&#34;h4 alert-heading&#34; role=&#34;heading&#34;&gt;Breaking change&lt;/div&gt;&#xA;&lt;p&gt;Version 3.0.0 unifies all StormForge components into a single Helm chart. Upgrading from the v2 Agent and Applier charts requires migration — see &lt;a href=&#34;/docs/installation/migration/&#34;&gt;Migrate v2 → v3&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;/div&gt;&#xA;&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Unified &lt;code&gt;stormforge&lt;/code&gt; Helm chart&lt;/strong&gt;: New chart that bundles the workload-agent and the applier in a single installation, replacing the separate &lt;code&gt;stormforge-agent&lt;/code&gt; chart. Required values are the same (&lt;code&gt;clusterName&lt;/code&gt;, &lt;code&gt;authorization.clientID&lt;/code&gt;, &lt;code&gt;authorization.clientSecret&lt;/code&gt;). &lt;strong&gt;Breaking change&lt;/strong&gt; — replaces &lt;code&gt;stormforge-agent&lt;/code&gt;.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;&lt;code&gt;workloadResourceKinds&lt;/code&gt; model&lt;/strong&gt;: A single list replaces the two parallel v2 parameters (&lt;code&gt;workloadResourceTypes&lt;/code&gt; + &lt;code&gt;ownerResourceTypes&lt;/code&gt;). Each entry carries an explicit &lt;code&gt;role&lt;/code&gt; field — &lt;code&gt;workload&lt;/code&gt;, &lt;code&gt;conditionalWorkload&lt;/code&gt;, &lt;code&gt;owner&lt;/code&gt;, &lt;code&gt;ignoredOwner&lt;/code&gt; — eliminating the ambiguity of separate lists. &lt;code&gt;patchTargetDefaults&lt;/code&gt; (renamed from &lt;code&gt;patchTargetTypeDefaults&lt;/code&gt;) is set per entry; the chart injects the required &lt;code&gt;live.stormforge.io/&lt;/code&gt; prefix internally. &lt;strong&gt;Breaking change&lt;/strong&gt; — see &lt;a href=&#34;/docs/installation/migration/&#34;&gt;Migrate v2 → v3&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;&lt;code&gt;includeCommonAddOnResourceKinds&lt;/code&gt;&lt;/strong&gt;: Replaces &lt;code&gt;includeCommonAddOnResourceTypes&lt;/code&gt;, enabled by default. Prepends curated entries for Argo Rollouts, Prometheus operator, OpenTelemetry collector, KEDA, and Dynatrace.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.15.2-applier</title>
				<link>/docs/releases/stormforge/previous/v2.15.2-applier/</link>
				<pubDate>Wed, 10 Jun 2026 18:22:03 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.15.2-applier/</guid>
				<description>&lt;h3 id=&#34;security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Go 1.26.4 toolchain and &lt;code&gt;x/crypto&lt;/code&gt; update&lt;/strong&gt;: Bumping &lt;code&gt;github.com/gramLabs/go-application&lt;/code&gt; to &lt;code&gt;v0.0.118&lt;/code&gt; transitively updates the Go toolchain to &lt;code&gt;1.26.4&lt;/code&gt; and &lt;code&gt;golang.org/x/crypto&lt;/code&gt; to &lt;code&gt;v0.52.0&lt;/code&gt;,&#xA;picking up all security fixes included in those releases.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.28.2-agent</title>
				<link>/docs/releases/stormforge/previous/v2.28.2-agent/</link>
				<pubDate>Thu, 04 Jun 2026 21:38:54 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.28.2-agent/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependency updates&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.15.1-applier</title>
				<link>/docs/releases/stormforge/previous/v2.15.1-applier/</link>
				<pubDate>Thu, 04 Jun 2026 20:43:01 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.15.1-applier/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependency Updates&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Fixed an issue where &lt;code&gt;WebhookImmediateRollout&lt;/code&gt; apply method while handling fallback on In-Place-Pod-Resize failure, might not deploy the correct recommendation across pod admission.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 6.2.6</title>
				<link>/docs/releases/stormforge-cli/v6.2.6/</link>
				<pubDate>Tue, 02 Jun 2026 19:50:48 +0000</pubDate>
				<guid>/docs/releases/stormforge-cli/v6.2.6/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The fields shown by &lt;code&gt;stormforge view workloads&lt;/code&gt; are now more consistent with the UI&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Reliability rate filters are usable to 4 decimal places&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>May 2026</title>
				<link>/docs/releases/whats-new/2026-05/</link>
				<pubDate>Sun, 31 May 2026 00:00:00 +0000</pubDate>
				<guid>/docs/releases/whats-new/2026-05/</guid>
				<description>&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;CPU throttling visibility&lt;/strong&gt;&lt;br&gt;&#xA;The Workloads page includes a CPU throttling column, and the workload details page includes a CPU throttling chart, so you can see which containers are hitting their CPU limits and how often.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.15.0-applier</title>
				<link>/docs/releases/stormforge/previous/v2.15.0-applier/</link>
				<pubDate>Wed, 20 May 2026 20:04:25 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.15.0-applier/</guid>
				<description>&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Suspend capability&lt;/strong&gt;: New &lt;code&gt;suspend&lt;/code&gt; Helm parameter disables applier&#xA;behavior at runtime without scaling down the Deployment or removing the webhook server.&#xA;Allowed values: &lt;code&gt;None&lt;/code&gt; (default), &lt;code&gt;NewRecommendations&lt;/code&gt;, &lt;code&gt;All&lt;/code&gt;. Invalid values are&#xA;rejected at startup. When &lt;code&gt;All&lt;/code&gt;, the webhook returns &lt;code&gt;Allowed&lt;/code&gt; immediately after decode&#xA;so the &lt;code&gt;MutatingWebhookConfiguration&lt;/code&gt; stays responsive.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Event reason renames&lt;/strong&gt; &lt;code&gt;(breaking)&lt;/code&gt;: All applier event reason strings have been&#xA;renamed to use StormForge domain language. Dashboards, alerts, or tooling that filters&#xA;on old reasons must be updated:&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;PatchApplied&lt;/code&gt;  &lt;code&gt;RecommendationApplied&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;PatchFailed&lt;/code&gt;  &lt;code&gt;RecommendationApplyFailed&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;PatchRolledBack&lt;/code&gt;  &lt;code&gt;RecommendationRolledBack&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;RollbackFailed&lt;/code&gt;  &lt;code&gt;RecommendationRollbackFailed&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;DriftDetected&lt;/code&gt;  &lt;code&gt;RecommendationDriftDetected&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;DriftReconciled&lt;/code&gt;  &lt;code&gt;RecommendationDriftReconciled&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;ValidationFailed&lt;/code&gt; (unrecoverable)  &lt;code&gt;RolloutValidationAbandoned&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;ValidationTimedOut&lt;/code&gt;  &lt;code&gt;RolloutValidationTimedOut&lt;/code&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 6.2.5</title>
				<link>/docs/releases/stormforge-cli/v6.2.5/</link>
				<pubDate>Tue, 19 May 2026 18:46:32 +0000</pubDate>
				<guid>/docs/releases/stormforge-cli/v6.2.5/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependency updates&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Fixed an issue where authorization tokens failed to refresh&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.14.0-applier</title>
				<link>/docs/releases/stormforge/previous/v2.14.0-applier/</link>
				<pubDate>Thu, 07 May 2026 18:08:37 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.14.0-applier/</guid>
				<description>&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Centralized Kubernetes Event Emission&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependency Updates&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 6.2.4</title>
				<link>/docs/releases/stormforge-cli/v6.2.4/</link>
				<pubDate>Wed, 06 May 2026 16:45:57 +0000</pubDate>
				<guid>/docs/releases/stormforge-cli/v6.2.4/</guid>
				<description>&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The &lt;code&gt;view workload&lt;/code&gt; command shows CPU throttling rate (when available)&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Made the &lt;code&gt;login --org&lt;/code&gt; flag optional&lt;/li&gt;&#xA;&lt;li&gt;Dependency updates&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Reliability filters on &lt;code&gt;view workload&lt;/code&gt; accept decimal numbers&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 6.2.3</title>
				<link>/docs/releases/stormforge-cli/v6.2.3/</link>
				<pubDate>Tue, 28 Apr 2026 17:07:56 +0000</pubDate>
				<guid>/docs/releases/stormforge-cli/v6.2.3/</guid>
				<description>&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Fixed a compatibility issue with v6.2.2 authorization tokens&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 6.2.2</title>
				<link>/docs/releases/stormforge-cli/v6.2.2/</link>
				<pubDate>Mon, 27 Apr 2026 21:21:16 +0000</pubDate>
				<guid>/docs/releases/stormforge-cli/v6.2.2/</guid>
				<description>&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Added a container level &lt;code&gt;stormforge get recommendations --container-resources&lt;/code&gt; alternate view&lt;/li&gt;&#xA;&lt;li&gt;Added a metric level &lt;code&gt;stormforge get recommendations --auto-scaling&lt;/code&gt; alternate view&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Update dependencies&lt;/li&gt;&#xA;&lt;li&gt;The estate-wide configuration editor no longer defaults to the internal YAML representation&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.28.1-agent</title>
				<link>/docs/releases/stormforge/previous/v2.28.1-agent/</link>
				<pubDate>Thu, 16 Apr 2026 20:58:48 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.28.1-agent/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Add RBAC for OpenShift operator-owned workloads when &lt;code&gt;openshift=true&lt;/code&gt;.&lt;/li&gt;&#xA;&lt;li&gt;Update prometheus container version to 3.11.2&lt;/li&gt;&#xA;&lt;li&gt;Dependency Updates:&#xA;&lt;ul&gt;&#xA;&lt;li&gt;kubernetes library group to 0.35.4.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;prometheus/prometheus&lt;/code&gt; to 0.311.2.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;gramLabs/go-application&lt;/code&gt; to 0.0.115.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;gramLabs/stormforge-go&lt;/code&gt; to 4.9.1.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.13.0-applier</title>
				<link>/docs/releases/stormforge/previous/v2.13.0-applier/</link>
				<pubDate>Mon, 13 Apr 2026 15:29:50 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.13.0-applier/</guid>
				<description>&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Adds Drift Reconciliation for Horizontal Pod Autoscalers&lt;/li&gt;&#xA;&lt;li&gt;Detects when StormForge Recommendations are rejected because of Cluster settings and triggers rollback faster.&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Failure Conditions detected: ResourceQuota violations, LimitRange validation, and Core Pod validation&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependency Updates:&#xA;&lt;ul&gt;&#xA;&lt;li&gt;kubernetes libraries to 0.35.3&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;argoproj/argo-rollouts&lt;/code&gt; to 1.9.0&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;rs/zerolog&lt;/code&gt; to 1.35.0&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;gramLabs/stormforge-go&lt;/code&gt; to 4.9.0&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;gramLabs/go-application&lt;/code&gt; to 0.0.114&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;gramLabs/structured-logging&lt;/code&gt; to 0.0.7&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;gramLabs/stormforge-agent/v2&lt;/code&gt; to 2.28.0.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Fixed an issue where Drift Reconciliation for Workloads was not retrieving the last applied recommendation sometimes.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Updated Go to 1.26.2.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.28.0-agent</title>
				<link>/docs/releases/stormforge/previous/v2.28.0-agent/</link>
				<pubDate>Thu, 09 Apr 2026 21:55:38 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.28.0-agent/</guid>
				<description>&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Adds support for In-API Cluster Config&lt;/li&gt;&#xA;&lt;li&gt;Adds user-override configuration for &lt;code&gt;clusterProvider&lt;/code&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;To configure custom provider string, add the following to helm values:&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;clusterProvider: exampleProvider&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;ul&gt;&#xA;&lt;li&gt;Adds support for custom cluster labels&#xA;&lt;ul&gt;&#xA;&lt;li&gt;To configure cluster labels, add the following to helm values:&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;clusterLabels:&#xA;  key1: value1&#xA;  key2: value2&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Updated Dependencies:&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;go-jose/go-jose/v4&lt;/code&gt; to 4.1.4.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;prometheus/prometheus&lt;/code&gt; to 0.311.1.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;aws/aws-sdk-go-v2/service/cloudwatchlogs&lt;/code&gt; to 1.65.0.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;aws/aws-sdk-go-v2/service/lambda&lt;/code&gt; to 1.88.5.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;aws/aws-sdk-go-v2/service/s3&lt;/code&gt; to 1.97.3.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;google/cel-go&lt;/code&gt; to 0.28.0.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;gramLabs/go-application&lt;/code&gt; to 0.0.114.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Updated Go to 1.26.2.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.27.4-agent</title>
				<link>/docs/releases/stormforge/previous/v2.27.4-agent/</link>
				<pubDate>Wed, 01 Apr 2026 20:20:08 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.27.4-agent/</guid>
				<description>&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Adds new metrics:&#xA;&lt;ul&gt;&#xA;&lt;li&gt;container_cpu_cfs_throttled_periods_total&lt;/li&gt;&#xA;&lt;li&gt;container_cpu_cfs_periods_total&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Adds ability to configure Auth credentials secret and env in Helm.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Strictly check file-based cluster-default config on startup and fail if invalid.&lt;/li&gt;&#xA;&lt;li&gt;Dependency Updates:&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;golang.org/x/oauth2&lt;/code&gt; to 0.36.0&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;k8s.io/klog/v2&lt;/code&gt; to 2.140.0&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;gruntwork-io/terratest&lt;/code&gt; to 0.56.0&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;google.golang.org/grpc&lt;/code&gt; to 1.79.3&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;argoproj/argo-rollouts&lt;/code&gt; to 1.9.0&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;gramLabs/go-application&lt;/code&gt; to 0.0.113&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;gramLabs/stormforge-go/v4&lt;/code&gt; to 4.9.0&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;gramLabs/structured-logging&lt;/code&gt; to 0.0.7&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>March 2026</title>
				<link>/docs/releases/whats-new/2026-03/</link>
				<pubDate>Tue, 31 Mar 2026 00:00:00 +0000</pubDate>
				<guid>/docs/releases/whats-new/2026-03/</guid>
				<description>&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;HPA settings shown on the workload details page&lt;/strong&gt;&lt;br&gt;&#xA;Workloads managed by a Horizontal Pod Autoscaler now show their HPA settings on the workload details page. See &lt;a href=&#34;/docs/configure/settings/hpa/&#34;&gt;HPA&lt;/a&gt; for how StormForge adjusts target utilization when it changes resource requests.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 6.2.1</title>
				<link>/docs/releases/stormforge-cli/v6.2.1/</link>
				<pubDate>Wed, 25 Mar 2026 21:15:29 +0000</pubDate>
				<guid>/docs/releases/stormforge-cli/v6.2.1/</guid>
				<description>&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Fixes an issue where StormForge tokens may not be properly decoded&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 6.2.0</title>
				<link>/docs/releases/stormforge-cli/v6.2.0/</link>
				<pubDate>Mon, 23 Mar 2026 22:16:52 +0000</pubDate>
				<guid>/docs/releases/stormforge-cli/v6.2.0/</guid>
				<description>&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Add an MCP Server to allow AI assistants to interact with the StormForge platform&lt;/li&gt;&#xA;&lt;li&gt;Added support for editing global configuration&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependency updates&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.12.2-applier</title>
				<link>/docs/releases/stormforge/previous/v2.12.2-applier/</link>
				<pubDate>Fri, 13 Mar 2026 19:10:25 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.12.2-applier/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependency Updates:&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;gramLabs/go-application&lt;/code&gt; to 0.0.112.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Fixed a bug that causes Applier to panic when applying pod resize to ArgoRollouts.&lt;/li&gt;&#xA;&lt;li&gt;Allows webhook cert-controller to be disabled.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Updated Go to 1.26.1.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;golang.org/x/oauth2&lt;/code&gt; to 0.36.0.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.12.1-applier</title>
				<link>/docs/releases/stormforge/previous/v2.12.1-applier/</link>
				<pubDate>Thu, 05 Mar 2026 20:56:07 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.12.1-applier/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Improved RBAC scope of the applier&lt;/li&gt;&#xA;&lt;li&gt;Improve Webhook TLS and certificate management&lt;/li&gt;&#xA;&lt;li&gt;Dependency Updates:&#xA;&lt;ul&gt;&#xA;&lt;li&gt;kubernetes libs to &lt;code&gt;0.35.2&lt;/code&gt;.&lt;/li&gt;&#xA;&lt;li&gt;stormforge-agent libs to 2.27.3&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.27.3-agent</title>
				<link>/docs/releases/stormforge/previous/v2.27.3-agent/</link>
				<pubDate>Thu, 05 Mar 2026 19:56:03 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.27.3-agent/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Enables Optimization CRDs by default.&lt;/li&gt;&#xA;&lt;li&gt;Updated default prometheus container image to 3.10.0.&lt;/li&gt;&#xA;&lt;li&gt;Dependency Updates:&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;filippo.io/edwards25519&lt;/code&gt; to 1.1.1.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;prometheus/prometheus&lt;/code&gt; to 0.310.0.&lt;/li&gt;&#xA;&lt;li&gt;kubernetes libs to 0.35.2.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Fixed a bug where the Agent could send duplicate StatusChanges for a workload, causing an error.&lt;/li&gt;&#xA;&lt;li&gt;Fixed several Helm issues&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>February 2026</title>
				<link>/docs/releases/whats-new/2026-02/</link>
				<pubDate>Sat, 28 Feb 2026 00:00:00 +0000</pubDate>
				<guid>/docs/releases/whats-new/2026-02/</guid>
				<description>&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Recommendations applied without restarting Pods&lt;/strong&gt;&lt;br&gt;&#xA;The webhook apply methods now use Kubernetes in-place Pod resizing by default, updating requests and limits on running Pods instead of triggering a rollout. Requires Applier v2.12.0 or later and Kubernetes v1.33 or later; on earlier Kubernetes versions these methods fall back to a rollout or defer the change until the next restart. See &lt;a href=&#34;/docs/configure/settings/apply-settings/&#34;&gt;Apply settings&lt;/a&gt;.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.12.0-applier</title>
				<link>/docs/releases/stormforge/previous/v2.12.0-applier/</link>
				<pubDate>Thu, 19 Feb 2026 19:18:59 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.12.0-applier/</guid>
				<description>&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;In-Place-Pod-Resize Support&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;To enable, set the workload&amp;rsquo;s &lt;code&gt;apply.method&lt;/code&gt; setting to &lt;code&gt;WebhookImmediateRollout&lt;/code&gt; or &lt;code&gt;WebhookHybridRollout&lt;/code&gt;.&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;WebhookImmediateRollout&lt;/code&gt; - Use a mutating webhook to modify Pods at admission. Existing pods will be resized in place when a new recommendation is applied. If Pods cannot be resized in place, a rollout/restart will be triggered.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;WebhookHybridRollout&lt;/code&gt; - Use a mutating webhook to modify Pods at admission. Existing pods will be resized in place when a new recommendation is applied. If Pods cannot be resized in place, changes will be deferred until the next rollout.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;HPA Reconciliation - Applier will watch, detect, and reconcile any drift in HPA &lt;code&gt;TargetUtilization&lt;/code&gt; setting.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;To enable this via helm:&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.27.2-agent</title>
				<link>/docs/releases/stormforge/previous/v2.27.2-agent/</link>
				<pubDate>Thu, 19 Feb 2026 17:35:58 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.27.2-agent/</guid>
				<description>&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Fixed a bug where the Agent would lose the pod-workload association if the only pod still in running state had an older generation.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependency Updates:&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;golang.org/x/oauth2&lt;/code&gt; to 0.35.0.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;github.com/google/cel-go&lt;/code&gt; to 0.27.0.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;argoproj/argo-rollouts&lt;/code&gt; to 1.8.4.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;gramLabs/stormforge-go/v4&lt;/code&gt; to 4.8.4.&lt;/li&gt;&#xA;&lt;li&gt;kubernetes libraries to 0.35.1.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Updated to Go 1.25.7.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.27.1-agent</title>
				<link>/docs/releases/stormforge/previous/v2.27.1-agent/</link>
				<pubDate>Fri, 23 Jan 2026 01:26:50 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.27.1-agent/</guid>
				<description>&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Added &lt;code&gt;ClusterOptimizationConfiguration&lt;/code&gt; and &lt;code&gt;OptimizationConfiguration&lt;/code&gt; Custom Resource Definitions (CRDs).&lt;br&gt;&#xA;&lt;em&gt;This release makes these CR types available, but they are not yet enabled by default. Use the Helm parameter &lt;code&gt;enableOptimizationConfigurationCRDs=true&lt;/code&gt; to opt in to using them.&lt;/em&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Updated Dependencies:&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;gruntwork-io/terratest&lt;/code&gt; to 0.55.0.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Updated Go to 1.25.6&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.26.0-agent</title>
				<link>/docs/releases/stormforge/previous/v2.26.0-agent/</link>
				<pubDate>Wed, 14 Jan 2026 19:35:29 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.26.0-agent/</guid>
				<description>&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Helm parameter &lt;code&gt;workloadResourceTypes&lt;/code&gt;: it defines CRD workload types for which support is not built-in to StormForge. It has subfield &lt;code&gt;patchTargetTypeDefaults&lt;/code&gt; to define patchpaths.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Helm parameter &lt;code&gt;ownerResourceTypes&lt;/code&gt;:  it defines configuration for types which may own workloads.  This parameter can be used to define default patch-paths for each owner type, to define owner types to ignore (treat as if they do not own workloads), or types at which to stop owner reference traversal. The subfields are &lt;code&gt;stopTraversal&lt;/code&gt;, &lt;code&gt;ignoreOwner&lt;/code&gt; and &lt;code&gt;patchTargetTypeDefaults&lt;/code&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.11.0-applier</title>
				<link>/docs/releases/stormforge/previous/v2.11.0-applier/</link>
				<pubDate>Fri, 09 Jan 2026 22:24:31 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.11.0-applier/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Attention: mutation webhook is now enabled by default with &lt;code&gt;webhook.enabled=true&lt;/code&gt; part of the helm values file. If one does not want to have the mutation webhook feature enabled, one needs to specify &lt;code&gt;webhook.enabled=false&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;Expose applier metrics via port 8080 as part of the webhook service&lt;/li&gt;&#xA;&lt;li&gt;Bumped K8s libraries to 1.35&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Helm parameter to support network policies: &lt;code&gt;networkPolicies.create=true&lt;/code&gt; and optionally for egress network policy &lt;code&gt;networkPolicies.additionalEgressRules&lt;/code&gt; with sample example on file&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Addressed CVE-2025-61729&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.25.1-agent</title>
				<link>/docs/releases/stormforge/previous/v2.25.1-agent/</link>
				<pubDate>Fri, 09 Jan 2026 22:11:05 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.25.1-agent/</guid>
				<description>&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Sample egress network policy on helm values file&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Bumped prometheus common library to latest version&lt;/li&gt;&#xA;&lt;li&gt;Bumped prometheus to &lt;code&gt;v3.9.1&lt;/code&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;A config parse condition when specifying &lt;code&gt;clusterDefaultsAutoDeployExemptNamespaces&lt;/code&gt; that cause agent not to start&lt;/li&gt;&#xA;&lt;li&gt;in rare occasions, fixed missing &amp;ldquo;selector&amp;rdquo; field on HPA external metrics.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Addressed CVE-2025-61729&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.10.1-applier</title>
				<link>/docs/releases/stormforge/previous/v2.10.1-applier/</link>
				<pubDate>Fri, 19 Dec 2025 04:00:45 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.10.1-applier/</guid>
				<description>&lt;h3 id=&#34;security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Addressed CVE-2025-68156&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.25.0-agent</title>
				<link>/docs/releases/stormforge/previous/v2.25.0-agent/</link>
				<pubDate>Fri, 19 Dec 2025 02:05:49 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.25.0-agent/</guid>
				<description>&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Helm Parameter &lt;code&gt;clusterDefaultsAutoDeployExemptNamespaces&lt;/code&gt;&lt;/strong&gt;&lt;br&gt;&#xA;This new Helm parameter defines a list of namespaces for which the &lt;code&gt;auto-deploy&lt;/code&gt; setting defined&#xA;in the cluster-defaults ConfigMap will be ignored.&lt;/p&gt;&#xA;&lt;p&gt;This parameter has a default value of &lt;code&gt;[&amp;quot;^kube-system$&amp;quot;, &amp;quot;^openshift.*&amp;quot;]&lt;/code&gt;. Workloads in&#xA;namespaces matching these regular expressions will not be subject to the &lt;code&gt;auto-deploy&lt;/code&gt; setting&#xA;defined in cluster-defaults. To enable &lt;code&gt;auto-deploy&lt;/code&gt; on workloads in affected namespaces, you&#xA;must use a namespace annotation, or a workload annotation.&lt;/p&gt;&#xA;&lt;p&gt;To modify this behavior, set the parameter to &lt;code&gt;null&lt;/code&gt; or to a list of regular expressions that you&#xA;define.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.24.4-agent</title>
				<link>/docs/releases/stormforge/previous/v2.24.4-agent/</link>
				<pubDate>Mon, 15 Dec 2025 20:11:41 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.24.4-agent/</guid>
				<description>&lt;p&gt;Fixed&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Fixed a Helm template ConfigMap rendering issue when using &lt;code&gt;patchTargetTypes&lt;/code&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.10.0-applier</title>
				<link>/docs/releases/stormforge/previous/v2.10.0-applier/</link>
				<pubDate>Thu, 11 Dec 2025 21:26:14 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.10.0-applier/</guid>
				<description>&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Added a Parameter manage Recommendation Ready Timeout. Defaults to &lt;code&gt;1H&lt;/code&gt;. This configurable parameter prevents stale recommendations from being applied at Applier start.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Dropped the de-dup logic to handle recommendation items, relying on state&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Setting a recommendation item to &lt;code&gt;FailedtoApply&lt;/code&gt; when the recommendation does not have a patch list&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Dependency Updates:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;kubernetes libs to 0.34.3.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;sigs.k8s.io/controller-runtime&lt;/code&gt; to 0.22.4.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;golang.org/x/oauth2&lt;/code&gt; to 0.34.0.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;open-policy-agent/cert-controller&lt;/code&gt; to 0.15.0.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;prometheus/common&lt;/code&gt; to 0.67.1.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;spf13/cobra&lt;/code&gt; to 1.10.2.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;gramLabs/go-application&lt;/code&gt; to 0.0.108.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;gramLabs/stormforge-agent&lt;/code&gt; to 2.24.3.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Fixed scenario that applier needed to be restarted to reapply recommendations that are set to be &amp;ldquo;Ready&amp;rdquo; via &lt;code&gt;sf apply&lt;/code&gt;. The solution was changing the de-dup logic of the applier.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.24.3-agent</title>
				<link>/docs/releases/stormforge/previous/v2.24.3-agent/</link>
				<pubDate>Thu, 11 Dec 2025 20:47:23 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.24.3-agent/</guid>
				<description>&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Added a helm parameter to dictate the setup the network policies &lt;code&gt;networkPolicies.create&lt;/code&gt;, default is false. Upon creation, the network policies are now functional (before the selectors were misconfigured). There is no egress policies being created by default (for such, please see the next bullet)&lt;/li&gt;&#xA;&lt;li&gt;Added helm parameters for extra network policies &lt;code&gt;networkPolicies.additionalIngressRules&lt;/code&gt; and &lt;code&gt;networkPolicies.additionalEgressRules&lt;/code&gt;.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;golang oauth2 &lt;code&gt;0.34.0&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;golang crypto &lt;code&gt;0.46.0&lt;/code&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;KEDA 2.18.2&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.24.2-agent</title>
				<link>/docs/releases/stormforge/previous/v2.24.2-agent/</link>
				<pubDate>Fri, 05 Dec 2025 01:55:20 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.24.2-agent/</guid>
				<description>&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Added collection of network metrics if &lt;code&gt;enableCostMetrics=true&lt;/code&gt;.&#xA;&lt;ul&gt;&#xA;&lt;li&gt;New metric name: &lt;code&gt;container_network_transmit_bytes_total&lt;/code&gt;.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Updated prometheus container version to 3.8.0.&lt;/li&gt;&#xA;&lt;li&gt;Dependency Updates:&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;prometheus/prometheus&lt;/code&gt; to 0.308.0.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;spf13/cobra&lt;/code&gt; to 1.10.2.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 6.1.1</title>
				<link>/docs/releases/stormforge-cli/v6.1.1/</link>
				<pubDate>Wed, 03 Dec 2025 22:09:49 +0000</pubDate>
				<guid>/docs/releases/stormforge-cli/v6.1.1/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Organization is required for logins when using &lt;code&gt;--url&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;Dependency updates&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.24.1-agent</title>
				<link>/docs/releases/stormforge/previous/v2.24.1-agent/</link>
				<pubDate>Tue, 25 Nov 2025 23:15:39 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.24.1-agent/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;When setting &lt;code&gt;enableCostMetrics&lt;/code&gt; to true (default is false), the user must now unset &lt;code&gt;workload.allowNamespaces&lt;/code&gt; and &lt;code&gt;workload.denyNamespaces&lt;/code&gt;. One can add the following lines on &lt;code&gt;values.yaml&lt;/code&gt;:&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;  workload:&#xA;    allowNamespaces: null&#xA;    denyNamespaces: null&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;h3 id=&#34;security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;prometheus to version &lt;code&gt;2.7.3&lt;/code&gt; to mitigate CVE-2025-54388&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.24.0-agent</title>
				<link>/docs/releases/stormforge/previous/v2.24.0-agent/</link>
				<pubDate>Thu, 20 Nov 2025 20:57:08 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.24.0-agent/</guid>
				<description>&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Adds support to define custom resource types to be recognized as StormForge workloads.&lt;/li&gt;&#xA;&lt;li&gt;Adds support to configure PatchPaths to optimize custom workload types and operators.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependency Updates:&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;gramLabs/go-application&lt;/code&gt; to 0.0.107.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;sigs.k8s.io/controller-runtime&lt;/code&gt; to 0.22.4.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;prometheus/common&lt;/code&gt; to 0.67.3.&lt;/li&gt;&#xA;&lt;li&gt;k8s libraries to 0.34.2.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Fixed an issue where &lt;code&gt;patchable: false&lt;/code&gt; status condition was being applied incorrectly.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;golang.org/x/oauth2&lt;/code&gt; to 0.33.0.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;golang.org/x/crypto&lt;/code&gt; to 0.45.0.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 6.1.0</title>
				<link>/docs/releases/stormforge-cli/v6.1.0/</link>
				<pubDate>Fri, 31 Oct 2025 16:01:37 +0000</pubDate>
				<guid>/docs/releases/stormforge-cli/v6.1.0/</guid>
				<description>&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The validity period can be specified when creating recommendations&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependency updates&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;deprecated&#34;&gt;Deprecated&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#deprecated&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The &lt;code&gt;--url&lt;/code&gt; option of the &lt;code&gt;stormforge login&lt;/code&gt; command will require an organization identifier in the next release&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.23.6-agent</title>
				<link>/docs/releases/stormforge/previous/v2.23.6-agent/</link>
				<pubDate>Thu, 30 Oct 2025 17:02:58 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.23.6-agent/</guid>
				<description>&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;[EXPERIMENTAL] One time specification of patch-paths for Custom Resource Workload Types.&lt;/li&gt;&#xA;&lt;li&gt;Added relabeling rules to Prometheus config to normalize opentelemetry JVM metrics to match client_java form.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependency Updates:&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;gramLabs/go-application&lt;/code&gt; to 0.0.106.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;gramLabs/stormforge-go&lt;/code&gt; to 4.8.0.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;golang.org/x/oauth2&lt;/code&gt; to 0.32.0.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;sigs.k8s.io/controller-runtime&lt;/code&gt; to 0.22.3.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;prometheus/prometheus&lt;/code&gt; to 0.307.3.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;prometheus/common&lt;/code&gt; to 0.67.2&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;kedacore/keda&lt;/code&gt; to 2.18.1.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Fixed an issue where deleting a WorkloadOptimizer CR does not update the &lt;code&gt;ManagedBy&lt;/code&gt; field for a Workload.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.23.5-agent</title>
				<link>/docs/releases/stormforge/previous/v2.23.5-agent/</link>
				<pubDate>Mon, 29 Sep 2025 18:31:09 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.23.5-agent/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Updated Dependencies&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;prometheus/prometheus&lt;/code&gt; to 0.306.0.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;gramlabs/stormforge-go&lt;/code&gt; to 4.7.11.&lt;/li&gt;&#xA;&lt;li&gt;Updated &lt;code&gt;prometheus&lt;/code&gt; container in Helm to 3.6.0.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;removed&#34;&gt;Removed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#removed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Removed deprecated &lt;code&gt;Secret&lt;/code&gt; helm template.&lt;/li&gt;&#xA;&lt;li&gt;Removed deprecated &lt;code&gt;autoDiscovery&lt;/code&gt; parameter.&lt;/li&gt;&#xA;&lt;li&gt;Removed support for &lt;code&gt;autoscaling/v2beta2&lt;/code&gt; version of HPA (no longer supported by Kubernetes).&lt;/li&gt;&#xA;&lt;li&gt;Removed unused startupProbe license check from the stormforge pod templates.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Removed the aggregate view in the ClusterRole template&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Go to &lt;code&gt;1.25.1&lt;/code&gt; to address CVE-2025-47910&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 6.0.2</title>
				<link>/docs/releases/stormforge-cli/v6.0.2/</link>
				<pubDate>Mon, 15 Sep 2025 17:25:55 +0000</pubDate>
				<guid>/docs/releases/stormforge-cli/v6.0.2/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependency updates&lt;/li&gt;&#xA;&lt;li&gt;Changed the version columns shown by &lt;code&gt;get clusters&lt;/code&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Corrected the URL emitted by the &lt;code&gt;check version&lt;/code&gt; command&lt;/li&gt;&#xA;&lt;li&gt;The patch command no longer ignores the target subresource&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.23.4-agent</title>
				<link>/docs/releases/stormforge/previous/v2.23.4-agent/</link>
				<pubDate>Wed, 10 Sep 2025 17:44:30 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.23.4-agent/</guid>
				<description>&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;[EXPERIMENTAL] Added helm chart parameter &lt;code&gt;enableCostMetrics&lt;/code&gt; to collect Cost Reporting metrics. Defaults to &lt;code&gt;false&lt;/code&gt;.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Update golang to 1.24.1.&lt;/li&gt;&#xA;&lt;li&gt;Dependencies update:&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;spf13/cobra&lt;/code&gt; to 1.10.1.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;spf13/pflag&lt;/code&gt; to 1.0.10.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;stretchr/testify&lt;/code&gt; to 1.11.1.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;x/oauth2&lt;/code&gt; to 0.31.0.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;sigs.k8s.io/controller-runtime&lt;/code&gt; to 0.22.1.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;prometheus/client_golang&lt;/code&gt; to 1.23.2.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;gramlabs/go-application&lt;/code&gt; to 0.0.105.&lt;/li&gt;&#xA;&lt;li&gt;kubernetes libraries to 0.34.1.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.9.2-applier</title>
				<link>/docs/releases/stormforge/previous/v2.9.2-applier/</link>
				<pubDate>Fri, 29 Aug 2025 17:06:40 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.9.2-applier/</guid>
				<description>&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Fixed an issue where new containers could be mistakenly added when using &lt;code&gt;DynamicAdmissionWebhook&lt;/code&gt; apply method.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.23.3-agent</title>
				<link>/docs/releases/stormforge/previous/v2.23.3-agent/</link>
				<pubDate>Fri, 22 Aug 2025 17:40:45 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.23.3-agent/</guid>
				<description>&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Fixed a bug that resulted in the workload sync did not properly sync to the API.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.9.1-applier</title>
				<link>/docs/releases/stormforge/previous/v2.9.1-applier/</link>
				<pubDate>Tue, 19 Aug 2025 19:19:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.9.1-applier/</guid>
				<description>&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Fixed an Argo Rollout Patch Validation failure (to mitigate Argo Rollout &lt;a href=&#34;https://github.com/argoproj/argo-rollouts/issues/3402&#34;&gt;type convention violation&lt;/a&gt;)&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependency Updates:&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;gramlabs/stormforge-agent&lt;/code&gt; to 2.23.1&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Update Go to 1.24.6 to address &lt;a href=&#34;https://pkg.go.dev/vuln/GO-2025-3849&#34;&gt;GO-2025-3849&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.23.2-agent</title>
				<link>/docs/releases/stormforge/previous/v2.23.2-agent/</link>
				<pubDate>Tue, 19 Aug 2025 19:18:26 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.23.2-agent/</guid>
				<description>&lt;h3 id=&#34;security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Update Go to 1.24.6 to address &lt;a href=&#34;https://pkg.go.dev/vuln/GO-2025-3849&#34;&gt;GO-2025-3849&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.23.1-agent</title>
				<link>/docs/releases/stormforge/previous/v2.23.1-agent/</link>
				<pubDate>Thu, 14 Aug 2025 21:52:56 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.23.1-agent/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Updated Prometheus Container version to 3.5.0&lt;/li&gt;&#xA;&lt;li&gt;Dependency Updates&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;prometheus/prometheus&lt;/code&gt; to 0.305.0.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;spf13/pflag&lt;/code&gt; to 1.0.7.&lt;/li&gt;&#xA;&lt;li&gt;kubernetes libs to 0.33.4.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;gramLabs/stormforge-go&lt;/code&gt; to 4.7.10.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;sigs.k8s.io/yaml&lt;/code&gt; to 1.6.0.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;prometheus/client_golang&lt;/code&gt; to 1.23.0.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Fixes an issue where a workload will be marked as patchable despite not having RBAC permissions.&lt;/li&gt;&#xA;&lt;li&gt;Fixes an issue where an unsupported workload or a workload without RBAC will cause a panic in the workload reconciler.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.9.0-applier</title>
				<link>/docs/releases/stormforge/previous/v2.9.0-applier/</link>
				<pubDate>Mon, 14 Jul 2025 19:03:12 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.9.0-applier/</guid>
				<description>&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;[Beta] Support for InPlace Pod Resizing on annotation &lt;code&gt;live.stormforge.io/apply.method=InPlacePodResizing&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;Added additional RBAC on Helm to support InPlace Pod Resizing&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependency Updates:&lt;/li&gt;&#xA;&lt;li&gt;controller-runtime 0.21.0&lt;/li&gt;&#xA;&lt;li&gt;e2e-framework to 0.6.0&lt;/li&gt;&#xA;&lt;li&gt;stormforge-go v4.7.9&lt;/li&gt;&#xA;&lt;li&gt;stormforge-agent v2.23.0&lt;/li&gt;&#xA;&lt;li&gt;google gnostic model v0.7.0&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Go to 1.24.5&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.23.0-agent</title>
				<link>/docs/releases/stormforge/previous/v2.23.0-agent/</link>
				<pubDate>Mon, 14 Jul 2025 18:30:20 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.23.0-agent/</guid>
				<description>&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Adds support for sending metrics and configuration to optimize init-container sidecars.&lt;/li&gt;&#xA;&lt;li&gt;Adds default requests values for Agent-installed deployments as a starting point. Users should set higher values as needed.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependencies&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;prometheus/prometheus&lt;/code&gt; to 0.304.2&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;argoproj/argo-rollouts&lt;/code&gt; to 1.8.3.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;gramLabs/go-application&lt;/code&gt; to 0.0.102.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;kedacore/keda&lt;/code&gt; to `2.17.1-0.20250521173204-e23ef462abb5.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;sigs.k8s.io/controller-runtime&lt;/code&gt; to 0.21.0.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;gramLabs/go-application&lt;/code&gt; to 0.0.102.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;gramLabs/stormforge-go&lt;/code&gt; to 4.7.9.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Fixes an issue where config for &lt;code&gt;patchPath&lt;/code&gt; annotations did not support Ephemeral Storage.&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Patch Paths can now be defined in quoted comma-delimited strings such as:&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;live.stormforge.io/containers.cpu.limits.patch-path: &amp;quot;/path1,/additional/path&amp;quot;&lt;/code&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Fixes a panic when unable to retrieve a pod from the Spark.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Go to 1.24.5.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.22.5</title>
				<link>/docs/releases/stormforge/previous/v2.22.5-agent/</link>
				<pubDate>Wed, 02 Jul 2025 19:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.22.5-agent/</guid>
				<description>&lt;h3 id=&#34;v2.22.5-agent-fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.22.5-agent-fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Fixed a WorkloadOptimizer resource issue that was preventing configuration from being applied correctly.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.8.3-applier</title>
				<link>/docs/releases/stormforge/previous/v2.8.3-applier/</link>
				<pubDate>Thu, 26 Jun 2025 19:57:07 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.8.3-applier/</guid>
				<description>&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Add Helm parameters to set &lt;code&gt;commonMetaLabels&lt;/code&gt; for StormForge deployed resources.&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Example &lt;code&gt;values.yaml&lt;/code&gt; configuration to set &lt;code&gt;commonMetaLabels&lt;/code&gt;:&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;commonMetaLabels:&#xA;  example.com/app: stormforge&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependency Updates:&#xA;&lt;ul&gt;&#xA;&lt;li&gt;kubernetes libraries to 0.33.2.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;argorproj/argo-rollouts&lt;/code&gt; to 1.8.3.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;sigs.k8s.io/yaml&lt;/code&gt; to 1.5.0.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.22.4</title>
				<link>/docs/releases/stormforge/previous/v2.22.4-agent/</link>
				<pubDate>Mon, 23 Jun 2025 13:00:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.22.4-agent/</guid>
				<description>&lt;h3 id=&#34;v2.22.4-agent-added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.22.4-agent-added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Added helm parameter to specify &lt;code&gt;securityContext&lt;/code&gt; for StormForge deployed containers.&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Example &lt;code&gt;values.yaml&lt;/code&gt; configuration to set &lt;code&gt;securityContext&lt;/code&gt; for containers in the &lt;code&gt;metrics-forwarder&lt;/code&gt; and &lt;code&gt;workload-controller&lt;/code&gt; pods.&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;commonContainerSecurityContext:&#xA;  allowPrivilegeEscalation: false&#xA;  capabilities:&#xA;    drop:&#xA;      - ALL&#xA;  readOnlyRootFilesystem: true&#xA;  seccompProfile:&#xA;    type: RuntimeDefault&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 6.0.1</title>
				<link>/docs/releases/stormforge-cli/v6.0.1/</link>
				<pubDate>Fri, 13 Jun 2025 19:40:26 +0000</pubDate>
				<guid>/docs/releases/stormforge-cli/v6.0.1/</guid>
				<description>&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Restored the v5 &lt;code&gt;edit cluster --reset-uid&lt;/code&gt; option&lt;/li&gt;&#xA;&lt;li&gt;Restored the v5 &lt;code&gt;--recommendation&lt;/code&gt; option for specifying recommendation names&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependency updates&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;removed&#34;&gt;Removed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#removed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The macOS binaries are no longer notarized&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Fixed an issue where get recommendations got too many results in YAML output&lt;/li&gt;&#xA;&lt;li&gt;Fixed an issue where the edit command would not report bad patch errors&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.8.2-applier</title>
				<link>/docs/releases/stormforge/previous/v2.8.2-applier/</link>
				<pubDate>Wed, 04 Jun 2025 20:20:02 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.8.2-applier/</guid>
				<description>&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;OLV2-2431 - Adding default requests on helm chart to set workload with Burstable QoS&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;OLV2-2426 - Applier in continuous reconciliation mode skips certain workloads&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Applier version 2.8.1</title>
				<link>/docs/releases/stormforge/previous/v2.8.1-applier/</link>
				<pubDate>Thu, 29 May 2025 19:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.8.1-applier/</guid>
				<description>&lt;h3 id=&#34;v2.8.1-applier-changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.8.1-applier-changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependencies&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;gramlabs/stormforge-go&lt;/code&gt; to 4.7.7&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;gramlabs/go-application&lt;/code&gt; to 0.0.101&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;gramlabs/stormforge-agent&lt;/code&gt; to 2.22.3&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.8.1-applier-security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.8.1-applier-security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;golang&lt;/code&gt; to 1.24.3 to address &lt;code&gt;GO-2025-3563&lt;/code&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.22.3</title>
				<link>/docs/releases/stormforge/previous/v2.22.3-agent/</link>
				<pubDate>Thu, 29 May 2025 18:00:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.22.3-agent/</guid>
				<description>&lt;h3 id=&#34;v2.22.3-agent-changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.22.3-agent-changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependencies&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;go-logr/logr&lt;/code&gt; to 1.4.3&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.22.3-agent-security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.22.3-agent-security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Upgraded Prometheus container dependency to 3.4.0 to address &lt;code&gt;CVE-2025-22871&lt;/code&gt;.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.22.2</title>
				<link>/docs/releases/stormforge/previous/v2.22.2-agent/</link>
				<pubDate>Wed, 28 May 2025 15:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.22.2-agent/</guid>
				<description>&lt;h3 id=&#34;v2.22.2-agent-added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.22.2-agent-added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Allows specifying multiple paths for patchPath setting:&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Example: &lt;code&gt;live.stormforge.io/containers.cpu.requests.patch-path: /path/to/target,containerA=&amp;quot;/new/path,/alternative/path&amp;quot;&lt;/code&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Version and build SHA on log during initialization&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.22.2-agent-changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.22.2-agent-changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;A new way to run controllers: a generic workload controller instead of multiple controllers used to support replica 0 workloads. Expected faster warm up time and more data integrity on annotations on replica 0 workloads.&lt;/li&gt;&#xA;&lt;li&gt;Dependencies&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;keda/v2&lt;/code&gt; to 2.17.1&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;prometheus/prometheus&lt;/code&gt; to 0.304.0&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;prometheus/common&lt;/code&gt; to 0.64.0&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;kubernetes libraries&lt;/code&gt; to 0.33.1&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;gramLabs/go-application&lt;/code&gt; to 0.0.100&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;gramLabs/stormforge-go&lt;/code&gt; to 4.7.7&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.22.2-agent-fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.22.2-agent-fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Potential problem of missing memory metrics when &lt;code&gt;ephemeral_storage&lt;/code&gt; is set.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.22.2-agent-security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.22.2-agent-security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;x/oauth2&lt;/code&gt; to 0.30.0&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;golang&lt;/code&gt; to 1.24.3 to address &lt;code&gt;GO-2025-3563&lt;/code&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Applier version 2.8.0</title>
				<link>/docs/releases/stormforge/previous/v2.8.0-applier/</link>
				<pubDate>Wed, 30 Apr 2025 09:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.8.0-applier/</guid>
				<description>&lt;h3 id=&#34;v2.8.0-applier-added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.8.0-applier-added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;[EXPERIMENTAL] Configuration for Alerts for Recommendation Apply Events&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.8.0-applier-fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.8.0-applier-fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;An issue where applying a patch to an unhealthy workload continued to rollback the patch.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.8.0-applier-changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.8.0-applier-changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependency updates:&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;gramLabs/stormforge-agent&lt;/code&gt; to 2.22.1&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;kubernetes/api&lt;/code&gt; to 0.33.0&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;Masterminds/sprig/v3&lt;/code&gt; to 3.3.0&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.22.1</title>
				<link>/docs/releases/stormforge/previous/v2.22.1-agent/</link>
				<pubDate>Mon, 21 Apr 2025 09:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.22.1-agent/</guid>
				<description>&lt;h3 id=&#34;v2.22.1-agent-added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.22.1-agent-added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Helm parameters to support auth configuration for JVM Scrape jobs&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.22.1-agent-fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.22.1-agent-fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;We fixed an issue where the Agent would fail if API Resource discovery partially fails.&lt;/li&gt;&#xA;&lt;li&gt;We fixed an issue with potential deadlock in the Node Cache.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Applier version 2.7.2</title>
				<link>/docs/releases/stormforge/previous/v2.7.2-applier/</link>
				<pubDate>Mon, 21 Apr 2025 09:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.7.2-applier/</guid>
				<description>&lt;h3 id=&#34;v2.7.2-applier-added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.7.2-applier-added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Add a flag &lt;code&gt;enableFallbackToClientSideApply&lt;/code&gt; to work around an issue when improper configuration on a patch target prevents us from being able to apply a recommendation using Server-Side Apply. Setting this flag to &lt;code&gt;true&lt;/code&gt; will result in handling errors by falling back to Client-Side Apply, &lt;strong&gt;which will disable automatic rollback in the event of healthcheck failures.&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.7.2-applier-changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.7.2-applier-changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependency updates:&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;x/oauth2&lt;/code&gt; to 0.29.0&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;golang/jwt/v4&lt;/code&gt; to 4.5.2&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;rs/zerolog&lt;/code&gt; to 1.34.0&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;structured-merge-diff/v4&lt;/code&gt; to 4.7.0&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;argoproj/argo-rollouts&lt;/code&gt; to 1.8.2&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;prometheus/client_golang&lt;/code&gt; to 1.22.0&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;controller-runtime&lt;/code&gt; to 0.20.4&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;gramLabs/stormforge-go/v4&lt;/code&gt; to 4.7.6&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;gramLabs/stormforge-agent/v2&lt;/code&gt; to 2.22.0&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.22.0</title>
				<link>/docs/releases/stormforge/previous/v2.22.0-agent/</link>
				<pubDate>Wed, 02 Apr 2025 19:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.22.0-agent/</guid>
				<description>&lt;h3 id=&#34;v2.22.0-agent-changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.22.0-agent-changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Internal improvements&lt;/strong&gt;&lt;br&gt;&#xA;Engineering work to support future feature additions&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.22.0-agent-added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.22.0-agent-added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Resource Request Mirroring&lt;/strong&gt;&lt;br&gt;&#xA;Enable recommendation mirroring, to support DR use cases or workloads owned by progressive delivery operators such as Flagger. Mirroring works by creating recommendations for a mirror workload based on usage metric observations of another. To configure mirroring, set the &lt;code&gt;metrics-from&lt;/code&gt; annotation on the mirror workload.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 6.0.0</title>
				<link>/docs/releases/stormforge-cli/v6.0.0/</link>
				<pubDate>Mon, 31 Mar 2025 18:41:19 +0000</pubDate>
				<guid>/docs/releases/stormforge-cli/v6.0.0/</guid>
				<description>&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;There is a new &lt;code&gt;stormforge view&lt;/code&gt; command for fetching output comparable to the web UI&lt;/li&gt;&#xA;&lt;li&gt;There is a new &lt;code&gt;stormforge describe&lt;/code&gt; command for fetching a more detailed view of a resource&lt;/li&gt;&#xA;&lt;li&gt;There is a new &lt;code&gt;stormforge manage&lt;/code&gt; command for manually configuring resources&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Commands accept a slash delimited name argument instead of (or in addition to) the filtering flags&lt;/li&gt;&#xA;&lt;li&gt;The &lt;code&gt;stormforge get&lt;/code&gt; command shows different fields&lt;/li&gt;&#xA;&lt;li&gt;The &lt;code&gt;stormforge edit&lt;/code&gt; command now launches an interactive editor&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;removed&#34;&gt;Removed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#removed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Optimize Pro functionality has been removed&lt;/li&gt;&#xA;&lt;li&gt;Performance Test functionality has been removed&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The &lt;code&gt;--selector&lt;/code&gt; argument is not ignored for tab completions&lt;/li&gt;&#xA;&lt;li&gt;Some commands mistakenly bypassed filtering requirements&lt;/li&gt;&#xA;&lt;li&gt;Flag and argument completions are more consistent&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.21.2</title>
				<link>/docs/releases/stormforge/previous/v2.21.2-agent/</link>
				<pubDate>Mon, 31 Mar 2025 14:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.21.2-agent/</guid>
				<description>&lt;h3 id=&#34;2.21.2-agent-fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#2.21.2-agent-fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Fixes an issue with hpa and pod reconciles could conflict and result in incomplete workload config.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;2.21.2-agent-changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#2.21.2-agent-changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Updated Dependencies&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;golang-jwt/jwt/v5&lt;/code&gt; to v5.2.2&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;argoproj/argo-rollouts&lt;/code&gt; to v1.8.2&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;rs/zerolog&lt;/code&gt; to v1.34.0&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;gramlabs/go-application&lt;/code&gt; to v0.0.99&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;gramlabs/stormforge-go&lt;/code&gt; to v4.7.6&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.21.1</title>
				<link>/docs/releases/stormforge/previous/v2.21.1-agent/</link>
				<pubDate>Thu, 20 Mar 2025 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.21.1-agent/</guid>
				<description>&lt;h3 id=&#34;v2.21.1-agent-added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.21.1-agent-added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Recommendations for Java workloads&lt;/strong&gt;&lt;br&gt;&#xA;You can now configure the Agent to generate Java maximum heap size recommendations for each Java container in a workload, in addition to requests and limits.&lt;/p&gt;&#xA;&lt;p&gt;The following settings have been added in support of this feature:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Support for the &lt;code&gt;runtime:java&lt;/code&gt; label selector when setting annotations.&lt;/p&gt;&#xA;&lt;p&gt;A best practice is to use the &lt;code&gt;RequestsAndLimits&lt;/code&gt; optimization policy for Java containers, which ensures that Optimize Live can implement the desired heap size. Example:&lt;/p&gt;&#xA;&lt;p&gt;&lt;code&gt;live.stormforge.io/containers.memory.optimization-policy: &amp;quot;balanced,runtime:java=reliability,container-a=savings&amp;quot;&lt;/code&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Annotations for defining heap size range and patch path details:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-yaml&#34; data-lang=&#34;yaml&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#ae81ff&#34;&gt;live.stormforge.io/containers.java.max-heap.min&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#ae81ff&#34;&gt;live.stormforge.io/containers.java.max-heap.max&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#ae81ff&#34;&gt;live.stormforge.io/containers.java.max-heap.patch-path&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#ae81ff&#34;&gt;live.stormforge.io/containers.java.max-heap.patch-format&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Applier version 2.7.1</title>
				<link>/docs/releases/stormforge/previous/v2.7.1-applier/</link>
				<pubDate>Thu, 20 Mar 2025 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.7.1-applier/</guid>
				<description>&lt;h3 id=&#34;v2.7.1-applier-added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.7.1-applier-added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;New optional Helm parameter &lt;code&gt;disableAutomaticRollback&lt;/code&gt;: Default value is &lt;code&gt;false&lt;/code&gt;. Typically, automatic rollback is disabled only upon guidance from StormForge Support or when workloads frequently become unhealthy.&lt;br&gt;&#xA;This parameter replaces the setting of &lt;code&gt;STORMFORGE_SKIP_ROLLBACK=true&lt;/code&gt; as an &lt;code&gt;additionalEnvVar&lt;/code&gt;.&lt;/li&gt;&#xA;&lt;li&gt;RBAC permissions are now granted by default for Argo Rollouts, eliminating the need for additonal manual configuration.&lt;/li&gt;&#xA;&lt;li&gt;New optional Helm parameter &lt;code&gt;additionalEnvVars&lt;/code&gt; replaces &lt;code&gt;extraEnvVars&lt;/code&gt;, which is now deprecated. Existing extraEnvVars settings are respected and no changes are required.&lt;br&gt;&#xA;In the Agent, this parameter was deprecated in version &lt;a href=&#34;/docs/releases/stormforge/#v2.20.2-agent-added&#34;&gt;2.20.2&lt;/a&gt;.&lt;/li&gt;&#xA;&lt;li&gt;New Helm parameters enable you to specify additional volumes and mounts to add to pods (for example, to mount custom CA bundles as part of using a transparent proxy):&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;additionalVolumes&lt;/code&gt; configures additional volumes that will be added to all pods&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;additionalVolumeMounts&lt;/code&gt; configures additional volume mounts that will be added to all containers&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.7.1-applier-changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.7.1-applier-changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependency updates:&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;evanphx/json-patch/v5&lt;/code&gt; to v5.9.11&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://pkg.go.dev/gomodules.xyz/jsonpatch/v2&#34;&gt;&lt;code&gt;gomodules.xyz/jsonpatch/v2&lt;/code&gt;&lt;/a&gt; to v2.5.0&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;go-jose/v4&lt;/code&gt; to v4.0.5&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;kubernetes&lt;/code&gt; libraries to v0.32.3&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;controller-runtime&lt;/code&gt; to v0.20.3&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;x/net&lt;/code&gt; to v0.36.0&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;structured-merge-diff&lt;/code&gt; to v4.6.0&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;gramLabs/stormforge-agent&lt;/code&gt; to v2.21.1&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;gramLabs/go-application&lt;/code&gt; to v0.0.98&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;gramLabs/stormforge-go&lt;/code&gt; to v4.7.5&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.20.2</title>
				<link>/docs/releases/stormforge/previous/v2.20.2-agent/</link>
				<pubDate>Wed, 05 Mar 2025 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.20.2-agent/</guid>
				<description>&lt;h3 id=&#34;v2.20.2-agent-added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.20.2-agent-added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;New optional Helm parameter &lt;code&gt;additionalEnvVars&lt;/code&gt; replaces &lt;code&gt;extraEnvVars&lt;/code&gt;, which is now deprecated. See &lt;a href=&#34;#v2.20.2-agent-deprecated&#34;&gt;Deprecated&lt;/a&gt; below.&lt;/li&gt;&#xA;&lt;li&gt;New &lt;code&gt;sf_node_labels&lt;/code&gt; metric and improved handling of node resource usage metrics.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;For the complete list metrics that StormForge collects, see the &lt;a href=&#34;/docs/reference/faq-security/#metrics&#34;&gt;Security FAQ&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;h3 id=&#34;v2.20.2-agent-changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.20.2-agent-changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Updated dependencies:&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;prometheus&lt;/code&gt; to v3.2.1&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;prometheus&lt;/code&gt; libraries to v0.302.0&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;kubernetes&lt;/code&gt; libraries to v0.32.2&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;stormforge-go&lt;/code&gt; to v4.7.4&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;go-application&lt;/code&gt; to v0.0.97&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;cobra&lt;/code&gt; to v1.9.1&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;client_golang&lt;/code&gt; to v1.21.1&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.20.2-agent-fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.20.2-agent-fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Node controller metrics are now garbage collected.&lt;/li&gt;&#xA;&lt;li&gt;Fixed a typo in the Helm template.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.20.2-agent-security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.20.2-agent-security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Updated dependencies&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;go-jose/v4&lt;/code&gt; to v4.0.5&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;x/oauth2&lt;/code&gt; to v0.28.0&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.20.2-agent-deprecated&#34;&gt;Deprecated&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.20.2-agent-deprecated&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;extraEnvVars&lt;/code&gt; Helm parameter. Use &lt;code&gt;additionalEnvVars&lt;/code&gt; (see &lt;a href=&#34;#v2.20.2-agent-added&#34;&gt;Added&lt;/a&gt; above). Existing &lt;code&gt;extraEnvVars&lt;/code&gt; settings are respected and no changes are required.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.20.1</title>
				<link>/docs/releases/stormforge/previous/v2.20.1-agent/</link>
				<pubDate>Wed, 19 Feb 2025 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.20.1-agent/</guid>
				<description>&lt;h3 id=&#34;v2.20.1-agent-changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.20.1-agent-changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;All workload metrics are now enabled by default. For a complete list of metrics, see the &lt;a href=&#34;/docs/reference/faq-security/#metrics&#34;&gt;Security FAQ&lt;/a&gt;.&lt;/li&gt;&#xA;&lt;li&gt;Several noisy &lt;code&gt;INFO&lt;/code&gt;-log entries are now to &lt;code&gt;DEBUG&lt;/code&gt;-level log entries.&lt;/li&gt;&#xA;&lt;li&gt;Updated dependencies:&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;kubernetes&lt;/code&gt; to v0.34.2&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.20.1-agent-fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.20.1-agent-fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;We fixed the issue of missing metrics when workloads are configured with limits only and no requests.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.20.0</title>
				<link>/docs/releases/stormforge/previous/v2.20.0-agent/</link>
				<pubDate>Tue, 11 Feb 2025 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.20.0-agent/</guid>
				<description>&lt;h3 id=&#34;v2.20.0-agent-added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.20.0-agent-added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Node metrics collection is now enabled by default.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;New custom node metrics:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;sf_node_capacity_resources&lt;/code&gt;: The total amount of resources that a node has.&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;node_cpu_usage_seconds_total&lt;/code&gt;: Used in calculating the average cluster CPU utilization&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;node_memory_working_set_byes&lt;/code&gt;: Used in calculating the average cluster memory utilization&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;For a complete list of metrics, see the &lt;a href=&#34;/docs/reference/faq-security/#metrics&#34;&gt;Security FAQ&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.20.0-agent-changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.20.0-agent-changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Added &lt;code&gt;namespaces&lt;/code&gt; to &lt;code&gt;useViewRole&lt;/code&gt; in RBAC configuration.&lt;/li&gt;&#xA;&lt;li&gt;Updated dependencies:&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;spf13/pflag&lt;/code&gt; to v1.0.6&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;argo-rollouts&lt;/code&gt; to v1.8.0&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;stormforge-go&lt;/code&gt; to v4.7.2&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;x/oauth2&lt;/code&gt; to v0.26.0&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;terratest&lt;/code&gt; to v0.48.2&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;go-application&lt;/code&gt; to v0.0.95&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.20.0-agent-fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.20.0-agent-fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;We fixed the synchronization of workload configurations and HPA deletions.&lt;/li&gt;&#xA;&lt;li&gt;We fixed an issue with how DaemonSets were reconciled.&lt;/li&gt;&#xA;&lt;li&gt;We fixed an issue that prevented memory bump-ups from being applied immediately when configured to do so.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 5.1.13</title>
				<link>/docs/releases/stormforge-cli/v5.1.13/</link>
				<pubDate>Thu, 06 Feb 2025 17:21:19 +0000</pubDate>
				<guid>/docs/releases/stormforge-cli/v5.1.13/</guid>
				<description>&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Fixes an issue where &lt;code&gt;-o name&lt;/code&gt; was selected when a TTY isn&amp;rsquo;t available&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.19.1</title>
				<link>/docs/releases/stormforge/previous/v2.19.1-agent/</link>
				<pubDate>Tue, 28 Jan 2025 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.19.1-agent/</guid>
				<description>&lt;h3 id=&#34;v2.19.1-agent-changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.19.1-agent-changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;p&gt;Updated dependencies:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;prometheus&lt;/code&gt; library to v0.301.0&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;prometheus/common&lt;/code&gt; to v0.62.0&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;stormforge-go&lt;/code&gt; to v4.7.1&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;go-application&lt;/code&gt; to v0.0.94&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.19.1-agent-deprecated&#34;&gt;Deprecated&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.19.1-agent-deprecated&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Installing Prometheus 2.x via Helm is no longer supported.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.19.1-agent-fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.19.1-agent-fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;We fixed how the Agent handles jobs that have Jobs Completions set to &lt;code&gt;null&lt;/code&gt;.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.19.1-agent-security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.19.1-agent-security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Updated Prometheus container to v3.1.0 to fix &lt;a href=&#34;https://github.com/advisories/GHSA-v778-237x-gjrc/&#34;&gt;CVE-2024-45337&lt;/a&gt; in &lt;code&gt;x/crypto&lt;/code&gt;.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.19.0</title>
				<link>/docs/releases/stormforge/previous/v2.19.0-agent/</link>
				<pubDate>Thu, 23 Jan 2025 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.19.0-agent/</guid>
				<description>&lt;h3 id=&#34;v2.19.0-agent-added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.19.0-agent-added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;A new Helm parameter &lt;code&gt;priorityClassName&lt;/code&gt; enables scheduling and priority configurations to add to all pods.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.19.0-agent-fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.19.0-agent-fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Better HPA detection and deletion now prevent the Agent from attempting to patch a workload if its HPA has been deleted.&lt;/li&gt;&#xA;&lt;li&gt;Rate limiting now prevents the Agent from making more than one recommendation request in response to a workload OOM event.&lt;/li&gt;&#xA;&lt;li&gt;We fixed an issue with the Helm schema validation for OptimizationPolicy.&lt;/li&gt;&#xA;&lt;li&gt;We updated how the Agent handles invalid credentials.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Applier version 2.7.0</title>
				<link>/docs/releases/stormforge/previous/v2.7.0-applier/</link>
				<pubDate>Wed, 22 Jan 2025 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.7.0-applier/</guid>
				<description>&lt;h3 id=&#34;v2.7.0-applier-added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.7.0-applier-added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;New Helm parameter &lt;code&gt;priorityClassName&lt;/code&gt; enables scheduling and priority configurations to add to all pods&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.7.0-applier-fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.7.0-applier-fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Log message improvement and cleanup&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.7.0-applier-changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.7.0-applier-changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Safer recommendation rollback&lt;/strong&gt;&lt;br&gt;&#xA;The rollback operation now reverts only the changes made to fields managed by &lt;code&gt;stormforge&lt;/code&gt; at the time the patch was applied. Previously, in a rollback, &lt;em&gt;all&lt;/em&gt; changes made between when the recommendation was applied and when the rollback happens were lost.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.7.0-applier-security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.7.0-applier-security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;p&gt;Dependency updates:&lt;/p&gt;</description>
			</item>
			<item>
				<title>Version 5.1.12</title>
				<link>/docs/releases/stormforge-cli/v5.1.12/</link>
				<pubDate>Mon, 13 Jan 2025 18:00:30 +0000</pubDate>
				<guid>/docs/releases/stormforge-cli/v5.1.12/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependency updates&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.18.0</title>
				<link>/docs/releases/stormforge/previous/v2.18.0-agent/</link>
				<pubDate>Wed, 08 Jan 2025 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.18.0-agent/</guid>
				<description>&lt;h3 id=&#34;v2.18.0-agent-added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.18.0-agent-added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Support for adding volumes and mounts to pods&lt;/strong&gt;&lt;br&gt;&#xA;The following new Helm parameters enable you to specify additional volumes and mounts to add to pods (for example, to mount custom CA bundles as part of using a transparent proxy):&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;additionalVolumes&lt;/code&gt; configures additional volumes that will be added to all pods&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;additionalVolumeMounts&lt;/code&gt; configures additional volume mounts that will be added to all containers&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.18.0-agent-changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.18.0-agent-changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependency updates:&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;stormforge-go&lt;/code&gt; to v4.6.1&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;go-application&lt;/code&gt; to v0.0.93&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;keda/v2&lt;/code&gt; to v2.16.1&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;x/oauth2&lt;/code&gt; to v0.25.0&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;terratest&lt;/code&gt; to v0.48.1&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;controller-runtime&lt;/code&gt; to v0.19.4&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 5.1.11</title>
				<link>/docs/releases/stormforge-cli/v5.1.11/</link>
				<pubDate>Wed, 18 Dec 2024 20:31:43 +0000</pubDate>
				<guid>/docs/releases/stormforge-cli/v5.1.11/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependency updates&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Fix for empty values showing up as &amp;ldquo;&lt;nil&gt;&amp;rdquo;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 5.1.10</title>
				<link>/docs/releases/stormforge-cli/v5.1.10/</link>
				<pubDate>Mon, 16 Dec 2024 16:50:25 +0000</pubDate>
				<guid>/docs/releases/stormforge-cli/v5.1.10/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependency updates&lt;/li&gt;&#xA;&lt;li&gt;The Go Template output has improved support for Kubernetes quantities&lt;/li&gt;&#xA;&lt;li&gt;Recommendation output includes JVM max heap (if applicable)&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.17.0</title>
				<link>/docs/releases/stormforge/previous/v2.17.0-agent/</link>
				<pubDate>Thu, 12 Dec 2024 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.17.0-agent/</guid>
				<description>&lt;h3 id=&#34;v2.17.0-agent-added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.17.0-agent-added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Improved support for Argo Rollouts&lt;/strong&gt;&lt;br&gt;&#xA;Support for Argo Rollouts and built-in Kubernetes types is now equivalent.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.17.0-agent-changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.17.0-agent-changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependency updates:&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;controller-runtime&lt;/code&gt; to v0.19.3&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;kube-api&lt;/code&gt; libraries to v0.32.0&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;deckarep/golang-set&lt;/code&gt; to v2.7.0&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;prometheus/common&lt;/code&gt; to v0.61.0&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;crypto&lt;/code&gt; to v0.31.0&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;stormforge-go&lt;/code&gt; to v4.6.0&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;go-application&lt;/code&gt; to v0.0.90&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.17.0-agent-fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.17.0-agent-fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Boolean types are now parsed correctly during workload autodiscovery.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.16.1</title>
				<link>/docs/releases/stormforge/previous/v2.16.1-agent/</link>
				<pubDate>Wed, 20 Nov 2024 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.16.1-agent/</guid>
				<description>&lt;h3 id=&#34;v2.16.1-agent-added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.16.1-agent-added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Support for applying recommendations by using a mutating admission webhook&lt;/strong&gt;&lt;br&gt;&#xA;You can now configure Optimize Live to apply recommendations via a mutating admission webhook instead of the default patch method by setting the following annotation:&#xA;&lt;code&gt;live.stormforge.io/apply.method: DynamicAdmissionWebhook&lt;/code&gt;&lt;/p&gt;&#xA;&lt;p&gt;You can define the apply method at the cluster, namesapce, or workload level. For details, see &lt;a href=&#34;/docs/configure/settings/apply-settings/#apply-method&#34;&gt;Apply method&lt;/a&gt; in the Apply settings topic.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Note&lt;/strong&gt;: A cluster administrator must enable this feature via a Helm parameter when installing the Applier. Feature-specific namespace allow/deny lists can be configured to restrict webhook usage. For details, see &lt;a href=&#34;/docs/installation/applier-config/#webhook&#34;&gt;Enabling the DynamicAdmissionWebhook&lt;/a&gt; in Applier configuration help topic.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Support for memory bump-up in response to OOM Events&lt;/strong&gt;&lt;br&gt;&#xA;You can now configure Optimize Live to respond to OOM events with a temporary memory bump-up. You can define the min and max memory bump-up amount, as well as when to apply the bump-up.&lt;/p&gt;&#xA;&lt;p&gt;You can view OOM events on the OOM Events graph on the Reports page (&lt;a href=&#34;/docs/releases/stormforge/#UI-15Oct2024-added&#34;&gt;example graph&lt;/a&gt;)&lt;/p&gt;&#xA;&lt;p&gt;Memory bump-ups can be configured at the resourcetype level, as shown below:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-yaml&#34; data-lang=&#34;yaml&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#f92672&#34;&gt;live.stormforge.io/reliability.oom.memory-bump-up.apply-immediately&lt;/span&gt;: &lt;span style=&#34;color:#e6db74&#34;&gt;&amp;#34;Always,resource:daemonsets=Never&amp;#34;&lt;/span&gt;  &#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#f92672&#34;&gt;live.stormforge.io/reliability.oom.memory-bump-up.max&lt;/span&gt;: &lt;span style=&#34;color:#e6db74&#34;&gt;&amp;#34;300Mi&amp;#34;&lt;/span&gt;  &#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#f92672&#34;&gt;live.stormforge.io/reliability.oom.memory-bump-up.min&lt;/span&gt;: &lt;span style=&#34;color:#e6db74&#34;&gt;&amp;#34;50Mi,resource:deployments=40Mi,resource:daemonsets=0&amp;#34;&lt;/span&gt;  &#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#f92672&#34;&gt;live.stormforge.io/reliability.oom.memory-bump-up.percent&lt;/span&gt;: &lt;span style=&#34;color:#e6db74&#34;&gt;&amp;#34;15,resource:deployments=25,resource:daemonsets=0&amp;#34;&lt;/span&gt;  &#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#f92672&#34;&gt;live.stormforge.io/reliability.oom.memory-bump-up.period&lt;/span&gt;: &lt;span style=&#34;color:#e6db74&#34;&gt;&amp;#34;P2D,resource:deployments=P1D&amp;#34;&lt;/span&gt;  &#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;For details and examples, see the &lt;a href=&#34;/docs/configure/settings/reliability/&#34;&gt;Reliability response&lt;/a&gt; topic.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Applier version 2.6.0</title>
				<link>/docs/releases/stormforge/previous/v2.6.0-applier/</link>
				<pubDate>Wed, 20 Nov 2024 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.6.0-applier/</guid>
				<description>&lt;h3 id=&#34;v2.6.0-applier-added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.6.0-applier-added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Support for optional mutating admission webhook&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.6.0-applier-fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.6.0-applier-fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Better handling of JSON type patches&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.6.0-applier-changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.6.0-applier-changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;p&gt;Upgraded dependencies to the following versions:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;kubernetes&lt;/code&gt; dependencies to v0.31.1&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;go-application&lt;/code&gt; to v0.0.89&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;stormforge-go&lt;/code&gt; to v4.5.1&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;stormforge-agent&lt;/code&gt; to v2.16.1&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.6.0-applier-security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.6.0-applier-security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;p&gt;Upgraded packages include:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;go&lt;/code&gt; to v1.23.3&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;prometheus&lt;/code&gt; to v0.60.1&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;prometheus go&lt;/code&gt; client to v1.20.5&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;golang.org/x/oauth2&lt;/code&gt; to v0.24.0&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.15.3</title>
				<link>/docs/releases/stormforge/previous/v2.15.3-agent/</link>
				<pubDate>Thu, 31 Oct 2024 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.15.3-agent/</guid>
				<description>&lt;h3 id=&#34;v2.15.3-agent-changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.15.3-agent-changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Updated &lt;code&gt;prometheus/common&lt;/code&gt; to v0.60.1&lt;/li&gt;&#xA;&lt;li&gt;Updated &lt;code&gt;controller-runtime&lt;/code&gt; to 0.19.1&lt;/li&gt;&#xA;&lt;li&gt;Reduced the wait timeout for RBAC (to minimize pod blocking operation) from 20s to 5s&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.15.3-agent-fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.15.3-agent-fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;We fixed a problem that was causing the &lt;code&gt;sf_workload_pod_container_resource_requests&lt;/code&gt; metric to drop intermittently, resulting in &lt;code&gt;No containers metrics observed for this workload in the last 10 minutes&lt;/code&gt; errors and incomplete graph lines.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.15.2</title>
				<link>/docs/releases/stormforge/previous/v2.15.2-agent/</link>
				<pubDate>Wed, 23 Oct 2024 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.15.2-agent/</guid>
				<description>&lt;h3 id=&#34;v2.15.2-agent-changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.15.2-agent-changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Upgraded Prometheus container to v2.55.0&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.15.2-agent-fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.15.2-agent-fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;We now correctly detect HPAs on clusters with &lt;a href=&#34;https://opentelemetry.io/docs/kubernetes/operator/&#34;&gt;open telemetry operator&lt;/a&gt; configured with autoscaling.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 5.1.9</title>
				<link>/docs/releases/stormforge-cli/v5.1.9/</link>
				<pubDate>Thu, 17 Oct 2024 20:48:08 +0000</pubDate>
				<guid>/docs/releases/stormforge-cli/v5.1.9/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependency updates&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The workload patches can be read from stdin&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.15.1</title>
				<link>/docs/releases/stormforge/previous/v2.15.1-agent/</link>
				<pubDate>Tue, 01 Oct 2024 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.15.1-agent/</guid>
				<description>&lt;h3 id=&#34;v2.15.1-agent-changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.15.1-agent-changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;p&gt;Dependency updates:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;kubernetes&lt;/code&gt; libraries to 0.31.1&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;stormforge-go&lt;/code&gt; to 4.3.3&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;go-application&lt;/code&gt; to 0.0.86&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;prometheus/client_golang&lt;/code&gt; to 1.20.4&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;prometheus/common&lt;/code&gt; to 0.60.0&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;terratest&lt;/code&gt; to 0.47.2&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.15.1-agent-fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.15.1-agent-fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Fixed the issue of the Agent not cleaning up stale metrics for deleted containers.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 5.1.8</title>
				<link>/docs/releases/stormforge-cli/v5.1.8/</link>
				<pubDate>Wed, 18 Sep 2024 17:51:05 +0000</pubDate>
				<guid>/docs/releases/stormforge-cli/v5.1.8/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependency upgrades&lt;/li&gt;&#xA;&lt;li&gt;Fixed an issue where some authorization scopes were not being requested&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.15.0</title>
				<link>/docs/releases/stormforge/previous/v2.15.0-agent/</link>
				<pubDate>Tue, 10 Sep 2024 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.15.0-agent/</guid>
				<description>&lt;h3 id=&#34;v2.15.0-agent-added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.15.0-agent-added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Configurable learning period&lt;/strong&gt;&lt;br&gt;&#xA;You can now configure the duration of the &lt;em&gt;learning period&lt;/em&gt; during which Optimize Live observes a new workload before providing recommendations that can be auto-deployed (default value is &lt;code&gt;P7D&lt;/code&gt;, 7 days). For example, a shorter learning period is helpful for branch-based deploys.&lt;/p&gt;&#xA;&lt;p&gt;To adjust the learning period, you can set a &lt;a href=&#34;/docs/configure/cluster-defaults/&#34;&gt;cluster&lt;/a&gt;, &lt;a href=&#34;/docs/configure/annotate-namespaces/&#34;&gt;namespace&lt;/a&gt;, or &lt;a href=&#34;/docs/configure/annotate-workloads/&#34;&gt;workload&lt;/a&gt; default by setting the &lt;code&gt;live.stormforge.io/learning-period&lt;/code&gt; annotation. You can view this setting on the &lt;strong&gt;Settings&lt;/strong&gt; &amp;gt; &lt;strong&gt;Schedule&lt;/strong&gt; section of workload&amp;rsquo;s details page.&lt;/p&gt;&#xA;&lt;p&gt;The value for this setting must be &lt;a href=&#34;https://en.wikipedia.org/wiki/ISO_8601#Durations&#34;&gt;ISO-8601&lt;/a&gt; compliant. Examples:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;P1D&lt;/code&gt;: 1 day (minimum valid value)&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;PT12H&lt;/code&gt;: 12 Hours&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.14.0</title>
				<link>/docs/releases/stormforge/previous/v2.14.0-agent/</link>
				<pubDate>Thu, 22 Aug 2024 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.14.0-agent/</guid>
				<description>&lt;h3 id=&#34;v2.14.0-agent-added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.14.0-agent-added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;CronJob controller now reconciles inactive Cronjob workload types&lt;/li&gt;&#xA;&lt;li&gt;Support for CronJob, ScheduledSparkApplication, and GitHubARC types.&lt;br&gt;&#xA;To enable discovery and recommendations for these types, set the corresponding featureGate to &lt;code&gt;true&lt;/code&gt; either via Helm or a &lt;code&gt;values.yaml&lt;/code&gt; file as shown in this excerpt:&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-yaml&#34; data-lang=&#34;yaml&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#f92672&#34;&gt;featureGates&lt;/span&gt;:&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    &lt;span style=&#34;color:#f92672&#34;&gt;optimizeCronJobs&lt;/span&gt;: &lt;span style=&#34;color:#66d9ef&#34;&gt;true&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    &lt;span style=&#34;color:#f92672&#34;&gt;optimizeSparkOperator&lt;/span&gt;: &lt;span style=&#34;color:#66d9ef&#34;&gt;true&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    &lt;span style=&#34;color:#f92672&#34;&gt;optimizeGithubARC&lt;/span&gt;: &lt;span style=&#34;color:#66d9ef&#34;&gt;true&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.14.0-agent-changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.14.0-agent-changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Zerolog is the standard logging mechanism. Logging arguments are now &lt;code&gt;--log-level=debug&lt;/code&gt; and &lt;code&gt;--log-level=trace&lt;/code&gt;, replacing &lt;code&gt;--v=&amp;lt;level&amp;gt;&lt;/code&gt;.&lt;/li&gt;&#xA;&lt;li&gt;Added a name to the &lt;code&gt;workload-agent&lt;/code&gt; metrics port&lt;/li&gt;&#xA;&lt;li&gt;Updated &lt;code&gt;go-application&lt;/code&gt; to v0.0.82&lt;/li&gt;&#xA;&lt;li&gt;Updated &lt;code&gt;keda&lt;/code&gt; to v2.15.1&lt;/li&gt;&#xA;&lt;li&gt;Updated &lt;code&gt;structured-logging&lt;/code&gt; to v0.0.5&lt;/li&gt;&#xA;&lt;li&gt;Updated &lt;code&gt;stormforge-go&lt;/code&gt; to v4.2.0&lt;/li&gt;&#xA;&lt;li&gt;Updated &lt;code&gt;controller-runtime&lt;/code&gt; to v0.19.0&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;2.14.0-agent-removed&#34;&gt;Removed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#2.14.0-agent-removed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Log arguments &lt;code&gt;--v=&amp;lt;level&amp;gt;&lt;/code&gt;. See &lt;a href=&#34;#v2.14.0-agent-changed&#34;&gt;Changed&lt;/a&gt; above for the new arguments.&lt;/li&gt;&#xA;&lt;li&gt;The &lt;code&gt;workload.workloadResources&lt;/code&gt; Helm parameter used for enabling the workloadResource types has been replaced as described in the &lt;a href=&#34;#v2.14.0-agent-added&#34;&gt;Added&lt;/a&gt; section above.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.14.0-agent-fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.14.0-agent-fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;CronJobs: Completed pods are now garbage collected on Optimize Live metrics&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.14.0-agent-security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.14.0-agent-security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Updated &lt;code&gt;grpc&lt;/code&gt; to v1.64.1&lt;/li&gt;&#xA;&lt;li&gt;Updated &lt;code&gt;golang.org/x/oauth2&lt;/code&gt; to v0.22.0&lt;/li&gt;&#xA;&lt;li&gt;Upgraded the Prometheus agent to v2.54.0 to address low- and medium-severity CVEs&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Applier version 2.5.0</title>
				<link>/docs/releases/stormforge/previous/v2.5.0-applier/</link>
				<pubDate>Fri, 02 Aug 2024 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.5.0-applier/</guid>
				<description>&lt;h3 id=&#34;v2.5.0-applier-changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.5.0-applier-changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Validation rollout of patches and persisting the state of the recommendation is now more reliable:&#xA;&lt;ul&gt;&#xA;&lt;li&gt;After patches are applied, the recommendation status is either &lt;code&gt;ApplierSuccess&lt;/code&gt; or &lt;code&gt;ApplierFailed&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;When validating the rollout and checking workload health, the validation status is either &lt;code&gt;RolloutValidationSuccess&lt;/code&gt;, &lt;code&gt;RolloutValidationTimeout&lt;/code&gt; or &lt;code&gt;RolloutValidationFailure&lt;/code&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Changed the rollout validation timeout to &lt;code&gt;5m&lt;/code&gt; (5 minutes) from &lt;code&gt;30m&lt;/code&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.5.0-applier-security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.5.0-applier-security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Multiple packages upgraded, including &lt;code&gt;go&lt;/code&gt; package upgraded to 1.22.5&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://github.com/advisories/GHSA-m5vv-6r4h-3vj9&#34;&gt;GHSA-m5vv-6r4h-3vj9&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://github.com/advisories/GHSA-v6v8-xj6m-xwqh&#34;&gt;GHSA-v6v8-xj6m-xwqh&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://github.com/advisories/GHSA-xr7q-jx4m-x55m&#34;&gt;GHSA-xr7q-jx4m-x55m&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.13.0</title>
				<link>/docs/releases/stormforge/previous/v2.13.0-agent/</link>
				<pubDate>Tue, 23 Jul 2024 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.13.0-agent/</guid>
				<description>&lt;h3 id=&#34;v2.13.0-agent-added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.13.0-agent-added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Adds 10 minute &amp;ldquo;Learning Period&amp;rdquo; to the Agent sidecar in the Metrics-forwarder pod for faster metrics scraping after init.&lt;/li&gt;&#xA;&lt;li&gt;Adds a workload metric &lt;code&gt;sf_workload_terminated_total&lt;/code&gt; that tracks the count of workload termination events. Initially will only track &lt;code&gt;OOMKilled&lt;/code&gt; events.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.13.0-agent-changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.13.0-agent-changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Added a default value to authorization.issuer to the Helm chart.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.13.0-agent-removed&#34;&gt;Removed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.13.0-agent-removed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Cadvisor metric &lt;code&gt;container_oom_events_total&lt;/code&gt; no longer collected.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.13.0-agent-fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.13.0-agent-fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Workload container order was not being preserved.&lt;/li&gt;&#xA;&lt;li&gt;Potential contention between DeletionPredicate and Reconcile.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 5.1.7</title>
				<link>/docs/releases/stormforge-cli/v5.1.7/</link>
				<pubDate>Tue, 16 Jul 2024 15:52:11 +0000</pubDate>
				<guid>/docs/releases/stormforge-cli/v5.1.7/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependency updates&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Fixes an issue where the &lt;code&gt;stormforge auth list&lt;/code&gt; results could be truncated&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.12.2</title>
				<link>/docs/releases/stormforge/previous/v2.12.2-agent/</link>
				<pubDate>Mon, 15 Jul 2024 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.12.2-agent/</guid>
				<description>&lt;h3 id=&#34;v2.12.2-agent-security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.12.2-agent-security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Go upgraded from 1.22.4 to 1.22.5 to address &lt;a href=&#34;https://pkg.go.dev/vuln/GO-2024-2963&#34;&gt;CVE GO-2024-2963&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;Addressed several CVEs related to the Prometheus container image (upgraded from 2.52.0 to 2.53.1)&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.12.1</title>
				<link>/docs/releases/stormforge/previous/v2.12.1-agent/</link>
				<pubDate>Tue, 02 Jul 2024 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.12.1-agent/</guid>
				<description>&lt;h3 id=&#34;v2.12.1-agent-added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.12.1-agent-added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The strings &lt;code&gt;&amp;quot;Enabled&amp;quot;&lt;/code&gt; and &lt;code&gt;&amp;quot;Disabled&amp;quot;&lt;/code&gt; are now accepted for the &lt;code&gt;live.stormforge.io/auto-deploy&lt;/code&gt; annotation, in addition to the existing values (&lt;code&gt;&amp;quot;true&amp;quot;&lt;/code&gt; and &lt;code&gt;&amp;quot;false&amp;quot;&lt;/code&gt;).&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.12.1-agent-changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.12.1-agent-changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;HPAs owned by Flagger are now supported (&lt;code&gt;patchTarget&lt;/code&gt; is a KEDA ScaledObject).&lt;/li&gt;&#xA;&lt;li&gt;If the HPA &lt;code&gt;patchTarget&lt;/code&gt; is not detected, &lt;code&gt;patchTarget&lt;/code&gt; is set to the HPA itself.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.12.1-agent-fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.12.1-agent-fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;HPA settings are no longer silently ignored when an HPA is owned by a ScaledObject other than KEDA.&lt;/li&gt;&#xA;&lt;li&gt;HPA objects with &lt;code&gt;.spec&lt;/code&gt; changes now update HPA values.&lt;/li&gt;&#xA;&lt;li&gt;ReplicaSets that have 0 pods are now reported correctly.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 5.1.6</title>
				<link>/docs/releases/stormforge-cli/v5.1.6/</link>
				<pubDate>Wed, 26 Jun 2024 19:32:20 +0000</pubDate>
				<guid>/docs/releases/stormforge-cli/v5.1.6/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependency upgrades&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.11.0</title>
				<link>/docs/releases/stormforge/previous/v2.11.0-agent/</link>
				<pubDate>Thu, 13 Jun 2024 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.11.0-agent/</guid>
				<description>&lt;h3 id=&#34;v2.11.0-agent-added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.11.0-agent-added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;New default container optimization policy&lt;/strong&gt;&lt;br&gt;&#xA;We added a &lt;code&gt;RequestsRaiseLimitsIfNeeded&lt;/code&gt; container optimization policy: Requests are always optimized; limits are optimized only if they already exist. If an existing limit is lower than what Optimize Live recommends, the limit is raised to Optimize Live’s recommended limit value.&lt;/p&gt;&#xA;&lt;p&gt;With this policy, limits are not lowered if they already exist, nor are they added if they don&amp;rsquo;t exist.&lt;/p&gt;&#xA;&lt;p&gt;Note: The default optimization policy is still &lt;code&gt;RequestsOnly&lt;/code&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Use the following annotation values (for details, see the &lt;a href=&#34;/docs/configure/settings/cpu-and-memory/#opt-policy&#34;&gt;product docs&lt;/a&gt;):&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;live.stormforge.io/containers.cpu.optimization-policy: &amp;#34;RequestsRaiseLimitsIfNeeded&amp;#34;&#xA;live.stormforge.io/containers.memory.optimization-policy: &amp;#34;RequestsRaiseLimitsIfNeeded&amp;#34;&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;PatchPath annotations&lt;/strong&gt;&lt;br&gt;&#xA;You can now use the following annotations to map a container resource value from a recommendation to where it belongs in the &lt;code&gt;patchTarget&lt;/code&gt;:&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;live.stormforge.io/containers.memory.limits.patch-path&#xA;live.stormforge.io/containers.memory.requests.patch-path&#xA;live.stormforge.io/containers.cpu.limits.patch-path&#xA;live.stormforge.io/containers.cpu.requests.patch-path&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 5.1.5</title>
				<link>/docs/releases/stormforge-cli/v5.1.5/</link>
				<pubDate>Fri, 24 May 2024 16:28:42 +0000</pubDate>
				<guid>/docs/releases/stormforge-cli/v5.1.5/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependency upgrades&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Built using Go 1.22.3 to address &lt;a href=&#34;https://nvd.nist.gov/vuln/detail/CVE-2024-24788&#34;&gt;CVE-2024-24788&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.10.8</title>
				<link>/docs/releases/stormforge/previous/v2.10.8-agent/</link>
				<pubDate>Thu, 23 May 2024 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.10.8-agent/</guid>
				<description>&lt;h3 id=&#34;v2.10.8-agent-fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.10.8-agent-fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The StormForge Agent no longer crashes when it cannot find deleted custom resources from an installed package.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.10.7</title>
				<link>/docs/releases/stormforge/previous/v2.10.7-agent/</link>
				<pubDate>Fri, 17 May 2024 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.10.7-agent/</guid>
				<description>&lt;h3 id=&#34;v2.10.7-agent-fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.10.7-agent-fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;We fixed the regex validation of hashed cron expressions (such as &lt;code&gt;&amp;quot;H H(0-5) * * *&amp;quot;&lt;/code&gt;), which are used to set recommendation schedules. For more schedule examples, see the &lt;a href=&#34;/docs/configure/settings/schedule/&#34;&gt;Recommendation schedule&lt;/a&gt; topic in the product docs.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 5.1.4</title>
				<link>/docs/releases/stormforge-cli/v5.1.4/</link>
				<pubDate>Fri, 10 May 2024 15:47:51 +0000</pubDate>
				<guid>/docs/releases/stormforge-cli/v5.1.4/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Added missing workload impact data to the &lt;code&gt;stormforge get workload&lt;/code&gt; output&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.10.6</title>
				<link>/docs/releases/stormforge/previous/v2.10.6-agent/</link>
				<pubDate>Mon, 06 May 2024 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.10.6-agent/</guid>
				<description>&lt;h3 id=&#34;v2.10.6-agent-changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.10.6-agent-changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Updated &lt;code&gt;prometheus&lt;/code&gt; dependency to 0.53.0&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.10.6-agent-fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.10.6-agent-fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;patchPath&lt;/code&gt; and &lt;code&gt;patchFormat&lt;/code&gt; on the WorkloadOptimizer CRD are now processed accordingly.&lt;/li&gt;&#xA;&lt;li&gt;Updated example command lines on Helm README.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Applier version 2.4.0</title>
				<link>/docs/releases/stormforge/previous/v2.4.0-applier/</link>
				<pubDate>Fri, 03 May 2024 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.4.0-applier/</guid>
				<description>&lt;h3 id=&#34;v2.4.0-applier-added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.4.0-applier-added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Continuous reconciliation&lt;/strong&gt;&lt;br&gt;&#xA;You can now configure the StormForge Applier to continuously reconcile drift, ensuring that the latest recommended settings are always maintained on a workload. See the new Helm configuration options below.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;code&gt;reconciliation.mode&lt;/code&gt;: &lt;code&gt;EventBased&lt;/code&gt; (default value) maintains the existing Applier behavior of patching workloads only when new recommendations are ready. &lt;code&gt;Continuous&lt;/code&gt; enables continuous reconciliation.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;code&gt;reconciliation.conflictingManagers: [value1,value2]&lt;/code&gt;: Used in conjunction with &lt;code&gt;mode: Continuous&lt;/code&gt;. The Applier cannot reconcile the desired state for fields owned by conflicting managers.&lt;/p&gt;&#xA;&lt;p&gt;Use the following Helm values in a YAML file when you install or update the Applier:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-yaml&#34; data-lang=&#34;yaml&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#f92672&#34;&gt;reconciliation&lt;/span&gt;:&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt; &lt;span style=&#34;color:#f92672&#34;&gt;mode&lt;/span&gt;: &lt;span style=&#34;color:#ae81ff&#34;&gt;Continuous&lt;/span&gt; &lt;span style=&#34;color:#75715e&#34;&gt;# default is `EventBased`&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt; &lt;span style=&#34;color:#75715e&#34;&gt;# List the field managers that conflict with the Applier;&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt; &lt;span style=&#34;color:#75715e&#34;&gt;# Fields managed by a conflicting field manager cannot be reconciled.&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt; &lt;span style=&#34;color:#f92672&#34;&gt;conflictingManagers&lt;/span&gt;: []&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 5.1.3</title>
				<link>/docs/releases/stormforge-cli/v5.1.3/</link>
				<pubDate>Mon, 22 Apr 2024 15:12:44 +0000</pubDate>
				<guid>/docs/releases/stormforge-cli/v5.1.3/</guid>
				<description>&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;When creating auto-deployed recommendations, you can now include a &lt;code&gt;--wait&lt;/code&gt; flag and corresponding &lt;code&gt;--timeout&lt;/code&gt; flag to delay applying the recommendation&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Workload CSV numeric values are rendered at a fixed precision&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The &lt;code&gt;stormforge apply&lt;/code&gt; command now correctly reapplies recommendations&lt;/li&gt;&#xA;&lt;li&gt;Sort keys are not silently ignored&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.10.5</title>
				<link>/docs/releases/stormforge/previous/v2.10.5-agent/</link>
				<pubDate>Fri, 19 Apr 2024 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.10.5-agent/</guid>
				<description>&lt;h3 id=&#34;v2.10.5-agent-added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.10.5-agent-added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Added network policies to ensure StormForge pods can communicate with each other now that the &lt;code&gt;workload-agent&lt;/code&gt; and &lt;code&gt;prometheus&lt;/code&gt; containers have been separated into their own pods.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.10.5-agent-changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.10.5-agent-changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Updated &lt;code&gt;controller-runtime&lt;/code&gt; to 0.17.3&lt;/li&gt;&#xA;&lt;li&gt;Updated &lt;code&gt;kubernetes&lt;/code&gt; dependencies to 0.17.3&lt;/li&gt;&#xA;&lt;li&gt;Updated &lt;code&gt;stormforge-go&lt;/code&gt; to 3.9.2&lt;/li&gt;&#xA;&lt;li&gt;Updated &lt;code&gt;prometheus&lt;/code&gt; dependency to 0.51.3&lt;/li&gt;&#xA;&lt;li&gt;Updated &lt;code&gt;uber/zap&lt;/code&gt; to 1.27.0&lt;/li&gt;&#xA;&lt;li&gt;Updated &lt;code&gt;stretchr/testify&lt;/code&gt; to 1.9.0&lt;/li&gt;&#xA;&lt;li&gt;Updated &lt;code&gt;kubernetes&lt;/code&gt; group to 0.29.4&lt;/li&gt;&#xA;&lt;li&gt;Updated &lt;code&gt;jackc/pgx/v5&lt;/code&gt; to 5.5.4&lt;/li&gt;&#xA;&lt;li&gt;Removed &lt;code&gt;kedacore&lt;/code&gt; 2.13.0&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.10.5-agent-fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.10.5-agent-fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;We added code to ensure that the &lt;code&gt;cluster_name&lt;/code&gt; label in the ENV secrets file is the source of truth for the cluster name.&lt;/li&gt;&#xA;&lt;li&gt;We fixed the problem of ReplicaSets being incorrectly created as workloads when owned by Argo rollouts.&lt;/li&gt;&#xA;&lt;li&gt;We fixed the bug that caused the &lt;code&gt;Failed to watch *v1.Secret&lt;/code&gt; error, which occurred when the Agent requested access to secrets in order to parse certain KEDA ScaledObjects, depending on the configuration.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.10.5-agent-security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.10.5-agent-security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Updated Prometheus container image to v2.51.0&lt;/li&gt;&#xA;&lt;li&gt;Updated &lt;code&gt;go-jose/v3&lt;/code&gt; to 3.0.3&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 5.1.2</title>
				<link>/docs/releases/stormforge-cli/v5.1.2/</link>
				<pubDate>Thu, 14 Mar 2024 19:24:07 +0000</pubDate>
				<guid>/docs/releases/stormforge-cli/v5.1.2/</guid>
				<description>&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The &lt;code&gt;get&lt;/code&gt; commands now support limited client-side filtering using Kubernetes field selectors via the &lt;code&gt;--field-selector&lt;/code&gt; option&lt;/li&gt;&#xA;&lt;li&gt;The &lt;code&gt;get workloads&lt;/code&gt; command now has a &lt;code&gt;--full-fetch&lt;/code&gt; option to force fetching all data from the API (note: this might take extra time to run)&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The CSV columns named &lt;code&gt;auto-deploy&lt;/code&gt; and &lt;code&gt;hpa-enabled&lt;/code&gt; are now named &lt;code&gt;auto_deploy&lt;/code&gt; and &lt;code&gt;hpa_enabled&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;The &lt;code&gt;get workloads&lt;/code&gt; command now shows &amp;ldquo;UNAVAILABLE&amp;rdquo; for values that were not fetched from the API&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 5.1.1</title>
				<link>/docs/releases/stormforge-cli/v5.1.1/</link>
				<pubDate>Tue, 12 Mar 2024 16:28:42 +0000</pubDate>
				<guid>/docs/releases/stormforge-cli/v5.1.1/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Added &lt;code&gt;schedule&lt;/code&gt;, &lt;code&gt;auto-deploy&lt;/code&gt;, and &lt;code&gt;hpa-enabled&lt;/code&gt; columns to the workload CSV output&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Updated go-jose to address &lt;a href=&#34;https://nvd.nist.gov/vuln/detail/CVE-2024-28180&#34;&gt;CVE-2024-28180&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Applier version 2.3.0</title>
				<link>/docs/releases/stormforge/previous/v2.3.0-applier/</link>
				<pubDate>Sat, 09 Mar 2024 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.3.0-applier/</guid>
				<description>&lt;h3 id=&#34;v2.3.0-applier-added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.3.0-applier-added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Continuously enforce the latest recommendation after workload updates&lt;/strong&gt;&lt;br&gt;&#xA;You can now configure Optimize Live to detect changes to workload requests or limits and then automatically reapply the latest recommendation. This ensures the workload remains optimized.&lt;/p&gt;&#xA;&lt;p&gt;By default, Optimize Live does &lt;strong&gt;not&lt;/strong&gt; reapply recommendations after such changes.&lt;/p&gt;&#xA;&lt;p&gt;To continuously enforce the latest recommendation, do one of the following when you install the Applier:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;In your Helm &lt;code&gt;values.yaml&lt;/code&gt; file, set &lt;code&gt;enforce: true&lt;/code&gt;.&lt;/li&gt;&#xA;&lt;li&gt;In the &lt;code&gt;helm install&lt;/code&gt; command, include &lt;code&gt;--set enforce=true&lt;/code&gt;.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;cr&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Define which CD tools&amp;rsquo; changes do not trigger reapplying a recommendation&lt;/strong&gt;&lt;br&gt;&#xA;If you set &lt;code&gt;enforce&lt;/code&gt; to &lt;code&gt;true&lt;/code&gt; as described above, you can also define which continuous delivery tools&amp;rsquo; changes (for example, changes by Argo CD, Flux) do not trigger reapplying a recommendation. If an exempt manager changes a workload&amp;rsquo;s requests or limits, Optimize Live will &lt;strong&gt;not&lt;/strong&gt; reapply the latest recommendation.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Version 5.1.0</title>
				<link>/docs/releases/stormforge-cli/v5.1.0/</link>
				<pubDate>Fri, 01 Mar 2024 19:15:54 +0000</pubDate>
				<guid>/docs/releases/stormforge-cli/v5.1.0/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Optimize Pro commands are now hidden&lt;/li&gt;&#xA;&lt;li&gt;The &lt;code&gt;stormforge patch&lt;/code&gt; command supports multiple recommendations&lt;/li&gt;&#xA;&lt;li&gt;Workload CSV output includes &lt;code&gt;replicas&lt;/code&gt; and &lt;code&gt;optimization_score&lt;/code&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;removed&#34;&gt;Removed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#removed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The &lt;code&gt;stormforge run&lt;/code&gt; command has been removed&lt;/li&gt;&#xA;&lt;li&gt;The &lt;code&gt;stormforge edit workload label&lt;/code&gt; command has been removed. Use &lt;code&gt;stormforge edit workload --set-label&lt;/code&gt; instead.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The &lt;code&gt;Deleted&lt;/code&gt; value is no longer suggested for &lt;code&gt;--state&lt;/code&gt; flags&lt;/li&gt;&#xA;&lt;li&gt;Create recommendation failures are properly reported&lt;/li&gt;&#xA;&lt;li&gt;Allow recommendations to be sorted by timestamp&lt;/li&gt;&#xA;&lt;li&gt;The &lt;code&gt;apply&lt;/code&gt; command now prevents empty filters&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Switched container image base from Alpine to Distroless&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.10.4</title>
				<link>/docs/releases/stormforge/previous/v2.10.4-agent/</link>
				<pubDate>Thu, 15 Feb 2024 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.10.4-agent/</guid>
				<description>&lt;h3 id=&#34;v2.10.4-agent-changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.10.4-agent-changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;To improve performance, the &lt;code&gt;workload-agent&lt;/code&gt; and &lt;code&gt;prometheus&lt;/code&gt; containers now run in their own pods.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.10.4-agent-fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.10.4-agent-fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;We fixed a bug in how we reconcile workload annotations. You’ll now see your updated configurations in the UI.&lt;/li&gt;&#xA;&lt;li&gt;We removed &lt;code&gt;cluster_name&lt;/code&gt; actual values from the &lt;code&gt;prometheus&lt;/code&gt; ConfigMap and now set the cluster name from the secret to prevent a cluster name mismatch.&lt;/li&gt;&#xA;&lt;li&gt;We fixed the validation of CPU and memory optimization goals to allow capitalized values (&lt;code&gt;Savings&lt;/code&gt;, &lt;code&gt;Balanced&lt;/code&gt;, &lt;code&gt;Reliability&lt;/code&gt;).&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.10.4-agent-dependencies&#34;&gt;Dependencies&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.10.4-agent-dependencies&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Prometheus agent upgraded to version 2.49.1&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;prometheus/common&lt;/code&gt; upgraded to 0.47.0&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;controller-runtime&lt;/code&gt; upgraded to 0.17.1&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;stormforge-go&lt;/code&gt; upgraded to 3.8.6&lt;/li&gt;&#xA;&lt;li&gt;Kubernetes API dependencies upgraded to 0.29.2&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.10.4-agent-security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.10.4-agent-security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The &lt;code&gt;workload-agent&lt;/code&gt; container now addresses &lt;a href=&#34;https://nvd.nist.gov/vuln/detail/cve-2020-8911&#34;&gt;CVE-2020-8911&lt;/a&gt; and &lt;a href=&#34;https://nvd.nist.gov/vuln/detail/cve-2020-8912&#34;&gt;CVE-2020-8912&lt;/a&gt; with the upgrade of &lt;code&gt;prometheus&lt;/code&gt; Go module to version 0.49.1.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.10.3</title>
				<link>/docs/releases/stormforge/previous/v2.10.3-agent/</link>
				<pubDate>Thu, 18 Jan 2024 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.10.3-agent/</guid>
				<description>&lt;h3 id=&#34;v2.10.3-agent-added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.10.3-agent-added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Support for workloads with names that exceed 47 characters&lt;/strong&gt;&lt;br&gt;&#xA;Optimize Live can now optimize workloads that have names that exceed 47 characters. Previously for such workloads, Optimize Live showed this error: &lt;code&gt;&amp;quot;No container metrics observed for this workload in the last 10 minutes.&amp;quot;&lt;/code&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.10.3-agent-fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.10.3-agent-fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Schedule annotations are now created consistently&lt;/strong&gt;&lt;br&gt;&#xA;We fixed a regression in which workloads with annotations were created without the &lt;code&gt;schedule&lt;/code&gt; value.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.10.2</title>
				<link>/docs/releases/stormforge/previous/v2.10.2-agent/</link>
				<pubDate>Tue, 16 Jan 2024 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.10.2-agent/</guid>
				<description>&lt;p&gt;This release consists of internal improvements that build on version 2.10.1 of the Agent.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Agent version 2.10.1</title>
				<link>/docs/releases/stormforge/previous/v2.10.1-agent/</link>
				<pubDate>Thu, 11 Jan 2024 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.10.1-agent/</guid>
				<description>&lt;h3 id=&#34;v2.10.1-agent-added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.10.1-agent-added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Added HPA Helm parameters&lt;/strong&gt;&lt;br&gt;&#xA;To set cluster-level HPA target utilization defaults, you can now use the following Helm chart values:&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;hpaCpuTargetUtilizationMin&#xA;hpaCpuTargetUtilizationMax&#xA;hpaMemoryTargetUtilizationMin&#xA;hpaMemoryTargetUtilizationMax&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.10.1-agent-fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.10.1-agent-fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;HPA annotations released in version 2.10.0&lt;/strong&gt;&lt;br&gt;&#xA;The new HPA annotations added in 2.10.0 did not work as documented, and have been been fixed.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.10.1-agent-security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.10.1-agent-security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Upgraded &lt;code&gt;cloudflare/circl&lt;/code&gt; from version 1.3.3 to version 1.3.7 to address high-severity security issue &lt;code&gt;CIRCL&#39;s Kyber: timing side-channel (kyberslash2)&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;Upgraded &lt;code&gt;golang.org/x/crypto&lt;/code&gt; to v0.17.0&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 5.0.6</title>
				<link>/docs/releases/stormforge-cli/v5.0.6/</link>
				<pubDate>Tue, 09 Jan 2024 18:37:42 +0000</pubDate>
				<guid>/docs/releases/stormforge-cli/v5.0.6/</guid>
				<description>&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The new &lt;code&gt;stormforge edit cluster&lt;/code&gt; command can be used to manage cluster resources&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The &lt;code&gt;stormforge apply&lt;/code&gt; command no longer applies recommendations that have insufficient data unless &lt;code&gt;--force&lt;/code&gt; is used&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;deprecated&#34;&gt;Deprecated&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#deprecated&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The &lt;code&gt;stormforge edit workload label&lt;/code&gt; command is now deprecated. Use  &lt;code&gt;stormforge edit workload --set-label&lt;/code&gt; instead.&lt;/li&gt;&#xA;&lt;li&gt;Deprecation notice: Starting in the &lt;em&gt;next&lt;/em&gt; release, in an effort to reduce dependencies, the &lt;code&gt;stormforge-cli&lt;/code&gt; container image will no longer include a shell.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The &lt;code&gt;stormforge get workload&lt;/code&gt; table view honors &lt;code&gt;--show-impact&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;The &lt;code&gt;stormforge get recommendations&lt;/code&gt; command now fetches all recommendations correctly when you specify JSON, YAML, or CSV output format&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Upgrades dependencies with known vulnerabilities&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.10.0</title>
				<link>/docs/releases/stormforge/previous/v2.10.0-agent/</link>
				<pubDate>Tue, 09 Jan 2024 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.10.0-agent/</guid>
				<description>&lt;h3 id=&#34;v2.10.0-agent-added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.10.0-agent-added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Annotations for HPA CPU and memory target utilization&lt;/strong&gt;&lt;br&gt;&#xA;You can now configure HPA target utilization ranges (min and max values) for both CPU and memory by using the following annotations:&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;live.stormforge.io/hpa.cpu.target-utilization.min&#xA;live.stormforge.io/hpa.cpu.target-utilization.max&#xA;live.stormforge.io/hpa.memory.target-utilization.min&#xA;live.stormforge.io/hpa.memory.target-utilization.max&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.10.0-agent-deprecated&#34;&gt;Deprecated&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.10.0-agent-deprecated&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Pod template (PodTemplateSpec) annotations on workloads&lt;/strong&gt;&lt;br&gt;&#xA;We no longer support PodTemplateSpec (&lt;code&gt;.metadata.spec.template.metadata.annotations&lt;/code&gt;) annotations for annotating workloads.&lt;/p&gt;&#xA;&lt;p&gt;Instead, workload-level annotations must now be added to the workload object directly in the &lt;strong&gt;&lt;code&gt;.metadata.annotations&lt;/code&gt;&lt;/strong&gt; section, as shown in this example:&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;apiVersion: apps/v1&#xA;kind: Deployment&#xA;metadata:&#xA;    name: example&#xA;    namespace: default&#xA;    annotations:&#xA;    live.stormforge.io/auto-deploy: &amp;#34;false&amp;#34;&#xA;    live.stormforge.io/containers.cpu.limits.limit-request-ratio: &amp;#34;1.3&amp;#34;&#xA;    ...&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Applier version 2.2.0</title>
				<link>/docs/releases/stormforge/previous/v2.2.0-applier/</link>
				<pubDate>Tue, 09 Jan 2024 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.2.0-applier/</guid>
				<description>&lt;h3 id=&#34;v2.2.0-applier-security&#34;&gt;Security&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.2.0-applier-security&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Updated &lt;code&gt;golang net/http&lt;/code&gt; packages to address &lt;a href=&#34;https://nvd.nist.gov/vuln/detail/CVE-2023-44487&#34;&gt;CVE-2023-44487&lt;/a&gt;.&lt;/li&gt;&#xA;&lt;li&gt;Updated &lt;a href=&#34;https://pkg.go.dev/golang.org/x/crypto&#34;&gt;&lt;code&gt;golang.org/x/crypto&lt;/code&gt;&lt;/a&gt; from version 0.14.0 to version 0.17.0.&lt;/li&gt;&#xA;&lt;li&gt;Updated &lt;code&gt;go-application&lt;/code&gt; to version 0.0.64.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 5.0.5</title>
				<link>/docs/releases/stormforge-cli/v5.0.5/</link>
				<pubDate>Thu, 30 Nov 2023 15:09:48 +0000</pubDate>
				<guid>/docs/releases/stormforge-cli/v5.0.5/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Dependency upgrades&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;JSON and YAML output should have matching field ordering&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.9.1</title>
				<link>/docs/releases/stormforge/previous/v2.9.1-agent/</link>
				<pubDate>Wed, 29 Nov 2023 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.9.1-agent/</guid>
				<description>&lt;h3 id=&#34;v2.9.1-agent-added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.9.1-agent-added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Additional metrics scraping&lt;/strong&gt;&lt;br&gt;&#xA;Optimize Live now scrapes the following cAdvisor metrics:&lt;br&gt;&#xA;&lt;code&gt;container_cpu_cfs_throttled_seconds_total&lt;/code&gt;, &lt;code&gt;container_memory_max_usage_bytes&lt;/code&gt; and &lt;code&gt;container_oom_events_total&lt;/code&gt;.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.9.0</title>
				<link>/docs/releases/stormforge/previous/v2.9.0-agent/</link>
				<pubDate>Wed, 08 Nov 2023 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.9.0-agent/</guid>
				<description>&lt;h3 id=&#34;v2.9.0-agent-added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.9.0-agent-added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Support for setting deployment thresholds (via UI, CLU, annotations)&lt;/strong&gt;&lt;br&gt;&#xA;To help reduce pod churn, you can now define minimum change thresholds to prevent Optimize Live from automatically applying new recommendations.&lt;/p&gt;&#xA;&lt;p&gt;You can define a percent change, unit amount change, or both, by using the following methods:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;UI&lt;/strong&gt;: On the &lt;strong&gt;Config&lt;/strong&gt; tab of workload details page, as part of the &lt;strong&gt;Automatic Deployment&lt;/strong&gt; setting.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Annotations&lt;/strong&gt;: &lt;code&gt;live.stormforge.io/auto-deploy.thresholds.*&lt;/code&gt; annotations. See the examples in the &lt;a href=&#34;/docs/configure/settings/apply-settings/#thresholds&#34;&gt;Auto-deploy&lt;/a&gt; topic.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;CLI:&lt;/strong&gt; &lt;code&gt;--auto-deploy-thresholds-min*&lt;/code&gt; arguments as part of the &lt;a href=&#34;/docs/stormforge-cli/reference/#stormforge-edit-workloads-handlers&#34;&gt;&lt;code&gt;stormforge edit workloads handler&lt;/code&gt;&lt;/a&gt; command.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;For details, see &lt;a href=&#34;/docs/configure/settings/apply-settings/#thresholds&#34;&gt;Auto-deploy thresholds&lt;/a&gt; in the Auto-deploy settings topic.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Changes to the default optimization policy and limit-to-request ratio&lt;/strong&gt;&lt;br&gt;&#xA;The default optimization policy is now RequestsOnly. Previously, it was RequestsAndLimits.&lt;/p&gt;&#xA;&lt;p&gt;When the optimization policy is set to RequestsAndLimits, the new default limit-to-request ratio is 2.0 (increased from 1.2). Optimize Live will not update containers using a 1.2 ratio to the new default 2.0 ratio. In the UI, a 1.2 limit-to-request ratio is now shown as &lt;strong&gt;Custom&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 5.0.4</title>
				<link>/docs/releases/stormforge-cli/v5.0.4/</link>
				<pubDate>Thu, 02 Nov 2023 17:24:53 +0000</pubDate>
				<guid>/docs/releases/stormforge-cli/v5.0.4/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The &lt;code&gt;edit workload handlers --auto-deploy&lt;/code&gt; flag is no longer implied by the thresholds&lt;/li&gt;&#xA;&lt;li&gt;The &lt;code&gt;edit workload container-resources&lt;/code&gt; command accepts the &lt;code&gt;RequestsAndLimits&lt;/code&gt; policy&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The &lt;code&gt;edit workload container-resources&lt;/code&gt; command can unset values&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 5.0.3</title>
				<link>/docs/releases/stormforge-cli/v5.0.3/</link>
				<pubDate>Thu, 26 Oct 2023 17:12:16 +0000</pubDate>
				<guid>/docs/releases/stormforge-cli/v5.0.3/</guid>
				<description>&lt;h3 id=&#34;added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Support for workload auto-deploy thresholds. See the &lt;code&gt;stormforge edit workload handlers&lt;/code&gt; command in the CLI reference.&lt;/li&gt;&#xA;&lt;li&gt;Workloads can be filtered by over- or under-provisioned state&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Removed references to workload schedule names&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The &lt;code&gt;auth revoke&lt;/code&gt; command was not accepting client identifiers&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.8.0</title>
				<link>/docs/releases/stormforge/previous/v2.8.0-agent/</link>
				<pubDate>Fri, 20 Oct 2023 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.8.0-agent/</guid>
				<description>&lt;h4 id=&#34;v2.8.0-agent-added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.8.0-agent-added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h4&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Easy troubleshooting&lt;/strong&gt;&lt;br&gt;&#xA;You can now do a health check and get troubleshooting info (for example, if the Agent doesn&amp;rsquo;t install as expected) more easily by running:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-sh&#34; data-lang=&#34;sh&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;helm test stormforge-agent -n stormforge-system --logs&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;UI: Add Cluster button now available on the Clusters page; improved cluster management workflow&lt;/strong&gt;&lt;br&gt;&#xA;You can now add clusters via the Optimize Live UI: In the left navigation, click &lt;strong&gt;Clusters&lt;/strong&gt;, and on the Clusters page, click &lt;strong&gt;Add Cluster&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; If you&amp;rsquo;re using the Optimize Live free trial license and want to add another cluster, click &lt;strong&gt;Add Cluster&lt;/strong&gt; and on the next page that&amp;rsquo;s shown, click &lt;strong&gt;Add a cluster to my trial&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Annotations: Support for additional case types (optimization goals and policies only)&lt;/strong&gt;&lt;br&gt;&#xA;UpperCamelCase values align with Kubernetes conventions, but you also can use lowercase values.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Valid values for the &lt;code&gt;live.stormforge.io/cpu.optimization-goal&lt;/code&gt; and &lt;code&gt;live.stormforge.io/memory.optimization-goal&lt;/code&gt; annotations:&lt;/p&gt;&#xA;&lt;p&gt;&lt;code&gt;&amp;quot;Balanced&amp;quot;&lt;/code&gt; (default), &lt;code&gt;&amp;quot;balanced&amp;quot;&lt;/code&gt;, &lt;code&gt;&amp;quot;Reliability&amp;quot;&lt;/code&gt;, &lt;code&gt;&amp;quot;reliability&amp;quot;&lt;/code&gt;, &lt;code&gt;&amp;quot;Savings&amp;quot;&lt;/code&gt;, &lt;code&gt;&amp;quot;savings&amp;quot;&lt;/code&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Valid values for the &lt;code&gt;live.stormforge.io/containers.cpu.optimization-policy&lt;/code&gt; and &lt;code&gt;live.stormforge.io/containers.memory.optimization-policy&lt;/code&gt; annotations:&lt;/p&gt;&#xA;&lt;p&gt;&lt;code&gt;&amp;quot;RequestsAndLimits&amp;quot;&lt;/code&gt; (default), &lt;code&gt;&amp;quot;requestsandlimits&amp;quot;&lt;/code&gt;,  &lt;code&gt;&amp;quot;RequestsOnly&amp;quot;&lt;/code&gt;, &lt;code&gt;&amp;quot;requestsonly&amp;quot;&lt;/code&gt;, &lt;code&gt;&amp;quot;DoNotOptimize&amp;quot;&lt;/code&gt;, &lt;code&gt;&amp;quot;donotoptimize&amp;quot;&lt;/code&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 5.0.2</title>
				<link>/docs/releases/stormforge-cli/v5.0.2/</link>
				<pubDate>Thu, 12 Oct 2023 17:19:52 +0000</pubDate>
				<guid>/docs/releases/stormforge-cli/v5.0.2/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The &lt;code&gt;get cluster&lt;/code&gt; output now includes the Optimize Live and StormForge Applier version numbers&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The &lt;code&gt;check connect&lt;/code&gt; works correctly when testing client credentials&lt;/li&gt;&#xA;&lt;li&gt;Generating tokens no longer requests the &lt;code&gt;offline_access&lt;/code&gt; scope&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.7.1</title>
				<link>/docs/releases/stormforge/previous/v2.7.1-agent/</link>
				<pubDate>Mon, 25 Sep 2023 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.7.1-agent/</guid>
				<description>&lt;h3 id=&#34;v2.7.1-agent-added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.7.1-agent-added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Recommendations for workloads that scale down to 0 replicas&lt;/strong&gt;&lt;br&gt;&#xA;Optimize Live now provides recommendations for workloads that scale down to zero replicas for short periods of time within a 7-day period.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;If a workload is scaled down to 0 replicas for 25% of the time over 7 days, a recommendation is still provided, and you&amp;rsquo;ll see a warning in UI about the amount of time scaled down.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;If a workload is at 0 replicas for more than 75% of the time over 7 days, no recommendation is provided, and you&amp;rsquo;ll see an error in the UI.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.7.0</title>
				<link>/docs/releases/stormforge/previous/v2.7.0-agent/</link>
				<pubDate>Thu, 14 Sep 2023 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.7.0-agent/</guid>
				<description>&lt;h3 id=&#34;v2.7.0-agent-added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.7.0-agent-added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;OpenShift support&lt;/strong&gt;&lt;br&gt;&#xA;You can now optimize workloads on clusters managed by OpenShift. When you install the StormForge Agent on a cluster, include the &lt;code&gt;--set openshift=true&lt;/code&gt; argument. For details, see &lt;a href=&#34;/docs/installation/install-openshift/&#34;&gt;Install on Red Hat OpenShift Container Platform&lt;/a&gt; in the product docs.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Support for automatic rightsizing of workloads scaled by a KEDA-owned HPA&lt;/strong&gt;&lt;br&gt;&#xA;Optimize Live can now provide recommendations and patch workloads that have an HPA that is managed by KEDA. Previously, Optimize Live could only make recommendations for these workloads.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Applier version 2.1.0</title>
				<link>/docs/releases/stormforge/previous/v2.1.0-applier/</link>
				<pubDate>Thu, 14 Sep 2023 08:30:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.1.0-applier/</guid>
				<description>&lt;h3 id=&#34;v2.1.0-applier-added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.1.0-applier-added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Improved patch rollback and workload health checks&lt;/strong&gt;&lt;br&gt;&#xA;The Applier now performs additional health checks to ensure that a workload is always in a healthy state before applying patches. If a patch fails, the Applier can now roll back all patches to reach the previous healthy state.&lt;/p&gt;&#xA;&lt;p&gt;We also improved the Applier logging, making it easier to understand what a patch is doing, patch application progress, and the health of a workload after applying patches.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Support for automatic rightsizing of workloads scaled by a KEDA-owned HPA&lt;/strong&gt;&lt;br&gt;&#xA;Although this is a new &lt;em&gt;Agent&lt;/em&gt; (version 2.7.0) feature, you must grant the StormForge &lt;em&gt;Applier&lt;/em&gt; additional RBAC permissions.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 5.0.1</title>
				<link>/docs/releases/stormforge-cli/v5.0.1/</link>
				<pubDate>Fri, 08 Sep 2023 21:02:31 +0000</pubDate>
				<guid>/docs/releases/stormforge-cli/v5.0.1/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Updated recommendation state names&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The authorization issuer was not configured properly in some cases&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 5.0.0</title>
				<link>/docs/releases/stormforge-cli/v5.0.0/</link>
				<pubDate>Fri, 18 Aug 2023 20:53:13 +0000</pubDate>
				<guid>/docs/releases/stormforge-cli/v5.0.0/</guid>
				<description>&lt;h3 id=&#34;changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Workload and recommendation commands reflect consolidation to a single schedule&lt;/li&gt;&#xA;&lt;li&gt;The &lt;code&gt;stormforge get workloads&lt;/code&gt; command hides impact details unless &lt;code&gt;--show-impact&lt;/code&gt; is used&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;removed&#34;&gt;Removed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#removed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The &lt;code&gt;install&lt;/code&gt; and &lt;code&gt;uninstall&lt;/code&gt; commands have been removed&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The &lt;code&gt;stormforge edit workload&lt;/code&gt; commands ignore workloads using in-cluster configuration&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.6.0</title>
				<link>/docs/releases/stormforge/previous/v2.6.0-agent/</link>
				<pubDate>Fri, 18 Aug 2023 10:30:00 -0500</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.6.0-agent/</guid>
				<description>&lt;h3 id=&#34;v2.6.0-agent-added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.6.0-agent-added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Optimize Live 30-day free trial&lt;/strong&gt;&lt;br&gt;&#xA;If you’re not already using Optimize Live, sign up at &lt;strong&gt;&lt;a href=&#34;https://app.stormforge.io/signup&#34;&gt;app.stormforge.io/signup&lt;/a&gt;&lt;/strong&gt; and within minutes, you’ll have Optimize Live running on the Kubernetes cluster you specify.&lt;/p&gt;&#xA;&lt;p&gt;Need to see it to believe it? This 3-min &lt;strong&gt;&lt;a href=&#34;https://youtu.be/CkpEqJssNfo&#34;&gt;Getting Started video&lt;/a&gt;&lt;/strong&gt; walks you through setup (which takes less than 2 minutes) and gives you a quick overview of the insights you&amp;rsquo;ll get in just 1 hour after installation.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;New StormForge Agent installation wizard&lt;/strong&gt;&lt;br&gt;&#xA;If you’re just starting out with Optimize Live, you can now install the StormForge Agent by using the Get Started wizard. Log in to &lt;a href=&#34;https://app.stormforge.io&#34;&gt;app.stormforge.io&lt;/a&gt; with your StormForge login, and in the left navigation, click &lt;strong&gt;Overview&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Recommendation schedules now support for Cron format&lt;/strong&gt;&lt;br&gt;&#xA;When you configure workloads using Kubernetes annotations, you can now set a schedule using &lt;a href=&#34;https://en.wikipedia.org/wiki/Cron&#34;&gt;Cron&lt;/a&gt; format. Previously, only macros and &lt;a href=&#34;https://en.wikipedia.org/wiki/ISO_8601#Durations&#34;&gt;ISO 8601 Duration&lt;/a&gt; strings were supported.&lt;/p&gt;&#xA;&lt;p&gt;Examples:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Once daily (default value and best practice):&lt;br&gt;&#xA;&lt;code&gt;live.stormforge.io/schedule: &amp;quot;H H * * *&amp;quot;&lt;/code&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Every morning at approximately 0800h (exact time is not guaranteed):&#xA;&lt;code&gt;live.stormforge.io/schedule: &amp;quot;00 08 * * *&amp;quot;&lt;/code&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;For details, see the &lt;a href=&#34;/docs/configure/settings/schedule/&#34;&gt;Recommendation schedule&lt;/a&gt; topic.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Applier version 2.0.6</title>
				<link>/docs/releases/stormforge/previous/v2.0.6-applier/</link>
				<pubDate>Thu, 03 Aug 2023 15:00:00 -0500</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.0.6-applier/</guid>
				<description>&lt;h3 id=&#34;v2.0.6-applier-changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.0.6-applier-changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Applier Helm chart updates&lt;/strong&gt;&lt;br&gt;&#xA;We updated the Applier’s Helm chart to use new Agent secret names and values. No action is required unless you have changed Agent secret values.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.5.1</title>
				<link>/docs/releases/stormforge/previous/v2.5.1-agent/</link>
				<pubDate>Thu, 03 Aug 2023 10:30:00 -0500</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.5.1-agent/</guid>
				<description>&lt;h3 id=&#34;v2.5.1-agent-fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.5.1-agent-fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;We fixed an encoding problem with the manageAuthSecret feature released in version 2.5.0.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.5.0</title>
				<link>/docs/releases/stormforge/previous/v2.5.0-agent/</link>
				<pubDate>Fri, 28 Jul 2023 18:30:00 -0500</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.5.0-agent/</guid>
				<description>&lt;h3 id=&#34;v2.5.0-agent-changed&#34;&gt;Changed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.5.0-agent-changed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Helm installation: &lt;code&gt;--set stormforge.clusterName=CLUSTER_NAME&lt;/code&gt; must be changed to &lt;code&gt;--set clusterName=CLUSTER_NAME&lt;/code&gt;.&lt;/li&gt;&#xA;&lt;li&gt;We now consume the &lt;code&gt;prometheus&lt;/code&gt; image from quay.io instead from Docker Hub. To fallback to Docker Hub, pass the following parameter as part of the Helm installation: &lt;code&gt;--set prom.image.repository=prom/prometheus&lt;/code&gt;.&lt;/li&gt;&#xA;&lt;li&gt;To manage or rotate authorization credentials outside of Helm, set the Helm value manageAuthSecret to &lt;code&gt;false&lt;/code&gt;. If you set this value to &lt;code&gt;false&lt;/code&gt;, make sure that the stormforge-agent-auth secret exists before installing or upgrading.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;v2.5.0-agent-known-issues&#34;&gt;Known Issues&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.5.0-agent-known-issues&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;In certain environments, changing namespace-level StormForge annotations might not trigger reconciliation. For these scenarios, the annotations will be granted only on the following Agent restart.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.4.1</title>
				<link>/docs/releases/stormforge/previous/v2.4.1-agent/</link>
				<pubDate>Fri, 21 Jul 2023 16:00:00 -0500</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.4.1-agent/</guid>
				<description>&lt;h3 id=&#34;v2.4.1-agent-fixed&#34;&gt;Fixed&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.4.1-agent-fixed&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The controller no longer crashes when reconciling WorkloadOptimizer custom resources.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.4.0</title>
				<link>/docs/releases/stormforge/previous/v2.4.0-agent/</link>
				<pubDate>Mon, 17 Jul 2023 16:00:00 -0500</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.4.0-agent/</guid>
				<description>&lt;h3 id=&#34;v2.4.0-agent-added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.4.0-agent-added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Support for setting default workload values at the cluster level&lt;/strong&gt;&lt;br&gt;&#xA;You can now use a configuration file or command line arguments as part of the &lt;code&gt;helm install&lt;/code&gt; command to set default values for all workloads in a cluster. See the examples below.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Configuration file:&lt;/strong&gt; Create a .yaml file and set the workload- and container-level values.&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;clusterDefaultConfig:&#xA;    schedule: P1D&#xA;    containersCpuRequestsMin: 100m,istio-proxy=50m&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;&lt;strong&gt;Command line arguments:&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;--set clusterDefaultConfig.schedule=P1D \&#xA;--set clusterDefaultConfig.containersCpuRequestsMin=100m,istio-proxy=50m&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Support for setting default workload values at the namespace level&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;You can now use annotations to set default workload values at the namespace level. Namespace-level values override cluster-level values.&lt;/p&gt;&#xA;&lt;p&gt;Add the annotations to the &lt;code&gt;metadata.annotations&lt;/code&gt; section of the namespace values file.&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-yaml&#34; data-lang=&#34;yaml&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt; &lt;span style=&#34;color:#f92672&#34;&gt;apiVersion&lt;/span&gt;: &lt;span style=&#34;color:#ae81ff&#34;&gt;v1&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt; &lt;span style=&#34;color:#f92672&#34;&gt;kind&lt;/span&gt;: &lt;span style=&#34;color:#ae81ff&#34;&gt;Namespace&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt; &lt;span style=&#34;color:#f92672&#34;&gt;metadata&lt;/span&gt;:&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt; &lt;span style=&#34;color:#f92672&#34;&gt;annotations&lt;/span&gt;: &#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;     &lt;span style=&#34;color:#f92672&#34;&gt;live.stormforge.io/schedule&lt;/span&gt;: &lt;span style=&#34;color:#e6db74&#34;&gt;&amp;#34;P1D&amp;#34;&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;     &lt;span style=&#34;color:#f92672&#34;&gt;live.stormforge.io/containers.cpu.requests.min&lt;/span&gt;: &lt;span style=&#34;color:#e6db74&#34;&gt;&amp;#34;100m,istio-proxy=50m&amp;#34;&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt; &lt;span style=&#34;color:#f92672&#34;&gt;creationTimestamp&lt;/span&gt;: &lt;span style=&#34;color:#e6db74&#34;&gt;&amp;#34;2023-07-20T17:28:42Z&amp;#34;&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt; &lt;span style=&#34;color:#f92672&#34;&gt;labels&lt;/span&gt;:&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;     &lt;span style=&#34;color:#f92672&#34;&gt;kubernetes.io/metadata.name&lt;/span&gt;: &lt;span style=&#34;color:#ae81ff&#34;&gt;kube-public&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt; &lt;span style=&#34;color:#f92672&#34;&gt;name&lt;/span&gt;: &lt;span style=&#34;color:#ae81ff&#34;&gt;kube-public&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt; &lt;span style=&#34;color:#f92672&#34;&gt;resourceVersion&lt;/span&gt;: &lt;span style=&#34;color:#e6db74&#34;&gt;&amp;#34;9&amp;#34;&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt; &lt;span style=&#34;color:#f92672&#34;&gt;uid&lt;/span&gt;: &lt;span style=&#34;color:#ae81ff&#34;&gt;&amp;lt;UID&amp;gt;&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt; &lt;span style=&#34;color:#f92672&#34;&gt;spec&lt;/span&gt;:&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt; &lt;span style=&#34;color:#ae81ff&#34;&gt;...&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Applier version 2.0.5</title>
				<link>/docs/releases/stormforge/previous/v2.0.5-applier/</link>
				<pubDate>Thu, 06 Jul 2023 15:00:00 -0500</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.0.5-applier/</guid>
				<description>&lt;p&gt;This release contained internal enhancements only. No action is required.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Agent version 2.3.0</title>
				<link>/docs/releases/stormforge/previous/v2.3.0-agent/</link>
				<pubDate>Thu, 29 Jun 2023 16:00:00 -0500</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.3.0-agent/</guid>
				<description>&lt;h3 id=&#34;v2.3.0-agent-added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.3.0-agent-added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Support for ingesting workload labels&lt;/strong&gt;&lt;br&gt;&#xA;By default, Optimize Live now ingests labels on Kubernetes workload objects, ensuring that StormForge workload labels match your workload labels, making it easier for you to search for workloads.&lt;/p&gt;&#xA;&lt;p&gt;To change this default behavior, setting &lt;code&gt;collectLabels&lt;/code&gt; to &lt;code&gt;false&lt;/code&gt; in a &lt;code&gt;helm install&lt;/code&gt; or &lt;code&gt;helm upgrade&lt;/code&gt; command:&#xA;&lt;code&gt;--set collectLabels=false&lt;/code&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Support for setting container default values by using annotations&lt;/strong&gt;&lt;br&gt;&#xA;You can now set default values for &lt;em&gt;all&lt;/em&gt; containers in a workload by using annotations in pod objects.&lt;/p&gt;&#xA;&lt;p&gt;In the Pod template metadata (&lt;code&gt;spec.template.metadata.annotations&lt;/code&gt;) of a Deployment object, use the following syntax:&#xA;&lt;code&gt;live.stormforge.io/containers.CONTAINER_PARAMETER: &amp;quot;DEFAULT_VALUE&amp;quot;&lt;/code&gt;&lt;/p&gt;&#xA;&lt;p&gt;Example: To set &lt;code&gt;cpu.requests.min&lt;/code&gt; to &lt;code&gt;20m&lt;/code&gt; for all containers in a workload: &lt;br&gt;&#xA;&lt;code&gt;live.stormforge.io/containers.cpu.requests.min: “20m”&lt;/code&gt;&lt;/p&gt;&#xA;&lt;p&gt;To learn more about setting default values by using annotations, see the topics under &lt;a href=&#34;/docs/configure/&#34;&gt;Configure optimization settings&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Applier version 2.0.4</title>
				<link>/docs/releases/stormforge/previous/v2.0.4-applier/</link>
				<pubDate>Thu, 29 Jun 2023 15:00:00 -0500</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.0.4-applier/</guid>
				<description>&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Additional custom Prometheus metrics&lt;/strong&gt;&lt;br&gt;&#xA;You can now get more Applier performance details with the following Prometheus metrics:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;The following new metrics are vectored and have &lt;code&gt;workload_namespace&lt;/code&gt; and &lt;code&gt;workload_resource&lt;/code&gt; labels:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;sf_patches_processed_total&lt;/li&gt;&#xA;&lt;li&gt;sf_patches_failed_total&lt;/li&gt;&#xA;&lt;li&gt;sf_patches_rolled_back_total&lt;/li&gt;&#xA;&lt;li&gt;sf_patches_rollback_failures_total&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;The following new metric does not have the &lt;code&gt;workload_namespace&lt;/code&gt; and &lt;code&gt;workload_resource&lt;/code&gt; labels - it applies only to the Applier, not a specific workload:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;sf_applier_api_disconnections_total&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Agent version 2.2.0</title>
				<link>/docs/releases/stormforge/previous/v2.2.0-agent/</link>
				<pubDate>Thu, 15 Jun 2023 16:00:00 -0500</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.2.0-agent/</guid>
				<description>&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Workload garbage collection&lt;/strong&gt;&lt;br&gt;&#xA;We now do garbage collection (by default, every hour) to ensure that when workloads are removed from the cluster, they’re also removed from Optimize Live. To change this reconciliation interval, edit the &lt;code&gt;workload.workloadSyncInterval&lt;/code&gt; in the workload’s &lt;code&gt;values.yaml&lt;/code&gt; file.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Regex support&lt;/strong&gt;&lt;br&gt;&#xA;We added regex support for the optional allowNamespaces and denyNamespaces parameters that you can provide when you install the StormForge agent.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Applier version 2.0.3</title>
				<link>/docs/releases/stormforge/previous/v2.0.3-applier/</link>
				<pubDate>Thu, 15 Jun 2023 15:00:00 -0500</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.0.3-applier/</guid>
				<description>&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Patch rollback support&lt;/strong&gt;&lt;br&gt;&#xA;We added rollback logic: If an error occurs when applying a patch for a recommendation, successful patches are rolled back.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Version 2.0</title>
				<link>/docs/releases/stormforge/previous/v2.0/</link>
				<pubDate>Thu, 13 Apr 2023 00:00:00 +0000</pubDate>
				<guid>/docs/releases/stormforge/previous/v2.0/</guid>
				<description>&lt;p&gt;Be sure to check out our &lt;a href=&#34;https://www.stormforge.io/press-releases/stormforge-launches-v2-optimize-live-kubernetes-resource-optimization/&#34;&gt;press release&lt;/a&gt;!&lt;/p&gt;&#xA;&lt;h5 id=&#34;v2.0-added&#34;&gt;Added&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#v2.0-added&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h5&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;New install method: Helm chart for stormforge-agent&lt;/strong&gt;&lt;br&gt;&#xA;You no longer need to download the StormForge CLI to install. Get up and running within minutes, and download the CLI later to run StormForge commands to manage your cluster.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Optional Applier installation using a single Helm command&lt;/strong&gt;&lt;br&gt;&#xA;We separated the Agent and the Applier to simplify the permissions required at install.&lt;br&gt;&#xA;If you plan to apply configurations on demand (outside of a regular schedule) or automatically outside of a CI/CD workflow, be sure to install the Applier component.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Control workload metrics collection with allow and deny lists&lt;/strong&gt;&lt;br&gt;&#xA;By default, Optimize Live collects metrics on all the workloads in the cluster.&lt;br&gt;&#xA;To restrict metrics collection to specific namespaces, you can provide a namespace allow list or deny list to when you install the agent.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;New UI workflows&lt;/strong&gt;&lt;br&gt;&#xA;&lt;strong&gt;Workload List View:&lt;/strong&gt; See all workloads and the recommendations for those workloads, view cost estimates, and search against workload name, namespace, or cluster.&lt;br&gt;&#xA;&lt;strong&gt;Workload Detail View&lt;/strong&gt;: View the impact of the recommendations on the workload, drill into the recommendation details, and get container-specific details. Export or download the patch from the UI.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>Account not activated</title>
				<link>/docs/api/auth_not_activated/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/api/auth_not_activated/</guid>
				<description>&lt;p&gt;To activate your account, log in to &lt;strong&gt;&lt;a href=&#34;https://app.stormforge.io/&#34;&gt;app.stormforge.io&lt;/a&gt;&lt;/strong&gt; using the email address you signed up with.&lt;/p&gt;</description>
			</item>
			<item>
				<title>You are now authenticated</title>
				<link>/docs/api/auth_success/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/api/auth_success/</guid>
				<description>&lt;p&gt;Your workstation is authenticated with StormForge, so you can use the StormForge CLI to query your clusters, workloads, and recommendations. You can close this window.&lt;/p&gt;&#xA;&lt;h2 id=&#34;next-steps&#34;&gt;Next steps&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#next-steps&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;StormForge analyzes observability data to recommend Kubernetes CPU and memory settings that reduce wasted resources and improve application performance.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;/about/&#34;&gt;About StormForge&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;/docs/installation/install/&#34;&gt;Install StormForge&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;/docs/configure/&#34;&gt;Configure default optimization settings&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;releases&#34;&gt;Releases&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#releases&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;/docs/releases/whats-new/&#34;&gt;What&amp;rsquo;s new in StormForge&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;/docs/releases/stormforge/&#34;&gt;StormForge Agent releases&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;/docs/releases/stormforge-cli/&#34;&gt;StormForge CLI releases&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Need help? &lt;a href=&#34;https://www.cloudbolt.io/company/contact-us/&#34;&gt;Contact us&lt;/a&gt;.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
