Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Access Clusters Using the Kubernetes API has outdate list of official client libraries #16906

Closed
sftim opened this issue Oct 14, 2019 · 7 comments
Closed

Access Clusters Using the Kubernetes API has outdate list of official client libraries #16906

sftim opened this issue Oct 14, 2019 · 7 comments
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@sftim
Copy link
Contributor

sftim commented Oct 14, 2019

This is a Bug Report

Problem: Access Clusters Using the Kubernetes API lists 2 official client libraries: Python and Go[lang]. The trouble is, there are actually 6 (at the time of writing).

Proposed Solution:
Revise the page. Either of:

  • list all 6 client libraries in that page
  • summarise the 6 client libraries and signpost readers to find more about the official client library that they prefer

Page to Update:
https://kubernetes.io/docs/tasks/administer-cluster/access-cluster-api/

Additional Information:
Some people might favor documenting Go and giving that client library special treatment, because lots of Kubernetes clients are written in Go. I recommend not giving Go special treatment, precisely because the ecosystem is currently so skewed towards one language. It's useful to facilitate diversity of client code.
@shubham-asati
Copy link
Contributor

@sftim It will be good if this page have examples of all six libraries with basic explanation.
I would like to add more details . Pls assign me this issue.

@sftim
Copy link
Contributor Author

sftim commented Oct 14, 2019

@shub-asa1 it's great to hear that you'd like to sort this out.

If you propose a pull request, and you've signed the CLA, that's all that's needed for a review and, I hope, a fix.

@sftim
Copy link
Contributor Author

sftim commented Oct 14, 2019

/kind cleanup
/priority important-longterm

@k8s-ci-robot k8s-ci-robot added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Oct 14, 2019
shubham-asati added a commit to shubham-asati/website that referenced this issue Oct 15, 2019
@shubham-asati
adding details for all official client libraries .
aad1df8 
there are six official client libraries for kubernetes. Added details and example for each language .Fix for issue kubernetes#16906
@shubham-asati shubham-asati mentioned this issue Oct 15, 2019
Merged
k8s-ci-robot pushed a commit that referenced this issue Oct 23, 2019
@shubham-asati @k8s-ci-robot
adding details for all official client libraries . Fix for issue #16906…
ef602a8 
… (#16940)

* adding details for all official client libraries .

there are six official client libraries for kubernetes. Added details and example for each language .Fix for issue #16906

* few typos and syntax mistakes resolved

* Update access-cluster-api.md

* removing extra code from haskell client
@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 12, 2020
@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 11, 2020
@fejta-bot
Copy link

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

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

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
Assignees
No one assigned
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@k8s-ci-robot @sftim @fejta-bot @shubham-asati