Repository navigation

Consider providing statusz / flagz endpoints #3110

Open

Labels

lifecycle/frozen

opened

on Feb 10, 2025

There are KEPs in k/k to introduce Statusz & Flagz to Kubernetes components:

I'm wondering if we want to have something similar for CR-based controllers (e.g. by providing utils for this)

k8s-triage-robot commented on May 11, 2025
k8s-triage-robot
on May 11, 2025
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied

After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied

After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale

Close this issue with /close

Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale
k8s-ci-robot
added
lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
on May 11, 2025
sbueringer commented on May 12, 2025
sbueringer
on May 12, 2025
MemberAuthor
/lifecycle frozen
k8s-ci-robot
added
lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.
and removed
lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
on May 12, 2025

to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

Labels

lifecycle/frozen

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests