From 192553aed9c73c235d25ad5a6653f24bc327828a Mon Sep 17 00:00:00 2001 From: Ryan Richard Date: Tue, 26 Sep 2023 13:16:13 -0700 Subject: [PATCH] Stop using deprecated critical-pod annotation --- deploy/concierge/deployment.yaml | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/deploy/concierge/deployment.yaml b/deploy/concierge/deployment.yaml index bc8397cc..bd1c690f 100644 --- a/deploy/concierge/deployment.yaml +++ b/deploy/concierge/deployment.yaml @@ -1,4 +1,4 @@ -#! Copyright 2020-2022 the Pinniped contributors. All Rights Reserved. +#! Copyright 2020-2023 the Pinniped contributors. All Rights Reserved. #! SPDX-License-Identifier: Apache-2.0 #@ load("@ytt:data", "data") @@ -134,8 +134,6 @@ spec: #! More recently added the more unique deploymentPodLabel() so Services can select these Pods more specifically #! without accidentally selecting any other Deployment's Pods, especially the kube cert agent Deployment's Pods. _: #@ template.replace(deploymentPodLabel()) - annotations: - scheduler.alpha.kubernetes.io/critical-pod: "" spec: securityContext: runAsUser: #@ data.values.run_as_user @@ -247,9 +245,6 @@ spec: effect: NoSchedule - key: node-role.kubernetes.io/control-plane #! The new name for these nodes as of Kubernetes 1.24. effect: NoSchedule - #! "system-cluster-critical" cannot be used outside the kube-system namespace until Kubernetes >= 1.17, - #! so we skip setting this for now (see https://github.com/kubernetes/kubernetes/issues/60596). - #!priorityClassName: system-cluster-critical #! This will help make sure our multiple pods run on different nodes, making #! our deployment "more" "HA". affinity: