Merge branch 'odh_release-0.3' into conflict_fix_0.3

Signed-off-by: Jooho Lee <[email protected]>

Author: Jooho

.github/ISSUE_TEMPLATE/blank_issue.md

@@ -0,0 +1,8 @@
+---
+name: Blank Issue
+about: Create a new issue from scratch
+title: ''
+labels: needs-triage
+assignees: ''
+
+---

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,27 @@
+---
+name: Bug Report
+about: Report a bug you encountered
+title: ''
+labels: kind/bug, needs-triage
+assignees: ''
+
+---
+
+<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
+
+-->
+
+**What happened**:
+
+**What you expected to happen**:
+
+**How to reproduce it (as minimally and precisely as possible)**:
+
+**Anything else we need to know?**:
+
+**Environment**:
+- Kubernetes version (use `kubectl version`):
+- llm-d-scheduler version (use `git describe --tags --dirty --always` if you built from source, or specify the tag if you used a tagged version or image):
+- Cloud provider or hardware configuration:
+- Install tools:
+- Others:

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: false

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,14 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: needs-triage
+assignees: ''
+
+---
+
+<!-- Please only use this template for submitting enhancement requests -->
+
+**What would you like to be added**:
+
+**Why is this needed**:

.github/ISSUE_TEMPLATE/new-release.md

