aws / aws/containers-roadmap

[EKS] [request]: partition placement group partition id on kubectl describe node

Open
#1,910 0 comments 9 reactions 0 assignees View on GitHub
EKS Proposed
Dominant language
Shell
Stars
5.4k
Forks
334
PR merge metrics
No merged PRs in 30d

Description

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**
When partition placement group is used to launch the workers, the created nodes will have a partition id. At the moment, the partition id is queried using ec2 describe-instances. The ask is to include the partition id inside kubectl describe node result, under Labels. This feature will be helpful to let the K8S scheduler allocate Pods of a service correctly into different partitions.

**Which service(s) is this request for?**
EKS

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
We want to ensure that the K8s schedule can identify the nodes based on the partition id and schedule a service on nodes, this will ensure that service will not run on the same hardware in case of failure.

**Are you currently working around this issue?**
AWS CLI call to get the instance id and the corresponding partition id. once determined we apply labels to the nodes for identification

**Additional context**
Anything else we should know?

**Attachments**
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)

Contributor guide

Open the contributing guide

Research direction

Start by reviewing how EKS worker nodes expose metadata to kubectl describe node and how the existing EC2 describe-instances or AWS CLI lookup obtains the partition id. The work is done when the partition id appears as a node label and Kubernetes scheduling can use it to distinguish partition placement groups.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, kubernetes
Domain
cloud, devops, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.