Release v0.1.0

[alculquicondor]

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: Match release-0.1 tags in manifests #211
• An OWNER prepares a draft release
  • Create a draft release at Github releases page.
  • Write the change log into the draft release.
  • Run
    make artifacts IMAGE_REGISTRY=k8s.gcr.io/kueue GIT_TAG=$VERSION
    to generate the artifacts and upload the files in the artifacts folder
    to the draft release.
• An OWNER runs
  git tag -s $VERSION
  and inserts the changelog into the tag description.
• 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 k8s.gcr.io/images/k8s-staging-kueue/images.yaml to promote the container images to production.
• Wait for the PR to be merged and verify that the image k8s.gcr.io/kueue/kueue:$VERSION is available.
• Publish the draft release prepared at the Github releases page.
• Add a link to the tagged release in this issue https://github.com/kubernetes-sigs/kueue/releases/tag/v0.1.0
• Send an announcement email to sig-scheduling@kubernetes.io and wg-batch@kubernetes.io with the subject [ANNOUNCE] kueue $VERSION is released
• Add a link to the release announcement in this issue https://groups.google.com/a/kubernetes.io/g/wg-batch/c/-gZOrSnwDV4
• For a major or minor release, update docs/setup/install.md in main branch.
  • Update references on deployment yamls.
  • Wait for the PR to be merged Add installation instructions for a released version #215
• For a major 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

First release of Kueue, a Kubernetes native set of APIs and controllers for job queueing.

The release includes:

• The API group kueue.x-k8s.io/v1alpha1 that includes the ClusterQueue, Queue, ResourceFlavor and Workload APIs.
• A set of controllers that support quota-based job queuing, with:
  • Resource sharing: unused resources can be borrowed to other tenants.
  • Resource flavors and fungibility: you can define multiple flavors or variants of a resource. Jobs are assigned to flavors that are still available.
  • Two queueing strategies: StrictFIFO and BestEffortFIFO.
• Support for the Kubernetes batch/v1.Job API.
• The Workload API abstraction allows you to integrate a third-party job API with Kueue.
• Documentation available at https://sigs.k8s.io/kueue/docs

[ArangoGutierrez]

PIN this one, now that the umbrella is complete

[alculquicondor]

Let's start. Can OWNERS +1?

[denkensk]

+1

[ArangoGutierrez]

/lgtm

[denkensk]

/lgtm

[ahg-g]

+1

[ArangoGutierrez]

[eduardo@fedora-workstation kueue]$ skopeo list-tags docker://k8s.gcr.io/kueue/kueue
{
    "Repository": "k8s.gcr.io/kueue/kueue",
    "Tags": [
        "sha256-430bb4d26a05e4de56e3e10d8bc5ebb8de28f77d575d99a4cacc8edadcf7567b.sig",
        "v0.1",
        "v0.1.0"
    ]
}

[ahg-g]

Nice! congrats on the first release :)

[alculquicondor]

Next, I'll send a PR to the template to link to sample PRs.

/close

[k8s-ci-robot]

@alculquicondor: Closing this issue.

In response to this:

Next, I'll send a PR to the template to link to sample PRs.

/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.