Help us understand the problem. What is going on with this article?

EKSにおけるノードダウン~Pod停止のタイムラグ

概要

タイトルの通りですが、EKSにおけるノードダウン~Pod停止のタイムラグについて。

問題点

K8sにおいては--pod-eviction-timeout durationを調整することでノードダウンが発生してからPod停止と見なされる時間を調整できるのですが、殊EKSではこの調整はできず、最低5分の縛りがあります。障害復帰を検討する際、この5分は時として長すぎることが懸念されます。

Reference

以下のように、K8sではパラメータのチューニングにより時間調整が可能なのですが、EKSでは現状不可のようです(2019/9/10現在)。

--pod-eviction-timeout duration Default: 5m0s
The grace period for deleting pods on failed nodes.

https://kubernetes.io/docs/reference/command-line-tools-reference/kube-controller-manager/

対策

需要があるかと思い、とりあえず以下のIssueにこの旨発言しておきました。
https://github.com/aws/containers-roadmap/issues/159
以上

Why do not you register as a user and use Qiita more conveniently?
  1. We will deliver articles that match you
    By following users and tags, you can catch up information on technical fields that you are interested in as a whole
  2. you can read useful information later efficiently
    By "stocking" the articles you like, you can search right away
Comments
Sign up for free and join this conversation.
If you already have a Qiita account
Why do not you register as a user and use Qiita more conveniently?
You need to log in to use this function. Qiita can be used more conveniently after logging in.
You seem to be reading articles frequently this month. Qiita can be used more conveniently after logging in.
  1. We will deliver articles that match you
    By following users and tags, you can catch up information on technical fields that you are interested in as a whole
  2. you can read useful information later efficiently
    By "stocking" the articles you like, you can search right away