GitPlanet

Cheap and reliable Node.js hosting starts at $3/month, and $1/month static HTML hosting

Created with love in Canada, visit hostnodejs.com today

Feel like to post an Ad? Learn Details
All Projects → gardener-attic → auto-node-repair

gardener-attic / auto-node-repair

Licence: Apache-2.0 license
Kubernetes controller to repair not-ready nodes

Programming Languages

go
31211 projects - #10 most used programming language

Labels

kubernetesawsgardener

Projects that are alternatives of or similar to auto-node-repair

Gardener
Kubernetes-native system managing the full lifecycle of conformant Kubernetes clusters as a service on Alicloud, AWS, Azure, GCP, OpenStack, EquinixMetal, vSphere, MetalStack, and Kubevirt with minimal TCO.
Stars: ✭ 2,093 (+12981.25%)
Mutual labels:  gardener

Auto Node Repair

  • Kubernetes controller to repair nodes which are NotReady by replacing them with new fresh nodes. This is done by manipulating AutoScalingGroups to repair the nodes.
  • Currently supports only AWS cloud provider.

Archived component no longer maintained

  • This component is not used by gardener anymore and no longer maintained. It was archived in the gardener-attic.

How does it work ?

  • Control loop for each Auto Scaling Group configured for a shoot cluster :
    • Identify Nodes which are NotReady since configurable amount of time (~10 minutes).
    • Create new nodes and wait until they are Ready
    • Cordon and drain all NotReady nodes.
    • Delete the NotReady nodes.
  • Apply this approach for each ASG in a shoot cluster one by one.
  • For a given ASG, create excess Nodes in parallel but cordon, drain and delete Nodes one by one.
  • If ASG does not have sufficient capacity for excess Nodes, first delete the NotReady nodes then create new one.

Make commands

Command Implication
Make compile Build the go code locally
Make release Deploy image into Gcloud

Steps for development

Use the deploy/kubernetes/deployment.yaml to deploy the auto-node-repair into the cluster. Refer to this file for more details.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].