Add description in qos-pod-4.yaml

[ydFu]

Add description that distinguish between container-1 and container-2 make it easy to read.

Signed-off-by: ydFu [email protected]

[netlify]

✔️ Deploy preview for kubernetes-io-master-staging ready!

🔨 Explore the source changes: e6799c5

🔍 Inspect the deploy logs: https://app.netlify.com/sites/kubernetes-io-master-staging/deploys/5fef100247a2a9000ade5a97

😎 Browse the preview: https://deploy-preview-25904--kubernetes-io-master-staging.netlify.app

[sftim]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: d4396ef200ed5d7c9dda347b9e11a8b97bfe0c38

[ydFu]

@sftim
Thank for review this PR.

[ydFu]

/assign @zparnold
Thanks.

[Aut0R3V]

I think the added comments make sense. Maybe an existing member can comment for cofirmation.

[sftim]

This PR already has an LGTM. With another LGTM I can approve it; I would like a second review from a Kubernetes member before this merges.

[ydFu]

/assign @sftim
l thinked this PR be reviewed from other Kubernetes member(@Aut0R3V),
Thanks for your help.

[irvifa]

I’m not sure if we need a comment about the limit provided to the memory since it’s already defined on the manifest though.

[irvifa]

Otherwise it’s lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Aut0R3V
To complete the pull request process, please assign sftim after the PR has been reviewed.
You can assign the PR to them by writing /assign @sftim in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• content/en/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

@ydFu: GitHub didn't allow me to request PR reviews from the following users: Aut0R3V.

Note that only kubernetes members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/assign @sftim
l thinked this PR be reviewed from other Kubernetes member(@Aut0R3V),
Could you help to add "approved label" ?
Thanks for your help.

/cc @Aut0R3V @rajeshdeshpande02 @steveperry-53
Could you help to revirew this PR ?
Thanks for your 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.

[ydFu]

/assign @tengqm
Please help review this PR.
Let me know if there is anything need to be revised,and thank a lot.

[tengqm]

@ydFu TBH, I don't think we really need comments like these. The manifest is already straightforward.

[ydFu]

Thanks for your guidance.
At the time I thought the code in qos-pod-4.yaml of this article in configure-pod-container/quality-service-pod.md that is for
introduction to getting started,so just added description to replace the special blank line.

[tengqm]

@ydFu All the YAML manifests under the examples directory are associated with some contexts. These examples are provided to save the users some time on manually creating every YAML file. In this case, I'd prefer leaving some room for users to digest the manifests. Comments are only necessary when something unusual or something worth noting.

[ydFu]

@tengqm
Thank you for your instruction and advice.
It let me know the norms in the YAML manifests under the examples directory.
The next submission is similar the adjustment,I will pay special attention.