@@ -0,0 +1,141 @@
+---
+name: New Release
+about: Propose a new release
+title: Release v0.x.0
+labels: ''
+assignees: ''
+
+---
+
+- [Introduction](#introduction)
+- [Prerequisites](#prerequisites)
+- [Release Process](#release-process)
+- [Announce the Release](#announce-the-release)
+- [Final Steps](#final-steps)
+
+## Introduction
+
+This document defines the process for releasing llm-d-inference-scheduler.
+
+## Prerequisites
+
+1. Permissions to push to the llm-d-inference-scheduler repository.
+
+2. Set the required environment variables based on the expected release number:
+
+   ```shell
+   export MAJOR=0
+   export MINOR=1
+   export PATCH=0
+   export REMOTE=origin
+   ```
+
+3. If creating a release candidate, set the release candidate number.
+
+   ```shell
+   export RC=1
+   ```
+
+## Release Process
+
+1. If needed, clone the llm-d-inference-scheduler [repo].
+
+   ```shell
+   git clone -o ${REMOTE} [email protected]:llm-d/llm-d-inference-scheduler.git
+   ```
+
+2. If you already have the repo cloned, ensure it’s up-to-date and your local branch is clean.
+
+3. Release Branch Handling:
+   - For a Release Candidate:
+     Create a new release branch from the `main` branch. The branch should be named `release-${MAJOR}.${MINOR}`, for example, `release-0.1`:
+
+     ```shell
+     git checkout -b release-${MAJOR}.${MINOR}
+     ```
+
+   - For a Major, Minor or Patch Release:
+     A release branch should already exist. In this case, check out the existing branch:
+
+     ```shell
+     git checkout -b release-${MAJOR}.${MINOR} ${REMOTE}/release-${MAJOR}.${MINOR}
+     ```
+
+4. Update release-specific content, generate release artifacts, and stage the changes.
+
+5. Sign, commit, and push the changes to the `llm-d-inference-scheduler` repo.
+
+   For a release candidate:
+
+    ```shell
+    git commit -s -m "Updates artifacts for v${MAJOR}.${MINOR}.${PATCH}-rc.${RC} release"
+    ```
+
+   For a major, minor or patch release:
+
+    ```shell
+    git commit -s -m "Updates artifacts for v${MAJOR}.${MINOR}.${PATCH} release"
+    ```
+
+6. Push your release branch to the llm-d-inference-scheduler remote.
+
+    ```shell
+    git push ${REMOTE} release-${MAJOR}.${MINOR}
+    ```
+
+7. Tag the head of your release branch with the number.
+
+   For a release candidate:
+
+    ```shell
+    git tag -s -a v${MAJOR}.${MINOR}.${PATCH}-rc.${RC} -m 'llm-d-inference-scheduler v${MAJOR}.${MINOR}.${PATCH}-rc.${RC} Release Candidate'
+    ```
+
+   For a major, minor or patch release:
+
+    ```shell
+    git tag -s -a v${MAJOR}.${MINOR}.${PATCH} -m 'llm-d-inference-scheduler v${MAJOR}.${MINOR}.${PATCH} Release'
+    ```
+
+8. Push the tag to the llm-d-inference-scheduler repo.
+
+   For a release candidate:
+
+    ```shell
+    git push ${REMOTE} v${MAJOR}.${MINOR}.${PATCH}-rc.${RC}
+    ```
+
+   For a major, minor or patch release:
+
+    ```shell
+    git push ${REMOTE} v${MAJOR}.${MINOR}.${PATCH}
+    ```
+
+9. Pushing the tag triggers CI action to build and publish the container image to the [ghcr registry].
+10. Test the steps in the tagged quickstart guide after the PR merges. TODO add e2e tests! <!-- link to an e2e tests once we have such one -->
+11. Create a [new release]:
+    1. Choose the tag that you created for the release.
+    2. Use the tag as the release title, i.e. `v0.1.0` refer to previous release for the content of the release body.
+    3. Click "Generate release notes" and preview the release body.
+    4. Go to Gateway Inference Extension latest release and make sure to include the highlights in llm-d-inference-scheduler as well.
+    5. If this is a release candidate, select the "This is a pre-release" checkbox.
+12. If you find any bugs in this process, create an [issue].
+
+## Announce the Release
+
+Use the following steps to announce the release.
+
+1. Send an announcement email to `[email protected]` with the subject:
+
+   ```shell
+   [ANNOUNCE] llm-d-inference-scheduler v${MAJOR}.${MINOR}.${PATCH} is released
+   ```
+
+2. Add a link to the final release in this issue.
+
+3. Close this issue.
+
+[repo]: https://github.com/llm-d/llm-d-inference-scheduler
+[ghcr registry]: https://github.com/llm-d/llm-d-inference-scheduler/pkgs/container/llm-d-inference-scheduler
+[new release]: https://github.com/llm-d/llm-d-inference-scheduler/releases/new
+[issue]: https://github.com/llm-d/llm-d-inference-scheduler/issues/new/choose

.github/actions/docker-build-and-push/action.yml

@@ -13,6 +13,9 @@ inputs:
   registry:
     required: true
     description: Container registry (e.g., ghcr.io/llm-d)
+  prerelease:
+    required: true
+    description: indicates whether or not this is a pre-release (not a release) build
 runs:
   using: "composite"
   steps:
@@ -32,9 +35,13 @@ runs:
 
     - name: Build image and push
       run: |
+        if [[ ${{ inputs.prerelease }} == "true" ]]; then
+          LATEST_TAG=""
+        else
+          LATEST_TAG="-t ${{ inputs.registry }}/${{ inputs.image-name }}:latest"
+        fi
         docker buildx build \
           --platform linux/amd64,linux/arm64 \
           -t ${{ inputs.registry }}/${{ inputs.image-name }}:${{ inputs.tag }} \
-          -t ${{ inputs.registry }}/${{ inputs.image-name }}:latest \
-          --push .
+          ${LATEST_TAG} --push .
       shell: bash

.github/dependabot.yml

@@ -29,8 +29,8 @@ updates:
     schedule:
       interval: "weekly"
     labels:
-      - "ci"
       - "dependencies"
+      - "release-note-none"
     commit-message:
       prefix: "deps(actions)"
 
@@ -41,6 +41,5 @@ updates:
       interval: "weekly"
     labels:
       - "dependencies"
-      - "docker"
     commit-message:
       prefix: "deps(docker)"

.github/workflows/check-typos.yaml

@@ -0,0 +1,17 @@
+name: Check Typos
+
+on:
+  pull_request:
+  push:
+
+jobs:
+  typos:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v5
+
+      - name: Check typos
+        uses: crate-ci/[email protected]
+

.github/workflows/ci-pr-checks.yaml

@@ -11,7 +11,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout source
-        uses: actions/checkout@v4
+        uses: actions/checkout@v5
 
       - name: Sanity check repo contents
         run: ls -la

.github/workflows/ci-release.yaml

@@ -12,7 +12,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout source
-        uses: actions/checkout@v4
+        uses: actions/checkout@v5
 
       - name: Set project name from repository
         id: version
@@ -33,6 +33,8 @@ jobs:
           else
             echo "tag=latest" >> "$GITHUB_OUTPUT"
           fi
+          PRE_RELEASE=${{ github.event_name != 'release' || github.event.release.prerelease }}
+          echo "prerelease=${PRE_RELEASE}" >> "$GITHUB_OUTPUT"
         shell: bash
 
       - name: Build and push image
@@ -42,6 +44,7 @@ jobs:
           image-name: ${{ steps.version.outputs.project_name }}
           registry: ghcr.io/llm-d
           github-token: ${{ secrets.GHCR_TOKEN }}
+          prerelease: ${{ steps.tag.outputs.prerelease }}
 
       - name: Run Trivy scan
         uses: ./.github/actions/trivy-scan