feat: add support for load balancer, listener, and pool tags annotations

[alexanderstephan]

Superceds #3058.

What this PR does / why we need it:
This PR adds support for the add tags to load balancer, listener, and pool via the service annotations in cloud-provider-openstack (OCCM).

Which issue this PR fixes(if applicable):
fixes #3032 #2327

Special notes for reviewers:
You can add annotations to the service like:

loadbalancer.openstack.org/listener-tags: "tags-test"
loadbalancer.openstack.org/load-balancer-tags: "tags-test"
loadbalancer.openstack.org/pool-tags: "tags-test"

Then check if the tags have been added to the service's load blancer(the service's type should be load balancer)

Release note:

[openstack-cloud-controller-manager] Support adding tags to load balancers, listeners, and pools via Service annotations.

[kubernetes-prow]

[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 stephenfin for approval. For more information see the Code Review Process.

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

Details

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

[kubernetes-prow]

Welcome @alexanderstephan!

It looks like this is your first PR to kubernetes/cloud-provider-openstack 🎉. 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/cloud-provider-openstack 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. 😃

[kubernetes-prow]

Hi @alexanderstephan. Thanks for your PR.

I'm waiting for a kubernetes 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-sigs/prow repository.

[kayrus]

/ok-to-test

[kayrus]

Thanks for the PR. See my comments.

[kayrus]

The PR looks much better now. I left one nit comment. @yahor-kurachkin could you take a look at this PR when you have a chance?

[yahor-kurachkin]

The PR looks good. Since I also working on loadbalancer.go at the moment, there will likely merge conflicts. I don't mind to resolving them on my side

[kubernetes-prow]

@alexanderstephan: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-cloud-provider-openstack-check	a673385	link	true	/test pull-cloud-provider-openstack-check

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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-sigs/prow repository. I understand the commands that are listed here.