Release v0.6.1

[tenzen-y]

Release Checklist

• OWNERS must LGTM the release proposal.
  At least two for minor or major releases. At least one for a patch release.
• Verify that the changelog in this issue and the CHANGELOG folder is up-to-date
  • Use https://github.com/kubernetes/release/tree/master/cmd/release-notes to gather notes.
    Example: release-notes --org kubernetes-sigs --repo kueue --branch release-0.3 --start-sha 4a0ebe7a3c5f2775cdf5fc7d60c23225660f8702 --end-sha a51cf138afe65677f5f5c97f8f8b1bc4887f73d2 --dependencies=false --required-author=""
• For major or minor releases (v$MAJ.$MIN.0), create a new release branch.
  • An OWNER creates a vanilla release branch with
    git branch release-$MAJ.$MIN main
  • An OWNER pushes the new release branch with
    git push release-$MAJ.$MIN
• Update the release branch:
  • Update RELEASE_BRANCH and RELEASE_VERSION in Makefile and run make prepare-release-branch
  • Update the CHANGELOG
  • Submit a pull request with the changes: Prepare release v0.6.1 #1847
• An OWNER prepares a draft release
  • Write the change log into the draft release.
  • Run
    make artifacts IMAGE_REGISTRY=registry.k8s.io/kueue GIT_TAG=$VERSION
    to generate the artifacts and upload the files in the artifacts folder
    to the draft release.
• An OWNER creates a signed tag running
  git tag -s $VERSION
  and inserts the changelog into the tag description.
  To perform this step, you need a PGP key registered on github.
• An OWNER pushes the tag with
  git push $VERSION
  • Triggers prow to build and publish a staging container image
    gcr.io/k8s-staging-kueue/kueue:$VERSION
• Submit a PR against k8s.io,
  updating registry.k8s.io/images/k8s-staging-kueue/images.yaml to
  promote the container images
  to production: Promote image for kueue v0.6.1 kubernetes/k8s.io#6578
• Wait for the PR to be merged and verify that the image registry.k8s.io/kueue/kueue:$VERSION is available.
• Publish the draft release prepared at the Github releases page.
  Link: https://github.com/kubernetes-sigs/kueue/releases/tag/v0.6.1
• Run the openvex action to generate openvex data. The action will add the file to the release artifacts.
• Run the SBOM action to generate the SBOM and add it to the release.
• For major or minor releases, merge the main branch into the website branch to publish the updated documentation.
• Send an announcement email to sig-scheduling@kubernetes.io and wg-batch@kubernetes.io with the subject [ANNOUNCE] kueue $VERSION is released. https://groups.google.com/a/kubernetes.io/g/wg-batch/c/gHCQETA8x2s
• Update the below files with respective values in main branch :
  • Latest version in README.md
  • Release notes in the CHANGELOG
  • version in site/config.toml
  • appVersion in charts/kueue/Chart.yaml
  • last-updated, last-reviewed, commit-hash, project-release, and distribution-points in SECURITY-INSIGHTS.yaml
  • Update latest version to v0.6.1 #1848
• For a major or minor release, prepare the repo for the next version:
  • create an unannotated devel tag in the
    main branch, on the first commit that gets merged after the release
    branch has been created (presumably the README update commit above), and, push the tag:
    DEVEL=v0.$(($MAJ+1)).0-devel; git tag $DEVEL main && git push $DEVEL
    This ensures that the devel builds on the main branch will have a meaningful version number.
  • Create a milestone for the next minor release and update prow to set it automatically for new PRs:
    

Changelog

Changes Since `v0.6.0`:

### Feature

- Added MultiKueue worker connection monitoring and reconnect. (#1809, @trasc)
- The Failed pods in a pod-group are finalized once a replacement pods are created. (#1801, @trasc)

### Bug or Regression

- Exclude Pod labels, preemptionPolicy and container images when determining whether pods in a pod group have the same shape. (#1760, @alculquicondor)
- Fix incorrect quota management when lendingLimit enabled in preemption (#1826, @kerthcet, @B1F030)
- Fix the configuration for the number of reconcilers for the Pod integration. It was only reconciling one group at a time. (#1837, @alculquicondor)
- Kueue visibility API is no longer installed by default. Users can install it via helm or applying the visibility-api.yaml artifact. (#1764, @trasc)
- WaitForPodsReady: Fix a bug that the requeueState isn't reset. (#1843, @tenzen-y)

### Other (Cleanup or Flake)

- Avoid API calls for admission attempts when Workload already has condition Admitted=false (#1845, @alculquicondor)
- Skip requeueing of Workloads when there is a status update for a ClusterQueue, saving on API calls for Workloads that were already attempted for admission. (#1832, @alculquicondor)

[tenzen-y]

@mimowo @alculquicondor Please let me know if there is any possible issues we should include in this release.

[alculquicondor]

Just #1845

[tenzen-y]

#1846 should be included in this.

[alculquicondor]

#1846 does not affect 0.6, right?

[tenzen-y]

#1846 does not affect 0.6, right?

Yes, that's right. I found it by @astefanutti's comment.

#1846 (comment)

[alculquicondor]

PTAL at release notes.

[tenzen-y]

PTAL at release notes.

I removed unnecessary spaces from release notes.
Could you perform a command to get the release note again?

[alculquicondor]

It looks like there was only one. Updated. And #1847 as well.

[tenzen-y]

It looks like there was only one. Updated. And #1847 as well.

LGTM!

[alculquicondor]

/close

[k8s-ci-robot]

@alculquicondor: Closing this issue.

In response to this:

/close

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/test-infra repository.