when using service-upstream: true use FQDN

[lahabana]

Is there an existing issue for this?

• I have searched the existing issues

Does this enhancement require public documentation?

• I have added an Acceptance Criteria item for adding and/or adjusting public documentation (if applicable)

Problem Statement

Currently using this feature we use {service}.{namespace}.svc.
Underneath this means we can do multiple DNS lookups to get the service.

Would it make sense to use {service}.{namespace}.svc.cluster.local to avoid some of the lookups?

Proposed Solution

• Use FQDN instead of partial domain when using service-upstream

Additional information

No response

Acceptance Criteria

• Check if cluster.local is configurable. If it is, reconsider this improvement
• Once done check the DNS lookup go down when using service-upstream: true

[lahabana]

It seems that cluster base DNS is configurable.
We have the options:

1. do the change and make it configurable (maybe as another annotation?)
2. do not do this
3. look at DP DNSConfig to maybe improve this so other way.