Support kind: Service as resource

[daniel-ciaglia]

Is your feature request related to a problem? Please describe.
historically a bunch of microservices were managed in a single namespace. Separating them into distinct namespaces changes the DNS names of them and requires a delicate orchestrated change of configuration with likely downtimes of downstream services

Describe the solution you'd like
Utilising kind service with type: ExternalName we would be able to gradually shift the internal traffic to the new deployment living in its separate nemspace without touching dependecies

Describe alternatives you've considered
Implementing a serviceMesh would give similar DNS otions (and more) but is out of scope of the current project phase