Update breaking changes details 1.16

[wallrj]

Preview: https://deploy-preview-1568--cert-manager.netlify.app/docs/releases/release-notes/release-notes-1.16/#breaking-changes

• Applied @maelvls 's suggestions (from Release cert-manager 1.16 #1520 (comment))
• Prioritized the Helm schema information (as suggested by @SgtCoDFish in Release notes updates for cert-manager v1.16.0-beta.0 #1565 (comment))
• Added some further reading to the Helm schema section.

[netlify]

✅ Deploy Preview for cert-manager ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	dba5531
🔍 Latest deploy log	https://app.netlify.com/sites/cert-manager/deploys/66fbb8f02be96c0008efc397
😎 Deploy Preview	https://deploy-preview-1568--cert-manager.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[jsoref]

the 1.16.x bit doesn't work...

Today, I can use:
helm template cert-manager --repo https://charts.jetstack.io --version 1.16.0-beta.0 --values values.yaml

But, as a reader, I expect a command like this to work as is in the docs, and not require guessing.

[SgtCoDFish]

suggestion: Having the command in just backticks like this means it gets split across lines:

That makes it harder to copy and I think a lot of people upgrading will want to copy it!

I'd suggest having it in triple backticks instead so it's rendered as a code block:

Suggested change

	> You can use `helm template cert-manager --repo https://charts.jetstack.io --version 1.16.x --values values.cert-manager.yaml`
	> ```bash
	> helm template cert-manager --repo https://charts.jetstack.io --version 1.16.x --values values.cert-manager.yaml
	> ```

(the suggestion might not work as-is, but you get the idea)

[jsoref]

Do we know if users actually need to use that much wording?

For me, this was more than enough (as I had already adjusted my Chart.yaml file to use the newer chart repo):

helm template cert-manager . --values values.yaml

[wallrj]

@SgtCoDFish Done. And added an example of an error.

@jsoref You're suggested command would only work for your specific sub-chart use-case, right? For general users it is better to state the repo URL (otherwise they'd need to run helm repo update first) and it's better to state the version otherwise they may not be testing against the cert-manager 1.16 release.

I wrote --version 1.16.x deliberately, because I thought it would continue to work for future 1.16 patch releases.
It does not work with 1.16 pre-releases without an additional --devel flag.
So I've added an explicit version variable instead which should be updated with future patch releases.

[SgtCoDFish]

/lgtm
/approve

I think this looks good. I don't actually think we need to update the --version unless we notice a major bug in the chart for 1.16.1, since this is just to check that pre-existing values work. But no major thing either way.

Thanks for this!

[cert-manager-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: SgtCoDFish

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 [SgtCoDFish]

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