Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

teleport-kube-agent-app should be evictable by cluster-autoscaler in order to scale down nodes #3061

Closed
3 tasks done
AndiDog opened this issue Dec 21, 2023 · 1 comment
Closed
3 tasks done

Comments

@AndiDog
Copy link

AndiDog commented Dec 21, 2023

cluster-autoscaler 2023-12-21T12:53:50.957115967+01:00 I1221 11:53:50.957076       1 cluster.go:164] node ip-10-0-66-124.eu-west-2.compute.internal cannot be removed: non-daemonset, non-mirrored, non-pdb-assigned kube-system pod present: teleport-kube-agent-0

Tasks

Preview Give feedback
  1. tuladhar
@AndiDog AndiDog added this to Roadmap Dec 21, 2023
@github-project-automation github-project-automation bot moved this to Inbox 📥 in Roadmap Dec 21, 2023
@tuladhar tuladhar moved this from Inbox 📥 to In Progress ⛏️ in Roadmap Jan 1, 2024
@tuladhar
Copy link

tuladhar commented Jan 1, 2024

Problem

teleport-kube-agent runs in kube-system namespace. And by default, kube-system pods prevent cluster-autoscaler from removing nodes unless:

  • A. Pod has annotation cluster-autoscaler.kubernetes.io/safe-to-evict: "true"
  • B. Pod has PDB

Solution

  • In case of teleport-kube-agent we enable PDB with maxUnavailable: 1 and turning on high-availability mode with 2 replicas.

@tuladhar tuladhar closed this as completed Jan 3, 2024
@github-project-automation github-project-automation bot moved this from In Progress ⛏️ to Done ✅ in Roadmap Jan 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

2 participants