fix(cert manager): Fix cert_manager_trusted_internal_ca manifest

[peschmae]

As described in #9921 the cert manager deployment fails if cert_manager_trusted_internal_ca is provided together with the dns policy.

What type of PR is this?
/kind bug

What this PR does / why we need it:
This moves the volume and mount, to the top of the conditionals in the cert manager manfiest, to fix the order.

Which issue(s) this PR fixes:
Fixes #9921

Special notes for your reviewer:
Alternatively, it would also be possible to split the volumeMount and the volumes definitions.

Does this PR introduce a user-facing change?:

Fix `cert_manager_trusted_internal_ca` manifest failing when dns policy is set

[k8s-ci-robot]

Welcome @peschmae!

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

[yankay]

/ok-to-test

[floryut]

@peschmae Thank you for the PR 👍
/ok-to-test

[MrFreezeex]

Thank you for the fix :D
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: floryut, MrFreezeex, peschmae

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

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