-
Notifications
You must be signed in to change notification settings - Fork 458
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add doc about Shoot status #2765
Conversation
Signed-off-by: ialidzhikov <i.alidjikov@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very nice doc! Thanks for picking this up ❤️
/lgtm
I think this doc also deserves a release note to make end users aware of it (some already asked for such documentation), don't you think 😉 |
Thank you for pointing out "kind/documentation" task. I now added a relnote. :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just two comments, although already merged. Thanks for the nice document!
- `ERR_INFRA_DEPENDENCIES` - indicates that the last error occurred due to dependent objects on the infrastructure level | ||
- `ERR_INFRA_RESOURCES_DEPLETED` - indicates that the last error occurred due to depleted resource in the infrastructure | ||
- `ERR_CLEANUP_CLUSTER_RESOURCES` - indicates that the last error occurred due to resources in the cluster that are stuck in deletion | ||
- `ERR_CONFIGURATION_PROBLEM` - indicates that the last error occurred due a configuration problem |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- `ERR_CONFIGURATION_PROBLEM` - indicates that the last error occurred due a configuration problem | |
- `ERR_CONFIGURATION_PROBLEM` - indicates that the last error occurred due to a configuration problem |
| `type` | Name of the condition. | | ||
| `status` | Indicates whether the condition is applicable, with possible values `True`, `False`, `Unknown`, or `Progressing`. | | ||
| `lastTransitionTime` | Timestamp for when the condition last transitioned from one status to another. | | ||
| `lastUpdateTime` | Timestamp for when the condition was updated. | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| `lastUpdateTime` | Timestamp for when the condition was updated. | | |
| `lastUpdateTime` | Timestamp for when the condition was updated. Usually changes when `reason` or `message` in condition is updated | |
How to categorize this PR?
/area documentation
/kind task
/priority normal
What this PR does / why we need it:
Add documentation about the Shoot status.
Release note: