Google Git
Sign in
apache / yunikorn-release / dff1b38bcafaf8affc6bffedaba4963e6d119140
commitdff1b38bcafaf8affc6bffedaba4963e6d119140[log] [tgz]
authorKrishna Birla <krishna.birla@cloudera.com>Fri Jan 20 16:49:09 2023 -0600
committerCraig Condit <ccondit@apache.org>Fri Jan 20 16:49:09 2023 -0600
tree3fbc6bf4d2aafd923a6c3826cb27c089d901b8f6
parent8152220200ade777fb36b206ec62e7727cc730af [diff]
[YUNIKORN-1541] Fix helm upgrade when host network is enabled (#125)

If the admission controller is deployed with hostNetwork, use the Recreate strategy
for the deployment to avoid host port conflicts on upgrade.

Closes: #125

Signed-off-by: Craig Condit <ccondit@apache.org>
2 files changed
tree: 3fbc6bf4d2aafd923a6c3826cb27c089d901b8f6
  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.