Implement DNS for new cluster bootstrapping

Each cluster should get access to the one DNS zone of our new adorsys.io Domain. The Domain is bought in the root account and then the respective NameserverSection is updated to point to different NS lying in the aws-subaccount.

External DNS needs to have access to this zone and all IAM policies regarding DNSmanagement.

The policy of the ops-github-kaas IAM User (-> #3) needs to be updated:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "sid": "stmt1667481895055",
      "action": [
        "iam:createuser",
        "iam:listgroupsforuser",
        "iam:taguser",
        "iam:deleteuser",
        "iam:putuserpolicy",
        "iam:getuser",
        "iam:getuserpolicy",
        "iam:createaccesskey",
        "iam:listaccesskeys"
      ],
      "effect": "allow",
      "resource": "arn:aws:iam::571075516563:user/externaldns/*"
    }
  ]
}

aws iam put-user-policy --user-name ops-github-kaas --policy-document file://policy.yml --policy-name create-user-external-dns

AC:

[x] a new domain adorsys.io is bought
[x] a new zone is created in a subaccount named adorsys.io
[x] the domain NS section is updated to reflect to the NS of the subaccount zone
[x] the terraform user in github actions is allowed to create a new external-dns IAM User & Policy for DNSManagement

adorsys / ops-adorsys-kubernetes-platform

Implement DNS for new cluster bootstrapping #5