<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Resources on contineroo.ch</title>
    <link>/docs/cloudflare-operator/resources/</link>
    <description>Recent content in Resources on contineroo.ch</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <atom:link href="/docs/cloudflare-operator/resources/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Account</title>
      <link>/docs/cloudflare-operator/resources/account/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/cloudflare-operator/resources/account/</guid>
      <description>&lt;p&gt;The API specification can be viewed &lt;a href=&#34;/docs/cloudflare-operator/api_reference/#cloudflare-operator.io/v1.Account&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;In order to use cloudflare-operator, you need to create an account resource. This resource contains the credentials for the Cloudflare API.&lt;/p&gt;&#xA;&lt;p&gt;Learn more about the account resource in the &lt;a href=&#34;/docs/cloudflare-operator/get_started/&#34;&gt;getting started guide&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Zone</title>
      <link>/docs/cloudflare-operator/resources/zone/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/cloudflare-operator/resources/zone/</guid>
      <description>&lt;p&gt;The API specification can be viewed &lt;a href=&#34;/docs/cloudflare-operator/api_reference/#cloudflare-operator.io/v1.Zone&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Zone resources represent Cloudflare zones and are used to tell cloudflare-operator which zones to manage.&lt;/p&gt;&#xA;&lt;p&gt;Learn more about the zone resource in the &lt;a href=&#34;/docs/cloudflare-operator/get_started/&#34;&gt;getting started guide&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;If you have more than one Account resource, set &lt;code&gt;spec.accountRef.name&lt;/code&gt; on each Zone so the operator knows which Cloudflare credentials to use. When only one Account exists in the cluster, &lt;code&gt;accountRef&lt;/code&gt; can be omitted.&lt;/p&gt;&#xA;&lt;h2 id=&#34;prevent-certain-dns-records-from-being-deleted-when-zone-prune-is-enabled&#34;&gt;Prevent Certain DNS Records From Being Deleted When Zone Prune Is Enabled&lt;/h2&gt;&#xA;&lt;p&gt;Prior to &lt;strong&gt;v1.7.0&lt;/strong&gt;, &lt;code&gt;cloudflare-operator&lt;/code&gt; had a fixed set of DNS records that were always ignored when &lt;code&gt;Zone&lt;/code&gt; prune was enabled. These included records required for ACME certificate validation and Cloudflare-specific TXT records. Users could not modify this behavior.&lt;/p&gt;</description>
    </item>
    <item>
      <title>DNSRecord</title>
      <link>/docs/cloudflare-operator/resources/dnsrecord/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/cloudflare-operator/resources/dnsrecord/</guid>
      <description>&lt;p&gt;The API specification can be viewed &lt;a href=&#34;/docs/cloudflare-operator/api_reference/#cloudflare-operator.io/v1.DNSRecord&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;DNSRecord resources represent DNS records in the Cloudflare account.&lt;/p&gt;&#xA;&lt;p&gt;For each DNS record, you need to create a DNSRecord resource.&lt;/p&gt;&#xA;&lt;p&gt;cloudflare-operator will create the DNS record in the Cloudflare account and keep it in sync with the DNSRecord resource.&lt;/p&gt;&#xA;&lt;p&gt;As described in the Ingress and Gateway API guides, cloudflare-operator can create DNSRecords from Ingress and supported Gateway API route resources.&lt;/p&gt;&#xA;&lt;p&gt;DNSRecords are reconciled through the Account selected by their matching Zone. If the Zone does not set &lt;code&gt;spec.accountRef.name&lt;/code&gt;, a DNSRecord can set &lt;code&gt;spec.accountRef.name&lt;/code&gt; directly. If both the Zone and DNSRecord set an Account, they must reference the same Account.&lt;/p&gt;</description>
    </item>
    <item>
      <title>IP</title>
      <link>/docs/cloudflare-operator/resources/ip/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/cloudflare-operator/resources/ip/</guid>
      <description>&lt;p&gt;The API specification can be viewed &lt;a href=&#34;/docs/cloudflare-operator/api_reference/#cloudflare-operator.io/v1.IP&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;As described in the &lt;a href=&#34;/docs/cloudflare-operator/core_concepts/#ip-objects&#34;&gt;core concept&lt;/a&gt;, IP objects can be used&#xA;to follow the &amp;ldquo;don&amp;rsquo;t repeat yourself&amp;rdquo; (DRY) principle.&lt;/p&gt;&#xA;&lt;p&gt;They also allow you to use the same IP address in multiple DNS records and let you use cloudflare-operator&#xA;as a dynamic DNS service.&lt;/p&gt;&#xA;&lt;p&gt;Learn more about the usage of IP objects in the &lt;a href=&#34;/docs/cloudflare-operator/guides/dynamic_ip/&#34;&gt;dynamic DNS guide&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
