Skip to content

Define all of the existing condition types and reasons #4651

@rikatz

Description

@rikatz

What would you like to be added:

Document all of the existing Gateway API condition types and reasons.

Why this is needed:
We don't have a centralized place today with what each Condition Type, Status and Reason means (other than on the API), and it would be good for users to have a place on the documentation to understand what each condition means

Metadata

Metadata

Assignees

Labels

kind/documentationCategorizes issue or PR as related to documentation.

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions