Allow multiple provider specific annotations of same type

[roehrijn]

Description

External DNS already supports exposing a single K8s service behind multiple hostnames by using the external-dns.alpha.kubernetes.io/hostname annotation with a comma-seperated list of hostnames in its value. One would do this for example for making a service availible with a technical, static hostname and a DNS load-balancer, like Route53 can act as, at the same time.
However, when defining additonal annotations on the service, e.g. external-dns.alpha.kubernetes.io/aws-weight this always applies to all the hostnames of the service. This makes it impossible to define different weights for different hostnames on the same service. At the same time it is not possible that an annotation only applies to a single one and not all the hostnames of a service.

This PR implements a solution to make exactly the described configuration possible by introducing a kind of "string map" notation in the annotations' values.

For example:

external-dns.alpha.kubernetes.io/hostname: my.foo.app, my.foo.internal
external-dns.alpha.kubernetes.io/aws-weight: my.foo.app=100

would define the two hostname my.foo.app and my.foo.internal, whereas a load balancing weight is only set for my.foo.app.

Checklist

• Unit tests updated
• End user documentation updated

_{Jan Roehrich [email protected], Mercedes-Benz Tech Innovation GmbH, legal info/Impressum}

[k8s-ci-robot]

[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 mloiseleur 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

[k8s-ci-robot]

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

[mloiseleur]

/ok-to-test

[mloiseleur]

Thanks. It looks good, implementation is light and it's documented 👍
/lgtm
/assign @Raffo