<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Armory Docs – Release Notes</title><link>/plugins/scale-agent/release-notes/</link><description>Recent content in Release Notes on Armory Docs</description><generator>Hugo -- gohugo.io</generator><atom:link href="/plugins/scale-agent/release-notes/index.xml" rel="self" type="application/rss+xml"/><item><title>Plugins: Armory Scale Agent Service Release Notes</title><link>/plugins/scale-agent/release-notes/agent-service/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/plugins/scale-agent/release-notes/agent-service/</guid><description>
&lt;table>
&lt;thead>
&lt;tr>
&lt;th style="text-align:left">Armory CD (Spinnaker) Version&lt;/th>
&lt;th style="text-align:left">Scale Agent Plugin Version&lt;/th>
&lt;th style="text-align:left">Scale Agent Service Version&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td style="text-align:left">2.28.x (1.28.x)&lt;/td>
&lt;td style="text-align:left">0.11.56&lt;/td>
&lt;td style="text-align:left">1.0.84&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align:left">1.29.x&lt;/td>
&lt;td style="text-align:left">0.12.21&lt;/td>
&lt;td style="text-align:left">1.0.84&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align:left">2.30.x (1.30.x)&lt;/td>
&lt;td style="text-align:left">0.13.20&lt;/td>
&lt;td style="text-align:left">1.0.84&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align:left">2.31.x (1.31.x)&lt;/td>
&lt;td style="text-align:left">0.14.1&lt;/td>
&lt;td style="text-align:left">1.0.84&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align:left">2.32.x (1.32.x)&lt;/td>
&lt;td style="text-align:left">0.14.1&lt;/td>
&lt;td style="text-align:left">1.0.84&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align:left">2.35.x (1.35.x)&lt;/td>
&lt;td style="text-align:left">0.16.2&lt;/td>
&lt;td style="text-align:left">1.0.84&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;p>Database compatibility:&lt;/p>
&lt;table>
&lt;thead>
&lt;tr>
&lt;th style="text-align:left">MySQL&lt;/th>
&lt;th style="text-align:left">PostgreSQL&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td style="text-align:left">5.7; AWS Aurora&lt;/td>
&lt;td style="text-align:left">10&amp;#43;&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;h2 id="release-notes">Release Notes&lt;/h2>
&lt;h3>&lt;a class="fas fa-rss" target="_blank" href="/plugins/scale-agent/release-notes/agent-service//index.xml">&lt;/a>&lt;/h3>
&lt;div class="alert alert-warning" role="alert">
&lt;h4 class="alert-heading">Known Issue&lt;/h4>
&lt;p>Note the following before upgrading the Armory Scale Agent service:&lt;/p>
&lt;ul>
&lt;li>Starting from &lt;strong>v1.0.42&lt;/strong>, the &lt;code>clouddriver.insecure&lt;/code> flag is set to &lt;code>true&lt;/code> by default. If you are using TLS, make sure to set it to &lt;code>false&lt;/code>.&lt;/li>
&lt;li>Versions &lt;strong>v1.0.32&lt;/strong> to &lt;strong>v1.0.46&lt;/strong> may have an inconsistent &lt;code>last-applied-configuration&lt;/code> annotation and &lt;code>.metadata.managedFields&lt;/code>. This may prevent you from deleting container sidecars, volumeMounts, envs, and other lists representing Maps in manifests. Since v1.0.47, agent is able to keep both the annotation and field managers consistent when configured to use server side apply. To use server side apply after v1.0.47, add a &lt;code>agent-k8s.armory.io/serverside-apply: true&lt;/code> annotation to your manifest in case by case basis, or set &lt;code>kubernetes.serverSideApply.enabled: always&lt;/code> in the configuration to use server side apply on all manifests. Running &lt;code>kubectl apply --server-side --force-conflicts&lt;/code> with kubectl version&amp;gt;=v1.26.0 will also keep both the annotation and field managers consistent. After that, both server side and client side apply deploymets will work normally.&lt;/li>
&lt;li>Versions &lt;strong>v1.0.50&lt;/strong> to &lt;strong>v1.0.51&lt;/strong> has a nil pointer error that happens when there are user declared CRDs in the config file.&lt;/li>
&lt;/ul>
&lt;p>Timeouts can occur after restarting Clouddriver or Agent. This issue is intermittent. It may occur when you upgrade the Armory Scale Agent service or plugin because the upgrade process involves restarting, but it is due to the restart and not the upgrade. These timeouts should resolve after a few minutes.&lt;/p>
&lt;/div></description></item><item><title>Plugins: Armory Scale Agent Clouddriver Plugin Release Notes</title><link>/plugins/scale-agent/release-notes/agent-plugin/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/plugins/scale-agent/release-notes/agent-plugin/</guid><description>
&lt;table>
&lt;thead>
&lt;tr>
&lt;th style="text-align:left">Armory CD (Spinnaker) Version&lt;/th>
&lt;th style="text-align:left">Scale Agent Plugin Version&lt;/th>
&lt;th style="text-align:left">Scale Agent Service Version&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td style="text-align:left">2.28.x (1.28.x)&lt;/td>
&lt;td style="text-align:left">0.11.56&lt;/td>
&lt;td style="text-align:left">1.0.84&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align:left">1.29.x&lt;/td>
&lt;td style="text-align:left">0.12.21&lt;/td>
&lt;td style="text-align:left">1.0.84&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align:left">2.30.x (1.30.x)&lt;/td>
&lt;td style="text-align:left">0.13.20&lt;/td>
&lt;td style="text-align:left">1.0.84&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align:left">2.31.x (1.31.x)&lt;/td>
&lt;td style="text-align:left">0.14.1&lt;/td>
&lt;td style="text-align:left">1.0.84&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align:left">2.32.x (1.32.x)&lt;/td>
&lt;td style="text-align:left">0.14.1&lt;/td>
&lt;td style="text-align:left">1.0.84&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align:left">2.35.x (1.35.x)&lt;/td>
&lt;td style="text-align:left">0.16.2&lt;/td>
&lt;td style="text-align:left">1.0.84&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;p>Database compatibility:&lt;/p>
&lt;table>
&lt;thead>
&lt;tr>
&lt;th style="text-align:left">MySQL&lt;/th>
&lt;th style="text-align:left">PostgreSQL&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td style="text-align:left">5.7; AWS Aurora&lt;/td>
&lt;td style="text-align:left">10&amp;#43;&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;h2 id="release-notes">Release Notes&lt;/h2>
&lt;h3>&lt;a class="fas fa-rss" target="_blank" href="/plugins/scale-agent/release-notes/agent-plugin//index.xml">&lt;/a>&lt;/h3>
&lt;div class="alert alert-warning" role="alert">
&lt;h4 class="alert-heading">Known Issue&lt;/h4>
&lt;p>Note the following before upgrading the Armory Scale Agent Plugin:&lt;/p>
&lt;ul>
&lt;li>
&lt;p>Do not use plugin versions v0.8.35 - v0.8.38, v0.9.27 - v0.9.30, v0.10.11 - v0.10.14 with more than one Clouddriver replica in a production environment.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Timeouts can occur after restarting Clouddriver or Agent. This issue is intermittent. It may occur when you upgrade the Armory Scale Agent Service or Plugin because the upgrade process involves restarting, but it is due to the restart and not the upgrade.&lt;/p>
&lt;p>These timeout errors should resolve after several minutes. This issue affects all current versions of the Armory Scale Agent.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Do not use plugin versions v0.9.75 - v0.9.82, v0.10.60 - v0.10.66, v0.11.22 - v0.11.28 with agent version &amp;gt;= v1.0.26, otherwise it could cause to have Timeouts issues.&lt;/p>
&lt;/li>
&lt;/ul>
&lt;/div></description></item></channel></rss>