godaddy/kubernetes-client

watch jobs with a hostname labelselector

Open

#374 创建于 2018年12月18日

在 GitHub 查看
 (1 评论) (0 反应) (0 负责人)JavaScript (954 star) (206 fork)batch import
help wantedquestionrequest for example

描述

Writing code like this:

const jobStream = client.apis.batch.v1.watch.jobs.getStream({ qs: { labelSelector: 'kubernetes.io/hostname=ip-10-0-22-120.us-west-2.compute.internal'}});

Doesn't work. Basically trying to watch all jobs on a host by host basis from a kubernetes daemonset. Tried to manually add a label with the spec.nodeName via the downward api but that doesn't appear to work in the JSON only via the volume api.

Open to ideas!

Thanks!

贡献者指南

技术栈
javascriptnodejs
领域
backenddevopsapi
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-2 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
needs investigation
前置要求
Node.jsKubernetes resourcesLabel selectors
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
30
研究方向
Investigate the watch implementation in the kubernetes client library, specifically the `getStream` method for jobs. Check if labelSelector is properly forwarded in the request. Look at the source code in the `watch` module and compare with similar implementations for other resources. Also review the Kubernetes API documentation to confirm that labelSelector is supported for watch endpoints. Consider looking at any existing tests or examples for watch with selectors.