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>
Added introductory sentence before Operations diagram to match the pattern
used for other diagrams. Explains the SSL certificate monitoring scenario
that the diagram illustrates, connecting the use case to the visual representation.
Signed-off-by: Nic Cope <nicc@rk0n.org>
Fixed Vale linter disable comment that was interrupting the ordered list
in the "Event handling" section of watchoperation.md. Moved the Vale
disable comments to wrap around the entire list instead of interrupting
it, which resolves the ordering numbering reset issue.
Signed-off-by: Nic Cope <nicc@rk0n.org>
Updated status field names in operation.md to match actual YAML
capitalization: conditions, failures, pipeline, appliedResourceRefs
instead of the capitalized versions.
Signed-off-by: Nic Cope <nicc@rk0n.org>
Added a new troubleshooting item to operation.md documenting the common
error when Operations feature is not enabled and how to resolve it by
adding the --enable-operations flag to Crossplane's startup arguments.
Updated numbering for subsequent troubleshooting items accordingly.
Signed-off-by: Nic Cope <nicc@rk0n.org>
Changed 'SSL Monitor Operation API' to 'SSL Monitor Operation' in the
mermaid diagram to prevent text truncation that was showing as
'SSL Monitor Operation AP' in the rendered output.
Signed-off-by: Nic Cope <nicc@rk0n.org>
Add backticks to all status field names (Conditions, Succeeded,
ValidPipeline, Failures, Pipeline) to match AppliedResourceRefs
per Jared's feedback in PR #956.
Signed-off-by: Nic Cope <nicc@rk0n.org>
Apply backticks to Kubernetes resource types (Operation, Ingress,
ClusterRole, Job) to follow documentation style conventions
for API objects per Jared's feedback in PR #956.
Signed-off-by: Nic Cope <nicc@rk0n.org>
Change from plain code block to console with disabled line numbers and copy
functionality per docs engineer feedback. Improves visual presentation of the
cron schedule diagram.
Signed-off-by: Nic Cope <nicc@rk0n.org>
Add critical guidance for WatchOperation functions that request resources
dynamically. Functions must return consistent requirements across iterations
for proper stabilization. Include working example with error handling.
Signed-off-by: Nic Cope <nicc@rk0n.org>
Add Test an operation section to Operations concept documentation showing how to
preview Operations locally using the CLI. Follows same pattern as composition
render documentation with usage examples and output format.
Signed-off-by: Nic Cope <nicc@rk0n.org>
A lot of our content dirs had links to master when they shouldn't have.
These are now replaced with local links.
Signed-off-by: Nic Cope <nicc@rk0n.org>
Nic Cope
Jared Watts
twobiers
Jason Tang
Adam Wolfe Gordon
adrienfuss