fix: TLSConfig secretName description

[arcezd]

On the DynamicServingConfig/TLSConfig are specifying the same secretNamespace description for the secretName attribute.
DynamicServingConfig

[jetstack-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign jakexks for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[netlify]

✅ Deploy Preview for cert-manager-website ready!

Name	Link
🔨 Latest commit	72d3d9b
🔍 Latest deploy log	https://app.netlify.com/sites/cert-manager-website/deploys/65c1611107d4030007b37007
😎 Deploy Preview	https://deploy-preview-1419--cert-manager-website.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.

[wallrj]

Thanks for spotting this @arcezd

These docs are automatically generated from the cert-manager API

https://github.com/cert-manager/cert-manager/blob/a22d1d673ae8c16733ed342d4330eb5f5ab3f016/pkg/apis/config/webhook/v1alpha1/types.go#L102-L104

So we first need to create a cert-manager PR to fix the documentation there and then regenerate these pages.

[arcezd]

Thanks for the clarification @wallrj, I just created the cert-manager PR 6785 with the changes, I guess we can close this one.
Thanks!

[wallrj]

Thanks @arcezd.
Once that cert-manager PR merges, we will have to regenerate the API documentation here, using the scripts in scripts/.
So let's leave this open as a reminder.

[cert-manager-prow]

PR needs rebase.

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-sigs/prow repository.