Release v0.5.0

[danielvegamyhre]

Release Checklist

• All OWNERS must LGTM the release proposal
• Verify that the changelog in this issue is up-to-date
• 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 things like README, deployment templates, docs, configuration, test/e2e flags.
  Submit a PR against the release branch:
• An OWNER prepares a draft release
  • Write the change log into the draft release.
  • Run
    make artifacts IMAGE_REGISTRY=registry.k8s.io/jobset 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-jobset/jobset:$VERSION
• Submit a PR against k8s.io,
  updating k8s.gcr.io/images/k8s-staging-jobset/images.yaml to
  promote the container images
  to production:
• Wait for the PR to be merged and verify that the image registry.k8s.io/jobset/jobset:$VERSION is available.
• Publish the draft release prepared at the Github releases page.
• Add a link to the tagged release in this issue:
• Send an announcement email to [email protected], [email protected] and [email protected] with the subject [ANNOUNCE] JobSet $VERSION is released
• Add a link to the release announcement in this issue:
• For a major or minor release, update README.md and docs/setup/install.md
  in main branch:
• For a major or minor release, 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.
• Close this issue

Changelog

Highlights

• JobSet TTL support added in feat: add support for ttl cleanup for finished jobsets #443
• Docsite is live at https://jobset.sigs.k8s.io/ with updated documentation and examples.
• Include first failed job name in event emitted when JobSet fails, to speed up the debugging process for large complex workloads Include first failed job name in event emitted when JobSet fails, as well as the JobSet failure condition #477
• Lower default resource request for JobSet controller manager so it fits on default cloud CPU VMs, but keep high limit to support maximum performance Lower default resource request for controller manager but keep high limit #480
• Perform only 1 JobSet status update per reconcile attempt to reduce pressure on k8s apiserver Call Status.Update once in each reconcile attempt #494
• Introduced MangedBy field to the JobSet spec to enable Multi-Kueue support

See release notes for full change log.

[ahg-g]

/lgtm

[danielvegamyhre]

Release published: https://github.com/kubernetes-sigs/jobset/releases/tag/v0.5.0

[danielvegamyhre]

Announcement email: https://groups.google.com/a/kubernetes.io/g/wg-batch/c/UG3Z_54KpBc/m/I5-VykT0AQAJ