-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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.
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
added description for KonnectivityService #44598
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR.
Please see the inline feedback
@sftim I have added commit |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about this? See the pages I've linked to for more detail.
I don't think we should frame Konnectivity as “vital” to a cluster - it isn't.
Update setup-konnectivity.md Update setup-konnectivity.md new commit
aeb9dc2
to
3e2f782
Compare
done |
LGTM for docs /sig api-machinery |
@kubernetes/sig-api-machinery-pr-reviews : PTAL |
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/remove-lifecycle rotten |
Left a message on the API Machinery Slack channel |
Pinging SIG API Machinery Leads and left a message on Slack @kubernetes/sig-api-machinery-leads PTAL |
Kubernetes can use an optional proxy mechanism, _Konnectivity_, that helps you connect | ||
your control plane's {{< glossary_tooltip text="API servers" term_id="kube-apiserver" >}} | ||
to your nodes, to {{< glossary_tooltip term_id="etcd" >}}, or to aggregated API servers. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can't the konnectivity service be used for all three egress types: controlplane (authn, authz, admission, conversion webhooks), etcd, and cluster (self-hosted aggregated apiservers)?
your control plane's {{< glossary_tooltip text="API servers" term_id="kube-apiserver" >}} | ||
to your nodes, to {{< glossary_tooltip term_id="etcd" >}}, or to aggregated API servers. | ||
|
||
The proxy operates at a stream layer, independent of packets and network routes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure what this sentence means. The apiserver has to be able to reach the konnectivity server and then the konnectivity server can tunnel as appropriate.
/close |
@tengqm: Closed this PR. In response to this:
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-sigs/prow repository. |
#44103