From b0f694f50ac792143382ee7899fe622e0e86303a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marko=20Mudrini=C4=87?= Date: Tue, 27 Jun 2023 12:46:25 +0200 Subject: [PATCH] CHANGELOG-1.27: Add note for AWS in-tree provider removal MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Marko Mudrinić --- CHANGELOG/CHANGELOG-1.27.md | 27 ++++++++++++++------------- 1 file changed, 14 insertions(+), 13 deletions(-) diff --git a/CHANGELOG/CHANGELOG-1.27.md b/CHANGELOG/CHANGELOG-1.27.md index 2eb6d11f4ca..bcb350a81a4 100644 --- a/CHANGELOG/CHANGELOG-1.27.md +++ b/CHANGELOG/CHANGELOG-1.27.md @@ -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 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)) - - 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 - phase (Succeeded or Failed, depending on the exit statuses of the pod containers) to pods which - are deleted while running. - - This fixes the issue for jobs using pod failure policy (with JobPodFailurePolicy and PodDisruptionConditions - feature gates enabled) that their pods could get stuck in the pending phase when deleted. - - Users who maintain controllers which relied on the fact that pods with RestartPolicy=Always - 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] - + This fixes the issue for jobs using pod failure policy (with JobPodFailurePolicy and PodDisruptionConditions + feature gates enabled) that their pods could get stuck in the pending phase when deleted. + + Users who maintain controllers which relied on the fact that pods with RestartPolicy=Always + 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] +- 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] + ## Changes by Kind ### Deprecation