<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Configure Scaling on Spinnaker</title>
		<link>https://deploy-preview-637--spinnaker-io.netlify.app/docs/setup/productionize/scaling/</link>
		<description>Recent content in Configure Scaling on Spinnaker</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<atom:link href="https://deploy-preview-637--spinnaker-io.netlify.app/docs/setup/productionize/scaling/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Horizontally Scale Spinnaker Services</title>
				<link>https://deploy-preview-637--spinnaker-io.netlify.app/docs/setup/productionize/scaling/horizontal-scaling/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://deploy-preview-637--spinnaker-io.netlify.app/docs/setup/productionize/scaling/horizontal-scaling/</guid>
				<description>&lt;p&gt;This page will explain under which circumstances it can help to&#xA;run more than one copy of any single service, and what considerations have to&#xA;be made when doing so.&lt;/p&gt;&#xA;&lt;p&gt;This article assumes you have access to scale the individual Spinnaker&#xA;microservices, and the mechanics of this are not covered here.&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;Keep in mind, if you are deploying Spinnaker to Kubernetes, you&amp;rsquo;re more&#xA;likely to see benefits of horizontal scaling if you&amp;rsquo;ve already allocated&#xA;resource requests and limits for the services being scaled.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
