Skip to content

Add missing supports for kubernetes client stable and gold #166

Description

@mbohlool

according to new kubernetes client guidelines python client is beta support and has silver capabilities. We are almost there to have gold capabilities and stable support. missing parts are:

Gold:

Stable:

  • N documented users of the library
  • Support level documented per-platform
  • Deprecation policy (backwards compatibility guarantees documented)
  • Release process well documented

Activity

  1. added
    kind/featureCategorizes issue or PR as related to a new feature.
    on Mar 31, 2017
  2. dims commented on Mar 31, 2017

    @dims
    Collaborator

    @mbohlool what does "proto encoding" mean?

  3. mbohlool commented on Mar 31, 2017

    @mbohlool
    ContributorAuthor

    @lavalamp should know more about this, but I assume it means we encode the request body with proto instead of json.

  4. lavalamp commented on Mar 31, 2017

    @lavalamp
    Contributor

    Correct, request & response bodies. Here's an example proto file: https://github.com/kubernetes/kubernetes/blob/master/pkg/apis/apps/v1beta1/generated.proto

    You may not be able to determine the proto encoding from the OpenAPI spec--it'll be interesting to see you try to support these protos in a non-go language...

    Also the levels were chosen so that Silver was a perfectly acceptable sort of client to have, so it's not bad to be Silver :)

    It's just that if someone is going to write a high-bandwidth controller of some sort, proto is a lot more efficient.

  5. brendandburns commented on Apr 27, 2017

    @brendandburns
    Contributor

    @lavalamp what does "Generated Examples" mean in that doc? Does that mean that you have example code for the library? or that it is generated from something?

  6. pokoli commented on Jun 7, 2017

    @pokoli

    Sorry if it's too obious, but does proto mean using this library: https://github.com/google/protobuf/tree/master/python ?

  7. mbohlool commented on Jun 8, 2017

    @mbohlool
    ContributorAuthor
  8. added
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    on Nov 7, 2018
  9. fejta-bot commented on Apr 26, 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

  10. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Apr 26, 2019
  11. fejta-bot commented on May 26, 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 May 26, 2019
  13. BenElgar commented on Jun 20, 2019

    @BenElgar

    Just to clarify, does this mean port forwarding is not currently supported?

  14. micw523 commented on Jun 20, 2019

    @micw523
    Contributor

    /remove-lifecycle rotten

  15. removed
    lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.
    on Jun 20, 2019
  16. micw523 commented on Jun 20, 2019

    @micw523
    Contributor

    That is correct. Port forwarding is not yet supported on this client.

  17. fejta-bot commented on Sep 18, 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

  18. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Sep 18, 2019
  19. micw523 commented on Sep 18, 2019

    @micw523
    Contributor

    /lifecycle frozen

  20. 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 Sep 18, 2019
  21. mayu2010 commented on Feb 16, 2020

    @mayu2010

    port-forward call still not supported in python-client now?

  22. KnifeyMoloko commented on May 19, 2020

    @KnifeyMoloko

    Hey guys, any idea on how the attach / port-forward item is looking?

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

    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/featureCategorizes issue or PR as related to a new feature.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions