Divided headings: labels, annotations, taints

[itsguneetsingh]

Made two separate headings as asked for in the issue #29670 and wrote some additional text under each heading explaining

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
• Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: [email protected]

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. I understand the commands that are listed here.

[k8s-ci-robot]

Welcome @Guneetconvent2002!

It looks like this is your first PR to kubernetes/website 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/website has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[itsguneetsingh]

signed the CLA

[geoffcline]

/check-cla

[geoffcline]

Hi @Guneetconvent2002 and welcome 👋

It seems your CLA still isn't detected. Can you check that the email address used for these commits (git log) and the CLA membership match?

[geoffcline]

also I'm going to /assign and suggest some revisions

[itsguneetsingh]

Hi @Guneetconvent2002 and welcome 👋

It seems your CLA still isn't detected. Can you check that the email address used for these commits (git log) and the CLA membership match?

That's strange cause I have made a CLA profile and it uses the same email ID as on my github

[itsguneetsingh]

also I'm going to /assign and suggest some revisions

do you mean that you're going to take over the issue or give me some suggestions to make changes??

[itsguneetsingh]

Could you maybe help me cause I have the same email ID for both git commit and EasyCLA

[geoffcline]

Yes, ill review and suggest changes. I'll also take a look at the CLA.

[geoffcline]

I requested some changes. Overall, I think it's helpful to add a link here.

You can submit a support request regarding the CLA here: https://jira.linuxfoundation.org/plugins/servlet/theme/portal/4/create/88

[jlbutler]

/assign

[netlify]

👷 Deploy Preview for kubernetes-io-vnext-staging processing.

🔨 Explore the source changes: 4a7a977

🔍 Inspect the deploy log: https://app.netlify.com/sites/kubernetes-io-vnext-staging/deploys/61a7fb2cee2e8a0008bf5e4e

[itsguneetsingh]

@jlbutler could maybe have a look on this and tell me what changes to make?

[jlbutler]

@jlbutler could maybe have a look on this and tell me what changes to make?

Hi there! 👋 For your commits, avoid using @'s (as well as # references) in the commit message. As you're working through your edits, you may consider rebasing and collapsing into a single commit (though not necessary right now).

For the content, @gcilne can you spin back through and review edits so far?

Thanks everyone!

[itsguneetsingh]

@jlbutler could maybe have a look on this and tell me what changes to make?

Hi there! 👋 For your commits, avoid using @'s (as well as # references) in the commit message. As you're working through your edits, you may consider rebasing and collapsing into a single commit (though not necessary right now).

For the content, @gcilne can you spin back through and review edits so far?

Thanks everyone!

Okay, I'll keep in mind in the future. I don't think that I need to undo that commit now. do I?
Also, It's been a week and I have no response regrading any changes to be made so, if you or @geoffcline could look at this and let me know what needs to be done or taken care of?

[geoffcline]

Can you revise this sentence based on this section of the style guide?

[geoffcline]

Just two small changes suggested 👍

[itsguneetsingh]

I have implemented the changes that you asked for @geoffcline
Hope it's fine now. Also, do I need to delete the commit mentioning you? cause the bot has reacted on it multiple times. If yes, then could you maybe tell me how I could do it?

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 13dcc8f903cc9e9d0e43729d05aff410cd253545

[sftim]

@Guneetconvent2002

Thanks for these changes @Guneetconvent2002

/lgtm
I think these are technically correct and (barely) OK to merge.
The proposed text links to https://k8s.io//docs/reference/generated/kubernetes-api/v1.22/#podsecuritycontext-v1-core
which:

• will go stale when Kubernetes v1.23 is released
• is a link to our old API reference, not the preferred current one

@Guneetconvent2002 If you want to, I think we could improve this documentation further and I have made some suggestions based on how I'd write these.

[sftim]

Hi @Guneetconvent2002

Could you squash this down to 1 commit? (If you're not sure how, you can instead let us know that you agree and a maintainer can do the squash for you).

[itsguneetsingh]

I don't really know how to squash commits together so, if a maintainer could do it, that would be great.

[geoffcline]

/label tide/merge-method-squash
/lgtm

[geoffcline]

ok, now it will be automatically squashed when approved :)

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 9ccc727cd56f6962de01118ae4e351760fdc5c48

[jlbutler]

@Guneetconvent2002 I'd pinged on this earlier, still unsure if this PR needs to come into dev-1.23 or main. If there isn't anything specific to the 1.23 release (or later), this PR can point at main.

[itsguneetsingh]

When I started working on this, the query mentioned that changes were required in dev-1.23 specifically. Since the topics where I've made changes; I was not able to find them in the main branch when I was trying to do so

[reylejano]

@Guneetconvent2002 can you squash your commits. One of your commit messages uses an invalid character #

[itsguneetsingh]

@Guneetconvent2002 can you squash your commits. One of your commit messages uses an invalid character #

I'm sorry but I don't really know how to do it. Perhaps if the admins could do it. @jlbutler could you maybe help me with that?

[jlbutler]

@Guneetconvent2002 i'll ping on slack again and see if we can work through it there.

[sftim]

I'll squash these down for you @Guneetconvent2002 using my maintainer access to write to your fork

[linux-foundation-easycla]

• ❌ - Guneet Singh The commit (4a7a977) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please submit a support request ticket.

[sftim]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sftim

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

The pull request process is described here

Needs approval from an approver in each of these files:

• content/en/OWNERS [sftim]

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

[sftim]

/remove-label tide/merge-method-squash