Skip to content

Conversation

andreaskaris
Copy link
Contributor

@andreaskaris andreaskaris commented Sep 9, 2025

Implements status conditions and component status tracking for the
Config custom resource to provide visibility into the reconciliation
state of managed components (ConfigMap, DaemonSets, CSIDriver, SCC).

  • Add ConfigComponentStatuses type with status for each component
  • Implement Progressing and Available conditions following Kubernetes
    conventions
  • Add event recording for status changes
  • Update controller with status subresource RBAC permissions
  • Add test coverage for all status states
  • Integrate status checks into lifecycle tests

The status system tracks individual component readiness and sets
overall conditions to indicate when the Config is progressing or
fully available.

@andreaskaris andreaskaris marked this pull request as draft September 9, 2025 16:03
frobware pushed a commit to frobware/bpfman-operator that referenced this pull request Sep 10, 2025
…s/component-update-ocp-bpfman-operator-bundle

chore(deps): update ocp-bpfman-operator-bundle to 7f70133
@andreaskaris andreaskaris force-pushed the conditions branch 2 times, most recently from f8e8458 to c3e3ac8 Compare September 10, 2025 13:08
@andreaskaris andreaskaris changed the title WIP: Conditions Add status tracking to Config resource WIP: Config follow-up: Conditions Add status tracking to Config resource Sep 10, 2025
@andreaskaris andreaskaris force-pushed the conditions branch 2 times, most recently from e3b5b5b to 26b91ff Compare September 14, 2025 13:41
Implements status conditions and component status tracking for the
Config custom resource to provide visibility into the reconciliation
state of managed components (ConfigMap, DaemonSets, CSIDriver, SCC).

- Add ConfigComponentStatuses type with status for each component
- Implement Progressing and Available conditions following Kubernetes
  conventions
- Add event recording for status changes
- Update controller with status subresource RBAC permissions
- Add test coverage for all status states
- Integrate status checks into lifecycle tests

The status system tracks individual component readiness and sets
overall conditions to indicate when the Config is progressing or
fully available.

Signed-off-by: Andreas Karis <[email protected]>
Signed-off-by: Andreas Karis <[email protected]>
Copy link
Contributor

mergify bot commented Sep 26, 2025

@andreaskaris, this pull request is now in conflict and requires a rebase.

@mergify mergify bot added the needs-rebase label Sep 26, 2025
Copy link

codecov bot commented Sep 26, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 0.00%. Comparing base (f00edc4) to head (8034a9b).
⚠️ Report is 5 commits behind head on main.

Additional details and impacted files
@@     Coverage Diff     @@
##   main   #474   +/-   ##
===========================
===========================

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant