mirror of
https://github.com/k3s-io/kubernetes.git
synced 2025-08-08 03:33:56 +00:00
fix: add the bug as a known issue o on the v1.26 release note
This commit is contained in:
parent
2bed67d0f1
commit
02d8fc28fa
@ -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)
|
||||
@ -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.26.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.26.1.
|
||||
|
||||
## Urgent Upgrade Notes
|
||||
|
||||
### (No, really, you MUST read this before you upgrade)
|
||||
|
Loading…
Reference in New Issue
Block a user