kube-spot-termination-notice-handler | Kubernetes DaemonSet to gracefully delete pods 2 minutes | DevOps library

by kube-aws Shell Version: Current License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | kube-spot-termination-notice-handler Summary

kube-spot-termination-notice-handler is a Shell library typically used in Devops applications. kube-spot-termination-notice-handler has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

A Kubernetes DaemonSet to run 1 container per node to periodically polls the EC2 Spot Instance Termination Notices endpoint. Once a termination notice is received, it will try to gracefully stop all the pods running on the Kubernetes node, up to 2 minutes before the EC2 Spot Instance backing the node is terminated.

Support

Quality

Security

License

Reuse

Support

kube-spot-termination-notice-handler has a low active ecosystem.

It has 333 star(s) with 74 fork(s). There are 10 watchers for this library.

It had no major release in the last 6 months.

There are 8 open issues and 8 have been closed. On average issues are closed in 140 days. There are 4 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of kube-spot-termination-notice-handler is current.

Quality

kube-spot-termination-notice-handler has no bugs reported.

Security

kube-spot-termination-notice-handler has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

kube-spot-termination-notice-handler is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

kube-spot-termination-notice-handler releases are not available. You will need to build from source code and install.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of kube-spot-termination-notice-handler

Get all kandi verified functions for this library.

kube-spot-termination-notice-handler Key Features

No Key Features are available at this moment for kube-spot-termination-notice-handler.

kube-spot-termination-notice-handler Examples and Code Snippets

No Code Snippets are available at this moment for kube-spot-termination-notice-handler.

Community Discussions

Trending Discussions on kube-spot-termination-notice-handler

How is the preemption notice handled?

QUESTION

How is the preemption notice handled?

Asked 2019-Feb-25 at 00:43

I'm currently running on AWS and use kube-aws/kube-spot-termination-notice-handler to intercept an AWS spot termination notice and gracefully evict the pods.

I'm reading this GKE documentation page and I see:

Preemptible instances terminate after 30 seconds upon receiving a preemption notice.

Going into the Compute Engine documentation, I see that a ACPI G2 Soft Off is sent 30 seconds before the termination happens but this issue suggests that the kubelet itself doesn't handle it.

So, how does GKE handle preemption? Will the node do a drain/cordon operation or does it just do a hard shutdown?

...

ANSWER

Answered 2018-Apr-19 at 11:14

Yes you are right, so far there is no built in way to handle ACPI G2 Soft Off.

Notice that if normal preemptible instance supports shutdown scripts (where you could introduce some kind of logic to perform drain/cordon), this is not the case if they are Kubernetes nodes:

Currently, preemptible VMs do not support shutdown scripts.

You can perform some test but quoting again from documentation:

You can simulate an instance preemption by stopping the instance.

And so far if you stop the instance, even if it is a Kubernetes node no action is taken to cordon/drain and gratefully remove the node from the cluster.

However this feature is still in beta therefore it is at its early stage of life and in this moment it is a matter of discussion if and how introduce this feature.

Disclaimer: I work For Google Cloud Platform Support

Source https://stackoverflow.com/questions/49916965

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install kube-spot-termination-notice-handler

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: