Consolidate DNS settings

[j-zimnowoda]

The DNS settings are spread among different objects and files, therefore otomi is not able to validate configuration inconsistency. Incorrect settings leads to strange errors in runtime.

Description

The DNS settings are spread among different files and objects.

cluster:
    domain: jeho.eks.otomi.cloud
    provider: aws
    dnsProvider: google # optional to indicated that DNS is different provider than cluster
    region: eu-central-1
    dnsZones: []

# env/charts/cert-manager.yaml
charts:
    cert-manager:
        azureClientSecret: <>
        provider:
            aws:
                route53:
                    region: eu-central-1
            azure:
                azuredns:
                    clientID: <>
                    tenantID: <>
                    subscriptionID: <>
                    resourceGroupName: external-dns
                    hostedZoneName: aks.otomi.cloud

# env/charts/external-dns.yaml
charts:
    external-dns:
        domainFilters: []
            - eks.otomi.cloud
        zoneIdFilters: []
        aws:
            region: eu-central-1
        azure:
            resourceGroup: external-dns
            aadClientId: <>
            aadClientSecret: <secret>

# env/secrets.settings.yaml
google:
    cloudDnsKey: <key>
    projectId: <projectID>

# env/secrets.settings.yaml
azure:
  tenantId: {{ $v.azure.tenantId }}
  subscriptionId: {{ $v.azure.subscriptionId }}

From above a user:

• can define different DNS providers for cert-manager and external-dns
• can define settings for many DNS providers at once but only one shall be used
• is not informed about inconsistent DNS configuration

I would like to propose to consolidate the DNS settings under one object:

```yaml
# settings.yaml
dns:
  properties:
    domain:
      type: list
    dnsZonse:
      type: array
      iteam: string
  oneOf: 
    - aws:
        properties:
          < aws specific properties>
    - azure:
        properties:
          < azure specific properties>
    - google:
        properties:
          <google specific properties>

What do you think?

[Dunky13]

In terms of simplifying the settings I think it would be a nice addition. Especially in light of the single-cluster-repo's and possibly bootstrapping a basic template, having a single clear file that defines what it describes, instead of having to search in multiple files. Would be a nice quality of life improvement. When bootstrapping you can even omit the other cloud providers.

[j-zimnowoda]

@Morriz I see you make 👍
How would you like to be performed. New user story/ task ?

[Morriz]

can you make it part of the flattening refactor? It goes with it imo

[j-zimnowoda]

oh, yeah I think it will be beneficial

[Morriz]

did you manage to squeeze it in then? I kinda did not look ;p

[j-zimnowoda]

yes, I did.