<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Cluster Recovery on JayeX - Cloud Native CI/CD Built On Kubernetes</title>
		<link>https://jx-docs-jx-jayex-io-jx-docs-pr-19.infra.jenkins-x.rocks/v3/admin/guides/cluster-recovery/</link>
		<description>Recent content in Cluster Recovery on JayeX - Cloud Native CI/CD Built On Kubernetes</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<atom:link href="https://jx-docs-jx-jayex-io-jx-docs-pr-19.infra.jenkins-x.rocks/v3/admin/guides/cluster-recovery/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Cluster Recovery Demo</title>
				<link>https://jx-docs-jx-jayex-io-jx-docs-pr-19.infra.jenkins-x.rocks/v3/admin/guides/cluster-recovery/cluster-demo/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://jx-docs-jx-jayex-io-jx-docs-pr-19.infra.jenkins-x.rocks/v3/admin/guides/cluster-recovery/cluster-demo/</guid>
				<description>&lt;p&gt;This section describes cluster recovery situations for when things go bad.  It can also be used to reguary recreate clusters, this is something the JayeX project does itself as we prefer to treat our clusters as cattle and not pets, giving confidence that we can restore services at any time.&lt;/p&gt;&#xA;&lt;p&gt;Disclaimer: there may well be better approaches so if you know of better ways please contribute and help improve the experience.  There are some manual steps below that we know to work but expect we can improve.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Cluster Rebuild Example</title>
				<link>https://jx-docs-jx-jayex-io-jx-docs-pr-19.infra.jenkins-x.rocks/v3/admin/guides/cluster-recovery/cluster-rebuild/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://jx-docs-jx-jayex-io-jx-docs-pr-19.infra.jenkins-x.rocks/v3/admin/guides/cluster-recovery/cluster-rebuild/</guid>
				<description>&lt;p&gt;This is an example on how to treat your clusters as cattle and not pets by rebuilding a JX3/GKE environment and restoring to it&amp;rsquo;s previous configuration. The steps will include building a JX3 Google/GSM environment from scratch and deploying projects to staging and production. It will utilize DNS (&lt;code&gt;jx3rocks.com&lt;/code&gt;), TLS, Let&amp;rsquo;s Encrypt certificates. The example includes the recovery of the helm chart repository which is currently implemented with &lt;a href=&#34;https://github.com/helm/chartmuseum&#34;&gt;ChartMuseum&lt;/a&gt; . This example is inteded for an audience already familiar with JayeX operability and focuses on an example of actual commands used to build and maintain a recoverable  environment. Additional information regarding using Google as the provider for this example can be found under &lt;a href=&#34;https://jx-docs-jx-jayex-io-jx-docs-pr-19.infra.jenkins-x.rocks/v3/admin/guides/tls_dns/#prerequisites&#34;&gt;Google Cloud Platform Prequisites&lt;/a&gt;.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
