Update doc certmanager 0.11 group and version change

[jenting]

Update documentation for certmanager 0.11 group and version change.
Change from certmanager.k8s.io/v1alpha1 to cert-manager.io/v1alpha2.

Fixes #1434

Signed-off-by: JenTing Hsiao [email protected]

[k8s-ci-robot]

Hi @jenting. 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.

[k8s-ci-robot]

Welcome @jenting!

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. 😃

[Adirio]

/ok-to-test

[camilamacedo86]

/approve

It shows ok for me. Let's looking for a second check from a trusted reviewer as well to see it get merged.

[camilamacedo86]

Hi @jenting,

This change also needs to be reflected in the book-v2 branch. See: https://github.com/kubernetes-sigs/kubebuilder/blob/master/CONTRIBUTING.md#how-to-contribute-to-docs

Could you please create the PR for we are able to move forward with?

wdyt @Adirio ?

[jenting]

Hi @jenting,

This change also needs to be reflected in the book-v2 branch. See: https://github.com/kubernetes-sigs/kubebuilder/blob/master/CONTRIBUTING.md#how-to-contribute-to-docs

Could you please create the PR for we are able to move forward with?

@camilamacedo86, sure~ but I thought someone (maybe release owner) would help me merge the changes from the master branch into the book-v2 branch.

Docs for unreleased features live in the master branch. We merge the master branch into the book-v2 branch when doing the releases.

[camilamacedo86]

My understand that is: If we do some change that should be reflected in the production docs. E.g a fix over something that is outdated there we need also to do a PR for book-v2.

However, it is fine. I will check it with @mengqiy and do in this case if required.

So:
/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: camilamacedo86, jenting

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

[jenting]

/test pull-kubebuilder-e2e-k8s-1-16-2

[jenting]

@camilamacedo86 After re-reading

If adding doc for an unreleased feature, the PR should target master branch. If updating existing docs, the PR should target master branch and then cherry-picked into book-v2 branch.

Open a cherry-pick PR #1453.