<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Managed Resources on Crossplane</title><link>https://deploy-preview-1062--crossplane.netlify.app/v2.0-preview/managed-resources/</link><description>Recent content in Managed Resources on Crossplane</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Mon, 01 Jan 0001 00:00:00 +0000</lastBuildDate><atom:link href="https://deploy-preview-1062--crossplane.netlify.app/v2.0-preview/managed-resources/index.xml" rel="self" type="application/rss+xml"/><item><title>Managed Resources</title><link>https://deploy-preview-1062--crossplane.netlify.app/v2.0-preview/managed-resources/managed-resources/</link><pubDate/><guid>https://deploy-preview-1062--crossplane.netlify.app/v2.0-preview/managed-resources/managed-resources/</guid><description>&lt;p>A &lt;em>managed resource&lt;/em> (&lt;code>MR&lt;/code>) represents an external service in a Provider. When
users create a new managed resource, the Provider reacts by creating an external
resource inside the Provider&amp;rsquo;s environment. Every external service managed by
Crossplane maps to a managed resource.&lt;/p>
&lt;div class="admonition note d-flex flex-column mx-4 p-0">
&lt;div class="admonition-title">
&lt;svg class="bi flex-shrink-0" role="img" aria-label="note:">&lt;use
xlink:href="#info"/>&lt;/svg>
&lt;span class="ps-1">Note&lt;/span>
&lt;/div>
&lt;div class="admonition-content">
Crossplane calls the object inside Kubernetes a &lt;em>managed resource&lt;/em> and the
external object inside the Provider an &lt;em>external resource&lt;/em>.
&lt;/div>
&lt;/div>
&lt;p>Examples of managed resources include:&lt;/p></description></item><item><title>Usages</title><link>https://deploy-preview-1062--crossplane.netlify.app/v2.0-preview/managed-resources/usages/</link><pubDate/><guid>https://deploy-preview-1062--crossplane.netlify.app/v2.0-preview/managed-resources/usages/</guid><description>&lt;p>A &lt;code>Usage&lt;/code> indicates a resource is in use. Two main use cases for Usages are
as follows:&lt;/p>
&lt;ol>
&lt;li>Protecting a resource from accidental deletion.&lt;/li>
&lt;li>Deletion ordering by ensuring that a resource isn&amp;rsquo;t deleted before the
deletion of its dependent resources.&lt;/li>
&lt;/ol>
&lt;p>See the section &lt;a href="#usage-for-deletion-protection">Usage for Deletion Protection&lt;/a> for the
first use case and the section &lt;a href="#usage-for-deletion-ordering">Usage for Deletion Ordering&lt;/a>
for the second one.&lt;/p>
&lt;h2 id="enable-usages">Enable usages &lt;a class="anchor-link" id="enable-usages" href="#enable-usages" aria-label="Link to this section: Enable usages">&lt;/a>&lt;/h2>
&lt;!-- vale write-good.Passive = NO -->
&lt;p>Usages are a beta feature. Beta features are enabled by default.&lt;/p></description></item></channel></rss>