Skip to content

cmd-path not respected #754

Description

@tcolgate

The python client does not respect cmd-path in the gcp provider.

We abuse this feature to retrieve credentials for our non-gke clusters (hosted in AWS). This works well with k8s.io/client-go, but does not seem to be supported by the clients in the kubernetes-client org, with the exception of the nodejs client.

Activity

  1. fejta-bot commented on May 12, 2019

    @fejta-bot

    Issues go stale after 90d of inactivity.
    Mark the issue as fresh with /remove-lifecycle stale.
    Stale issues rot after an additional 30d of inactivity and eventually close.

    If this issue is safe to close now please do so with /close.

    Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
    /lifecycle stale

  2. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on May 12, 2019
  3. fejta-bot commented on Jun 11, 2019

    @fejta-bot

    Stale issues rot after 30d of inactivity.
    Mark the issue as fresh with /remove-lifecycle rotten.
    Rotten issues close after an additional 30d of inactivity.

    If this issue is safe to close now please do so with /close.

    Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
    /lifecycle rotten

  4. added
    lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.
    and removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Jun 11, 2019
  5. jfrabaute commented on Jun 17, 2019

    @jfrabaute
    Contributor

    We are having the same issue with a standard GKE cluster.
    The kube config has "cmd-path" and the client is failing to refresh the access token.
    Exception raised is:

    google.auth.exceptions.DefaultCredentialsError: Could not automatically determine credentials. Please set GOOGLE_APPLICATION_CREDENTIALS or explicitly create credentials and re-run the application. For more information, please see https://cloud.google.com/docs/authentication/getting-started
    

    Is there a plan to make this python client with with "cmd-path"?

  6. jfrabaute commented on Jun 18, 2019

    @jfrabaute
    Contributor

    /remove-lifecycle rotten

  7. removed
    lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.
    on Jun 18, 2019
  8. fejta-bot commented on Sep 16, 2019

    @fejta-bot

    Issues go stale after 90d of inactivity.
    Mark the issue as fresh with /remove-lifecycle stale.
    Stale issues rot after an additional 30d of inactivity and eventually close.

    If this issue is safe to close now please do so with /close.

    Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
    /lifecycle stale

  9. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Sep 16, 2019
  10. jfrabaute commented on Oct 3, 2019

    @jfrabaute
    Contributor

    We're having the same problem with all our gke clusters which are using cmd-path.
    I've just send a pull request to try to fix this: kubernetes-client/python-base#168

  11. fejta-bot commented on Nov 3, 2019

    @fejta-bot

    Stale issues rot after 30d of inactivity.
    Mark the issue as fresh with /remove-lifecycle rotten.
    Rotten issues close after an additional 30d of inactivity.

    If this issue is safe to close now please do so with /close.

    Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
    /lifecycle rotten

  12. added
    lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.
    and removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Nov 3, 2019
  13. jfrabaute commented on Nov 3, 2019

    @jfrabaute
    Contributor

    /remove-lifecycle rotten

  14. removed
    lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.
    on Nov 3, 2019
  15. fejta-bot commented on Feb 1, 2020

    @fejta-bot

    Issues go stale after 90d of inactivity.
    Mark the issue as fresh with /remove-lifecycle stale.
    Stale issues rot after an additional 30d of inactivity and eventually close.

    If this issue is safe to close now please do so with /close.

    Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
    /lifecycle stale

  16. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Feb 1, 2020
  17. jfrabaute commented on Feb 1, 2020

    @jfrabaute
    Contributor

    /remove-lifecycle stale

    The fix is merged on python-base, new python client version not released yet.
    Also, this PR might be needed as well to have this change fully operational: kubernetes-client/python-base#169

  18. removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Feb 1, 2020
  19. roycaihw commented on Feb 21, 2020

    @roycaihw
    Member

    Both fixes have been merged. They will be included in the upcoming 12.0.0a1 release

  20. jfrabaute commented on Mar 13, 2020

    @jfrabaute
    Contributor

    It looks like the fixes are present in 11.0.0 release. @roycaihw can you confirm? If so, maybe we can close this issue.

  21. roycaihw commented on Mar 18, 2020

    @roycaihw
    Member

    @jfrabaute Thanks for pointing that out. You're right.

    /close

  22. k8s-ci-robot commented on Mar 18, 2020

    @k8s-ci-robot
    Contributor

    @roycaihw: Closing this issue.

    Details

    In response to this:

    @jfrabaute Thanks for pointing that out. You're right.

    /close

    Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions