📖 docs(cert-manager): Change ownership links

[jesse-c]

cert-manager became a CNCF project in 2022 [1]. The existing links to cert-manager, with Jetstack ownership, redirect to the new ownership.

The updated links have been verified to be working.

There was one file that had EOL whitespace formatting corrected.

FIXES #3607

[1] https://www.cncf.io/blog/2022/10/19/cert-manager-becomes-a-cncf-incubating-project/

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: jesse-c / name: Jesse Claven (390ca0c)

[k8s-ci-robot]

Welcome @jesse-c!

It looks like this is your first PR to kubernetes-sigs/kubebuilder 🎉. 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-sigs/kubebuilder 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. 😃

[k8s-ci-robot]

Hi @jesse-c. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[camilamacedo86]

Hi @jesse-c,

That is great. Could you please just sign the CLA so that we can move forward with this one? See: #3610 (comment)

/lgtm

/ok-to-test

[jesse-c]

Thank you, @camilamacedo86, for the quick turn around! I've just finished the CLA process and the check is passing now.

[camilamacedo86]

/lgtm

[jesse-c]

/retest

[jesse-c]

@camilamacedo86: I can't see why the extracting (tar -xf ...) is failing in the APIDiff action. For comparable PRs, it did run okay [1]. Furthermore, there aren't Go API changes as there aren't changes to Go files, outside of the one string value change. I have run the command manually locally (go-apidiff --compare-imports --print-compatible --repo-path=./ master 390ca0c2fc64f40ace0aa33e5c0a33072cfc78d) and there were no issues.

Is this a known flaky action? Any suggestions on determining the cause of this failure? Thank you! 🙏🏻

[1] https://github.com/kubernetes-sigs/kubebuilder/pull/3606/files

[camilamacedo86]

/lgtm

/hold cancel

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: camilamacedo86, jesse-c

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:

• OWNERS [camilamacedo86]

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

[camilamacedo86]

Moving forward with this one.
The APIDiff is falling when should not since it is only docs changes,

[jesse-c]

Thank you @camilamacedo86 for working through this with me!