Skip to content

Commit

Permalink
fix: add the bug as a known issue o on the v1.26 release note
Browse files Browse the repository at this point in the history
Change-Id: I4d38ed15c492abbfafda770fcb6aed2b37e0ac24
  • Loading branch information
sanposhiho authored and alculquicondor committed Apr 13, 2023
1 parent 845ba3e commit 1601bb7
Showing 1 changed file with 11 additions and 0 deletions.
11 changes: 11 additions & 0 deletions CHANGELOG/CHANGELOG-1.27.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,8 @@
- [Node Binaries](#node-binaries)
- [Container Images](#container-images)
- [Changelog since v1.26.0](#changelog-since-v1260)
- [Known Issues](#known-issues)
- [The PreEnqueue extension point doesn't work in backoffQ](#the-preEnqueue-extension-point-doesnt-work-for-pods-going-to-activeq-through-backoffq)
- [Urgent Upgrade Notes](#urgent-upgrade-notes)
- [(No, really, you MUST read this before you upgrade)](#no-really-you-must-read-this-before-you-upgrade)
- [Changes by Kind](#changes-by-kind)
Expand Down Expand Up @@ -198,6 +200,15 @@ name | architectures

## Changelog since v1.26.0

## Known Issues

### The PreEnqueue extension point doesn't work for Pods going to activeQ through backoffQ

In v1.27.0, we've found the bug that the PreEnqueue extension point doesn't work for Pods going to activeQ through backoffQ.
It doesn't affect any of the vanilla Kubernetes behavior, but, may break custom PreEnqueue plugins.

The cause PR is [reverted](https://github.com/kubernetes/kubernetes/pull/117194) by v1.27.1.

## Urgent Upgrade Notes

### (No, really, you MUST read this before you upgrade)
Expand Down

0 comments on commit 1601bb7

Please sign in to comment.