<p>By default, in Kubernetes, an internal address is created when a service is deployed. It is possible to reach this service through the following address: <code>my-svc.my-namespace.svc.cluster-domain.example</code> (<a href="https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#services" rel="nofollow noreferrer">doc reference</a>)</p>
<p>I would like to add more internal addresses to this service when it gets deployed (I use helm to deploy my services). I want to be able to access the same service through <code>my-svc</code>, <code>my-svc-1</code> and <code>my-svc-2</code>. I was wondering if I could add these aliases into the deployment process so it automatically generates multiple entries for the same address.</p>
<p>As a workaround, I read that I can use CoreDNS and add CNAME entries but that's definitely not the optimal choice since I don't know if I can automatically add these entries into CoreDNS when I deploy the service. If that's possible, I'd be happy to know how it can be achieved.</p>

Nate
<p>I didn't try it yet, but maybe you can add Service Type: ExternalName for my-svc-1, my-svc-2 and let them point to the my-svc.my-namespace.svc.cluster-domain.example.</p>
<p>See documentation here: <a href="https://kubernetes.io/docs/concepts/services-networking/service/#externalname" rel="nofollow noreferrer">service-external-name</a></p>
