Google GitGoogle Git
Sign in
apache/yunikorn-release/fb48fc2789ac5caef0d8bc2ed93847a84d1c927d
commit
fb48fc2789ac5caef0d8bc2ed93847a84d1c927d
[log]
author
Wilfred Spiegelenburg <wilfreds@apache.org>
Tue Jul 22 11:23:41 2025 +1000
committer
Wilfred Spiegelenburg <wilfreds@apache.org>
Tue Jul 22 11:23:41 2025 +1000
tree
7e4a4a41f1b2ed905ae1f31296a3e31be213d77a
parent
358b533ea4bffa849e4da329fd9cf9d4bbce7d01 [diff]
[YUNIKORN-3081] Remove pods get from admission controller cluster role (#199)

The admission controller code does not reference the pod retrieval. That
means it should not need the permission on a role.

Closes: #199

Signed-off-by: Wilfred Spiegelenburg <wilfreds@apache.org>
2 files changed
tree: 7e4a4a41f1b2ed905ae1f31296a3e31be213d77a
  1. .github/
  2. helm-charts/
  3. perf-tools/
  4. release-top-level-artifacts/
  5. tools/
  6. .asf.yaml
  7. .gitignore
  8. check_license.sh
  9. go.mod
  10. go.sum
  11. LICENSE
  12. NOTICE
  13. README.md
README.md

Apache YuniKorn Release

pre-commit

This project provides the instructions and tools needed to generate Apache YuniKorn release artifacts. Reference:

Release Procedure

A simplified procedure:

  • Create a release branch in all git repos, such as branch-0.8
  • Stabilize the release
  • Create a tag and prepare to generate the release, e.g v0.8.0
  • Run the release tool to generate source code tarball, checksum and signature
  • Upload tarball, signature and checksum as a release candidate
  • Start a voting thread for the project
  • Publish the release (source code, helm chart and pre-build images)
  • Update the website

The full procedure is documented in the release procedure.