Skip to content

need support load_kube_config_data() #1213

Description

@onecer

What is the feature and why do you need it:

I creating a simply k8s tools to mange that for my customers. They have diffrence cluster.

I want to store kubeconfig in mysql, manage mutilple k8s cluster.

from now just have two way too create a client.

  • load_kube_config(). -- load kubeconfig fron file
  • client.Configuration() -- use token

I think that kubeconfig is easy to config. Its friendly for my users.

here is my program process steps.

  1. read kubeconfig from mysql
  2. store it to disk /tmp/xxx.
  3. load_kube_config(/tmp/xxx)

Describe the solution you'd like to see:

support set kubeconfig from strings. like load_kube_config_data(data='kubeconfig data')

Activity

  1. added
    kind/featureCategorizes issue or PR as related to a new feature.
    on Jul 24, 2020
  2. ConscriptMR commented on Aug 1, 2020

    @ConscriptMR

    well not from strings but from JSONs maybe would be more practical

  3. roycaihw commented on Aug 7, 2020

    @roycaihw
    Member

    Loading kubeconfig from dict support was added recently: kubernetes-client/python-base#195. You can load JSON blob into dict and load kubeconfig from there

  4. fejta-bot commented on Nov 5, 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

  5. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Nov 5, 2020
  6. fejta-bot commented on Dec 5, 2020

    @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

  7. 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 Dec 5, 2020
  8. fejta-bot commented on Jan 4, 2021

    @fejta-bot

    Rotten issues close after 30d of inactivity.
    Reopen the issue with /reopen.
    Mark the issue as fresh with /remove-lifecycle rotten.

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

  9. k8s-ci-robot commented on Jan 4, 2021

    @k8s-ci-robot
    Contributor

    @fejta-bot: Closing this issue.

    Details

    In response to this:

    Rotten issues close after 30d of inactivity.
    Reopen the issue with /reopen.
    Mark the issue as fresh with /remove-lifecycle rotten.

    Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
    /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

    kind/featureCategorizes issue or PR as related to a new feature.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions