crossplane / crossplane/docs

Provide details about standard conditions used by Crossplane

Open
#750 2 comments 1 reaction 1 assignee Claimed by @plumbis View on GitHub
bug pending-reporter
Dominant language
SCSS
Stars
60
Forks
163
Avg merge
15h 20m
Merged PRs (30d)
9

Description

### URL

https://docs.crossplane.io/latest/concepts/managed-resources/#conditions

### What's Wrong?

Discussed a bit in this PR: https://github.com/crossplane/crossplane/pull/5453#discussion_r1562242295

Our docs focus on the possible specific reasons for each condition, but don't seem to focus on the high level conditions themselves, e.g. `Ready` and `Synced`. What are their intent and semantics, what scenarios do they cover?

@negz quick write-up that is useful:

> Today we have the following status conditions:
>
> * Ready - The external resource is ready to use, (where applicable) according to its API.
> * Synced - The managed resource's desired state has been successfully applied to the external resource.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.