Skip to content

periodically reload InClusterConfig token #616

Closed
#1161
kubernetes-client/python-base
#191
Closed
periodically reload InClusterConfig token#616
#1161
kubernetes-client/python-base
#191
Labels
good first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.kind/featureCategorizes issue or PR as related to a new feature.

Description

@mbohlool
mbohlool
opened on Aug 31, 2018

This feature is being implemented for client-go in the main repo and needs to be implemented here too: kubernetes/kubernetes#67359

Activity

  1. mbohlool
    added
    kind/featureCategorizes issue or PR as related to a new feature.
    good first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.
    on Aug 31, 2018

  2. marie-yau commented on Oct 20, 2018

    @marie-yau
    marie-yau
    on Oct 20, 2018

    Will let you know shortly. I'm working on it.

  3. saurav-malani commented on Oct 26, 2018

    @saurav-malani
    saurav-malani
    on Oct 26, 2018

    @GeekTheGreat are you still working on this? If not, then I would like to take it up.

  4. marie-yau commented on Oct 26, 2018

    @marie-yau
    marie-yau
    on Oct 26, 2018

    Hello @saurav-malani, I'm working on it.

  5. sunitharavi9 commented on Jan 17, 2019

    @sunitharavi9
    sunitharavi9
    on Jan 17, 2019

    I would like to work on this issue.

  6. saurav-malani commented on Feb 12, 2019

    @saurav-malani
    saurav-malani
    on Feb 12, 2019

    Hello @isunitha98selvan! I haven't seen any activity on this issue, for the past 4 weeks. Are you still working on this?

  7. marie-yau commented on Feb 12, 2019

    @marie-yau
    marie-yau
    on Feb 12, 2019

    Hello everyone, you can work on it. It is too difficult for me to fix.

  8. fejta-bot commented on May 13, 2019

    @fejta-bot
    fejta-bot
    on May 13, 2019

    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. k8s-ci-robot
    added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on May 13, 2019

  10. micw523 commented on May 13, 2019

    @micw523
    micw523
    on May 13, 2019
    Contributor

    /remove-lifecycle stale

  11. k8s-ci-robot
    removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on May 13, 2019

  12. LTMenezes commented on May 24, 2019

    @LTMenezes
    LTMenezes
    on May 24, 2019

    Can I work on this issue? @mbohlool

  13. mikedanese commented on Aug 6, 2019

    @mikedanese
    mikedanese
    on Aug 6, 2019

    @LTMenezes please do.

  14. schedutron commented on Oct 19, 2019

    @schedutron
    schedutron
    on Oct 19, 2019

    @LTMenezes are you still working on this? I'd like to give a shot.

  15. LTMenezes commented on Dec 19, 2019

    @LTMenezes
    LTMenezes
    on Dec 19, 2019

    Sorry for the delay @schedutron, I am not, you can go ahead.

  16. fejta-bot commented on Mar 18, 2020

    @fejta-bot
    fejta-bot
    on Mar 18, 2020

    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

  17. k8s-ci-robot
    added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Mar 18, 2020

  18. mikedanese commented on Mar 20, 2020

    @mikedanese
    mikedanese
    on Mar 20, 2020

    /lifecycle frozen

  19. k8s-ci-robot
    added
    lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.
    and removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Mar 20, 2020

  20. zshihang commented on Apr 27, 2020

    @zshihang
    zshihang
    on Apr 27, 2020
    Contributor

    /remove-lifecycle frozen

  21. k8s-ci-robot
    removed
    lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.
    on Apr 27, 2020

  22. zshihang commented on Apr 28, 2020

    @zshihang
    zshihang
    on Apr 28, 2020
    Contributor

    this can be closed. @mikedanese

  23. mikedanese commented on May 11, 2020

    @mikedanese
    mikedanese
    on May 11, 2020

    @zshihang Thanks!

  24. mikedanese commented on May 11, 2020

    @mikedanese
    mikedanese
    on May 11, 2020

    /close

  25. k8s-ci-robot commented on May 11, 2020

    @k8s-ci-robot
    k8s-ci-robot
    on May 11, 2020
    Contributor

    @mikedanese: You can't close an active issue/PR unless you authored it or you are a collaborator.

    Details

    In response to this:

    /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.

  26. k8s-ci-robot
    closed this as completedin #1161on May 26, 2020
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

    good first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.kind/featureCategorizes issue or PR as related to a new feature.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions