godaddy/kubernetes-client

.getStream() doesn't authenticate with refreshAuth

Open

#373 opened on Dec 15, 2018

View on GitHub
 (7 comments) (2 reactions) (0 assignees)JavaScript (954 stars) (206 forks)batch import
help wanted

Description

On an AWS EKS cluster calling:

        const stream = client.apis.apps.v1.watch.namespaces('default').deployments.getStream();
        const jsonStream = new JSONStream();
        stream.pipe(jsonStream);
        jsonStream.on('data', object => {
            console.log('Event: ', JSON.stringify(object, null, 2));
        });

Fails to authenticate with:

Event: { "kind": "Status", "apiVersion": "v1", "metadata": {}, "status": "Failure", "message": "deployments.apps is forbidden: User "system:anonymous" cannot watch deployments.apps in the namespace "tilloo"", "reason": "Forbidden", "details": { "group": "apps", "kind": "deployments" }, "code": 403 }

Workaround is to call any other API first. This may be related to: #248

Contributor guide

Tech stack
javascriptnodejskubernetes
Domain
api
Issue type
bug
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-3 hours
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.
clear
Prerequisites
Node.jsKubernetes basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Investigate the `getStream()` method in the Kubernetes client to see why authentication fails. The issue mentions that calling another API first works, so the authentication token may not be refreshed before streaming. Check the auth interceptor/refresh logic and ensure it runs before stream connections. Also review linked issue #248 for similar authentication problems.