Skip to content

Revisit Release Process #2954

Open
Open

Description

@rexagod

There are some quirks (and leftovers, see @bhope's comment below) that need to be addressed: https://github.com/kubernetes/kube-state-metrics/actions/runs/25553160051/job/75005673130?pr=2949.

cc @mrueg

Activity

  1. added
    kind/bugCategorizes issue or PR as related to a bug.
    on May 11, 2026
  2. added
    needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.
    on May 11, 2026
  3. k8s-ci-robot commented on May 11, 2026

    @k8s-ci-robot
    Contributor

    This issue is currently awaiting triage.

    If kube-state-metrics contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

    The triage/accepted label can be added by org members by writing /triage accepted in a comment.

    Details

    Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

  4. bhope commented on May 14, 2026

    @bhope
    Member

    #2756 had some nice groundwork. The data.yaml script was added via #2769 but was never hooked into automation, and the kpromo pr step post-tag is still fully manual. I think we can close most of this gap with two focused workflow_dispatch actions.

  5. changed the title [-]Redo Release Process[/-] [+]RevisitRelease Process[/+] on May 15, 2026
  6. changed the title [-]RevisitRelease Process[/-] [+]Revisit Release Process[/+] on May 15, 2026
  7. rexagod commented on May 15, 2026

    @rexagod
    MemberAuthor

    Right, we'd be better off driving the effort over the line than consider alternatives, primarily since the tooling is tailored to our use cases.

    @Rishab87 would you be interested in driving this again? I can help with the reviews in a better capacity now as kubernetes/enhancements#4785 has stabilized to a degree at this point.

  8. moved this from Needs Triage to Needs Review (PR) or Response (Issue) in SIG Instrumentationon May 15, 2026
  9. Rishab87 commented on May 16, 2026

    @Rishab87
    Contributor

    @rexagod sure, happy to help!

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugCategorizes issue or PR as related to a bug.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions