github/kubernetes
4
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

CHANGELOG-1.27: Add note for AWS in-tree provider removal

Browse Source 
Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
This commit is contained in:
Marko Mudrinić
2023-06-27 12:46:25 +02:00
parent 9d50c0a025
commit b0f694f50a
1 changed files with 14 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

27
CHANGELOG/CHANGELOG-1.27.md
View File

@@ -593,20 +593,21 @@ The cause PR is [reverted](https://github.com/kubernetes/kubernetes/pull/117194)
(The feature became GA in 1.23 and the gate was removed for all other (The feature became GA in 1.23 and the gate was removed for all other
components several releases ago.) If you were still manually components several releases ago.) If you were still manually
enabling it you must stop now.' ([#116255](https://github.com/kubernetes/kubernetes/pull/116255), [@danwinship](https://github.com/danwinship)) enabling it you must stop now.' ([#116255](https://github.com/kubernetes/kubernetes/pull/116255), [@danwinship](https://github.com/danwinship))
- Give terminal phase correctly to all pods that will not be restarted. - Give terminal phase correctly to all pods that will not be restarted.
In particular, assign Failed phase to pods which are deleted while pending. Also, assign a terminal
phase (Succeeded or Failed, depending on the exit statuses of the pod containers) to pods which
are deleted while running.
In particular, assign Failed phase to pods which are deleted while pending. Also, assign a terminal This fixes the issue for jobs using pod failure policy (with JobPodFailurePolicy and PodDisruptionConditions
phase (Succeeded or Failed, depending on the exit statuses of the pod containers) to pods which feature gates enabled) that their pods could get stuck in the pending phase when deleted.
are deleted while running.
Users who maintain controllers which relied on the fact that pods with RestartPolicy=Always
This fixes the issue for jobs using pod failure policy (with JobPodFailurePolicy and PodDisruptionConditions never enter the Succeeded phase may need to adapt their controllers. This is because as a consequence of
feature gates enabled) that their pods could get stuck in the pending phase when deleted. the change pods which use RestartPolicy=Always may end up in the Succeeded phase in two scenarios: pod
deletion and graceful node shutdown. ([#115331](https://github.com/kubernetes/kubernetes/pull/115331), [@mimowo](https://github.com/mimowo)) [SIG Cloud Provider, Node and Testing]
Users who maintain controllers which relied on the fact that pods with RestartPolicy=Always - The in-tree cloud provider for AWS (and the EBS storage plugin) has now been removed. Please use the external cloud provider and CSI driver from https://github.com/kubernetes/cloud-provider-aws instead. ([#115838](https://github.com/kubernetes/kubernetes/pull/115838), [@torredil](https://github.com/torredil)) [SIG API Machinery, Apps, Architecture, Auth, CLI , Cloud Provider, Cluster Lifecycle, Instrumentation, Node, Release, Scheduling, Storage, and Testing]
never enter the Succeeded phase may need to adapt their controllers. This is because as a consequence of
the change pods which use RestartPolicy=Always may end up in the Succeeded phase in two scenarios: pod
deletion and graceful node shutdown. ([#115331](https://github.com/kubernetes/kubernetes/pull/115331), [@mimowo](https://github.com/mimowo)) [SIG Cloud Provider, Node and Testing]
## Changes by Kind ## Changes by Kind
### Deprecation ### Deprecation