<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Install Agones on Agones</title>
    <link>/site/docs/installation/install-agones/</link>
    <description>Recent content in Install Agones on Agones</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language><atom:link href="/site/docs/installation/install-agones/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Install Agones using YAML</title>
      <link>/site/docs/installation/install-agones/yaml/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/site/docs/installation/install-agones/yaml/</guid>
      <description>Installing Agones Warning Installing Agones with the install.yaml file will use pre-generated, well known TLS certificates stored in this repository for securing Kubernetes webhooks communication.
For production workloads, we strongly recommend using the helm installation which allows you to generate new, unique certificates or provide your own certificates. Alternatively, you can use helm template as described below to generate a custom yaml installation file with unique certificates.
Installing Agones using the pre-generated install.</description>
    </item>
    
    <item>
      <title>Install Agones using Helm</title>
      <link>/site/docs/installation/install-agones/helm/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/site/docs/installation/install-agones/helm/</guid>
      <description>Prerequisites Helm package manager 3.2.3+ Supported Kubernetes Cluster Helm 3 Installing the Chart To install the chart with the release name my-release using our stable helm repository:
helm repo add agones https://agones.dev/chart/stable helm repo update helm install my-release --namespace agones-system --create-namespace agones/agones We recommend installing Agones in its own namespaces, such as agones-system as shown above. If you want to use a different namespace, you can use the helm --namespace parameter to specify.</description>
    </item>
    
  </channel>
</rss>
