We want to continue serving the v2.0-preview content (there are a
lot of links to it floating around out there), but it is very
confusing to see it in the drop down. This commit marks the v2.0-preview
version as hidden from the version drop down selector, while still
serving them in the case someone uses the direct URL.
Signed-off-by: Jared Watts <jbw976@gmail.com>
For this commit, we looked at all guides/content from v1.20 and
copied over any content that is still relevant for v2.0 but was
not included in the huge refactor of the v2 docs.
* change logs guide
* Argo CD guide
* import existing resources guide
* self-signed certificates guide
* image configs (missing details in master)
Signed-off-by: Jared Watts <jbw976@gmail.com>
The rewrite feature of `ImageConfig` was merged around the time v2 work started,
and as a result the docs for it were lost in v2. Re-introduce the missing docs
from 1.20.
Signed-off-by: Adam Wolfe Gordon <awg@upbound.io>
The key point I want to get across with this guide is:
1. Who can upgrade (what breaking changes we made)
2. That there's no tooling to automate migration yet
3. That you can upgrade and start using v2 features anyway
Signed-off-by: Nic Cope <nicc@rk0n.org>
* Keep them concise (~50 chars) for rendering on index pages
* Adjust them for clarity and accuracy
* Add descriptions to pages that were missing them
Signed-off-by: Nic Cope <nicc@rk0n.org>
* Realtime compositions are beta now
Signed-off-by: Nic Cope <nicc@rk0n.org>
* Composition functions don't run on delete
Signed-off-by: Nic Cope <nicc@rk0n.org>
* You can't patch XR metadata
Signed-off-by: Nic Cope <nicc@rk0n.org>
* Document function response cache
Signed-off-by: Nic Cope <nicc@rk0n.org>
---------
Signed-off-by: Nic Cope <nicc@rk0n.org>
* Drop note about (only) AWS MRs supporting v2
A few of the other providers like GCP and Azure now do. The rest will
fast follow.
Also, it's not misleading to say the others don't support v2. That reads
like they're incompatible, which they're not. They're just not
namespaced yet.
Signed-off-by: Nic Cope <nicc@rk0n.org>
* Only use modern namespaced provider-upjet-aws MRs
* Make sure they're using v2.0.0 providers
* Make sure they use m.example.org style API groups
* Make sure they're namespaced
Signed-off-by: Nic Cope <nicc@rk0n.org>
---------
Signed-off-by: Nic Cope <nicc@rk0n.org>
Large Crossplane providers install hundreds of CRDs consuming significant API
server resources, even when users only need a few resource types. The new
alpha ManagedResourceDefinition (MRD) and ManagedResourceActivationPolicy
(MRAP) features in Crossplane v2.0+ solve this by enabling selective
activation of provider resources, but lack user-facing documentation.
This change adds complete documentation covering both concepts and practical
implementation. The MRD concepts page explains the CRD scaling problem and
selective activation approach. The MRAP concepts page details pattern-based
activation strategies and multiple policy coordination. Two how-to guides
provide end-to-end workflows: one for users wanting to reduce CRD overhead
through selective activation, and another for provider developers implementing
safe-start capability. The user guide was tested with simulated MRDs to verify
the activation workflow and troubleshooting steps.
Signed-off-by: Nic Cope <nicc@rk0n.org>
Jay Miracola