<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Best Practices on Agones</title>
    <link>/site/docs/guides/best-practices/</link>
    <description>Recent content in Best Practices on Agones</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Fri, 12 May 2023 00:00:00 +0000</lastBuildDate><atom:link href="/site/docs/guides/best-practices/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Google Kubernetes Engine Best Practices</title>
      <link>/site/docs/guides/best-practices/gke/</link>
      <pubDate>Fri, 12 May 2023 00:00:00 +0000</pubDate>
      
      <guid>/site/docs/guides/best-practices/gke/</guid>
      <description>Overview On this page, we&amp;rsquo;ve collected several Google Kubernetes Engine (GKE) best practices.
Release Channels Why? We recommend using Release Channels for all GKE clusters. Using Release Channels has several advantages:
Google automatically manages the version and upgrade cadence for your Kubernetes Control Plane and its nodes. Clusters on a Release Channel are allowed to use the No minor upgrades and No minor or node upgrades scope of maintenance exclusions - in other words, enrolling a cluster in a Release Channel gives you more control over node upgrades.</description>
    </item>
    
  </channel>
</rss>
