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 (206 forks)batch import
help wanted

Repository metrics

Stars
 (954 stars)
PR merge metrics
 (No merged PRs in 30d)

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

Research direction
Investigate how refreshAuth is handled in the getStream() method compared to other API calls. The issue suggests that making another API call first works around the authentication failure. Look at the authentication flow for watch streams and identify where the refreshAuth token is not being applied. Refer to issue #248 for related context.
Tech stack
javascriptnodejs
Domain
backendapi
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.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitNode.jsKubernetes basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55