godaddy/kubernetes-client

watch jobs with a hostname labelselector

Open

#374 opened on Dec 18, 2018

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (954 stars) (206 forks)batch import
help wantedquestionrequest for example

Description

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!

Contributor guide

Tech stack
javascriptnodejs
Domain
backenddevopsapi
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Node.jsKubernetes resourcesLabel selectors
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
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.