godaddy / godaddy/kubernetes-client

Question About Streaming and Watch End Points

Open
#576 1 comment 2 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
962
Forks
189
PR merge metrics
No merged PRs in 30d

Description

This document states that streaming support is being removed from end points other than watch and pod logs:

https://github.com/godaddy/kubernetes-client/blob/master/merging-with-kubernetes.md

However, according to the Kubernetes API reference, the watch end points are deprecated and the correct way to watch for events is to use the list end points with watch parameter:

https://v1-14.docs.kubernetes.io/docs/reference/generated/kubernetes-api/v1.14/#watch-pod-v1-core

I noticed that the list end points in kubernetes-client don't have the new .getObjectStream() and .getByteStream() methods, and a warning like this displays when using .getStream() with list:

`kubernetes-client deprecated .getStream see https://github.com/godaddy/kubernetes-client/blob/master/merging-with-kubernetes.md`

Is it correct that kubernetes-client should require me to use the deprecated watch end points, or is this an oversight?

Contributor guide

Open the contributing guide

Research direction

Read merging-with-kubernetes.md and compare its streaming guidance with the linked Kubernetes API reference. Inspect the list and watch endpoint implementations and their stream methods; done means establishing whether list endpoints should support the newer watch parameter or documenting the intended usage.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, kubernetes
Domain
api
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.