Support Multiple Service Registrations

[lawliet89]

Is your feature request related to a problem? Please describe.

I would like to use both the Consul and Kubernetes service registration for different service discovery use cases.

Describe the solution you'd like

Support multiple service registration.

Describe alternatives you've considered

Consul sync using consul-k8s, but this does not sync the active replica to Consul.

Explain any additional use-cases
If there are any use-cases that would help us understand the use/need/value please share them as they can help us decide on acceptance and prioritization.

Additional context
Add any other context or screenshots about the feature request here.

[mjarmy]

Can you describe your potential use cases in some more detail?

[lawliet89]

I have multiple kubernetes clusters with consul deployed. The consul clusters are WAN joined. They can discover services in each other. Consul k8s syncs the kubernetes services fine but direct service registration from vault adds additional tags like "active" and "standby" which are useful.

At the same time, I would like to use the kubernetes service registration feature which labels the pod that contain the active vault server in combination with kubernetes service label selectors to only serve traffic from the kubernetes service (load balancer, node port, etc.) to the active vault pod.