feat: allow to configure extraDNSNames to be added to the frontproxy certificate

[nexus49]

This feature is particularly useful when deploying into KCP via a tool like flux from a local kind cluster. Setting these additional dnsNames allows you for example to use the cluster internal service name in a kubeconfig to deploy with flux.

[kcp-ci-bot]

Hi @nexus49. Thanks for your PR.

I'm waiting for a kcp-dev 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.

Details

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.

[embik]

/approve

[kcp-ci-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: embik

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [embik]

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

[kcp-ci-bot]

LGTM label has been added.

Details

Git tree hash: 5f254ec42b987abd7235815be334434ca4768945