posit-dev / posit-dev/team-operator
team-operator: Add Kubernetes events for state transitions
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10
- Forks
- 1
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 4
Description
Summary
Emit Kubernetes events on lifecycle transitions, dependency waits, and reconcile failures so customer admins can see operator state via kubectl describe.
Acceptance Criteria
-
Normalevents on first-time transitions:Created,Ready,Updated -
Warningevents on recoverable problems:DependencyPending,WaitingForSecret,WaitingForCRD -
Warningevents on hard failures:ReconcileError,ConfigInvalid,AuthenticationFailed - Sub-dispatch failures emit on the per-product CR, not on Site
-
--observability-events-enabled=falsesuppresses all emission
Design: https://github.com/posit-dev/team-operator/issues/7#issuecomment-4379428412 (Phase 2 section)
Phase 2 of three. Phase 1: #7. Phase 3: #133.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Phase 2 section of the linked design and compare it with the Phase 1 work in #7. Trace lifecycle transitions, dependency waits, reconcile failures, sub-dispatch targets, and the observability-events flag. Done means the listed Normal and Warning events appear on the correct resources and disabling the flag suppresses all emission.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100