docs: document Kubernetes Events on LLMInferenceService readiness transitions
- Dominant language
- MDX
- Stars
- 113
- Forks
- 193
- Avg merge
- 5d 20h
- Merged PRs (30d)
- 3
Description
## Summary
KServe v0.19 added Kubernetes Event emission on LLMInferenceService readiness state transitions. This provides push-based availability signals for operators and monitoring systems. No documentation exists for this feature.
## What needs to be documented
- `Normal` event with reason `LLMInferenceServiceReady` emitted on NotReady → Ready transition
- `Warning` event with reason `LLMInferenceServiceNotReady` emitted on Ready → NotReady transition (includes failing conditions list)
- `Warning` event with reason `UpdateFailed` on status update errors
- How operators can consume these events for alerting and monitoring
- Example `kubectl get events` output showing the events
## Related PR
- https://github.com/kserve/kserve/pull/5437
## Since
KServe v0.19
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the KServe v0.19 readiness transition behavior and related PR #5437, then locate the website section covering LLMInferenceService status or operations. Document the three event types, how operators can consume them for monitoring, and a representative kubectl get events example; done means all listed transitions and failure behavior are explained.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- Half a day
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 74/100