-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
Add common examples to Service Topology documentation #17808
Conversation
Deploy preview for kubernetes-io-vnext-staging processing. Building with commit 1943afd https://app.netlify.com/sites/kubernetes-io-vnext-staging/deploys/5ddf16d5ef951900082e76f5 |
/assign @johnbelamaric @imroc |
|
||
{{< feature-state for_k8s_version="v1.17" state="alpha" >}} | ||
|
||
To enable service topology, enable the `ServiceTopology` and `EndpointSlice` feature gate for all Kubernetes components: |
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.
/lgtm
Although some components do not need to enable these features, it may be easier to just enable them all, without having to remember these details.
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.
Some feedback. I noticed that the new task page ends up with two Prerequisites sections.
preferentially routed to endpoints that are on the same Node as the client, or | ||
in the same availability zone. | ||
|
||
## Prerequisites |
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 recommend moving this to the {{% capture prerequisites %}}
section (at time of writing, that starts on line 15)
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.
Good catch, thank you
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.
So the page actually renders the prerequisite capture as a "Before you begin" so I think it looks okay as-is.
routing: | ||
|
||
* Kubernetes 1.17 or later | ||
* Kube-proxy running in iptables mode or IPVS mode |
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.
Consider making kube-proxy
be a glossary tooltip. You can also link to the Service concept page, if you like; there is a section about the different modes.
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.
done, thanks
|
||
{{% capture whatsnext %}} | ||
|
||
* Read about using [Service Topology](/docs/concepts/services-networking/service-topology) |
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.
* Read about using [Service Topology](/docs/concepts/services-networking/service-topology) | |
* Read about the [Service Topology](/docs/concepts/services-networking/service-topology) concept |
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.
done, thanks
/lgtm Maybe also change |
{{% capture whatsnext %}} | ||
|
||
* Read about the [Service Topology](/docs/concepts/services-networking/service-topology) concept | ||
* Read [Connecting Applications with Services](/docs/concepts/services-networking/connect-applications-service/) |
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.
Should we have "Read about EndpointSlice" here?
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.
good catch, added!
/lgtm |
6e99b11
to
fa71e44
Compare
* BlockVolume is no longer alpha Signed-off-by: dulltz <[email protected]> * Apply comment #18167 (comment) Co-Authored-By: Tim Bannister <[email protected]> * Apply comment #18167 (comment) * Apply comment #18167 (review) Signed-off-by: dulltz <[email protected]> Co-authored-by: Tim Bannister <[email protected]>
* Renamed FeatureGate RequestManagement to APIPriorityAndFairness * sorted alphabetically * wrote RequestManagement into the deprecated table
@andrewsykim , would you comment on the status of this PR. Thank you. Are there outstanding 1.17 updates? |
@andrewsykim: PR needs rebase. 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. |
Added missing article in one of the sentences
Sorry this fell off my radar. I think it would be good to still add the changes. Should I re-open this PR against master? |
Please do! |
The Kubernetes logo links to the top-of-site for the current localization, so localize the title attribute.
Related kubernetes/minikube#6013 When using the `vmware` driver for minikube the shared folder will be in `/mnt/hgfs` instead of directly on root `/`.
Signed-off-by: Andrew Sy Kim <[email protected]>
Signed-off-by: Andrew Sy Kim <[email protected]>
New changes are detected. LGTM label has been removed. |
[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 |
/close Closing in favor of #18712 |
@andrewsykim: 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/test-infra repository. |
Follow-up PR to #17459.