Issue with k8s.io/docs/reference/access-authn-authz/certificate-signing-requests/

[BaskingWithSharks]

Documentation says
"A CertificateSigningRequest (CSR) resource is used to request that a certificate be signed by a denoted signer".
and
"The CertificateSigningRequest resource type allows a client to ask for an X.509 certificate be issued..."

What is it now ? "be signed" or "be issued" or do these words denote the same action ?

[sftim]

This is mostly a support request I think.

Issuing and signing a certificate are closely related concepts. We could improve the wording, which would help non-native speakers, folks who are new to this, and folks who are in a hurry - amongst others.

I don't see a case for prioritising that cleanup though.
/sig auth
/priority awaiting-more-evidence
/language en

[sftim]

Maybe if we link to https://en.wikipedia.org/wiki/Certificate_signing_request for context?

[divya-mohan0209]

I agree with Tim that signing and issuing are closely linked and maybe we could word it better + link it to the Wiki link mentioned above.

[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

[divya-mohan0209]

/remove-lifecycle rotten