Contributor guide: document internal Kubelet API

[ehashman]

The kubelet has an undocumented, unversioned API that is not intended for client use.

Its existence often catches new contributors by surprise. It would be good to add some developer documentation on the API in the community repo under the SIG Node folder: https://github.com/kubernetes/community/tree/master/contributors/devel/sig-node

See https://github.com/kubernetes/kubernetes/blob/release-1.22/pkg/kubelet/server/server.go#L331-L404 and https://github.com/kubernetes/kubernetes/blob/release-1.22/pkg/kubelet/server/server.go#L412-L498 for the corresponding endpoints in the kubelet.

/sig node
/kind documentation
/help

[k8s-ci-robot]

@ehashman:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

The kubelet has an undocumented, unversioned API that is not intended for client use.

Its existence often catches new contributors by surprise. It would be good to add some developer documentation on the API in the community repo under the SIG Node folder: https://github.com/kubernetes/community/tree/master/contributors/devel/sig-node

See https://github.com/kubernetes/kubernetes/blob/release-1.22/pkg/kubelet/server/server.go#L331-L404 and https://github.com/kubernetes/kubernetes/blob/release-1.22/pkg/kubelet/server/server.go#L412-L498 for the corresponding endpoints in the kubelet.

/sig node
/kind documentation
/help

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.

[catblade]

Interested.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[vaibhav2107]

/remove-lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[vaibhav2107]

/remove-lifecycle stale