Remove ManagedZone API

[mikenairn]

Part of : #166

Removes the ManagedZone API and all related code and docs.

The DNSRecord resource no longer has a reference to a ManagedZone, instead a new providerRef field is added which references a single dns provider secret. The contents of this secret are identical to what was previously used by the ManagedZone.dnsProviderSecretRef.

apiVersion: v1
kind: Secret
metadata:
  name: myawsroute53
type: kuadrant.io/aws
stringData:
 AWS_ACCESS_KEY_ID: "xyz"
 AWS_SECRET_ACCESS_KEY: "12345"

The secrets do not contain information about what zone a record will be published into, instead a zone in the dns provider will be assigned to a DNSRecord via lookup on it's first reconcile. What zone will be used, if any, is determined by the zones available via the credentials in the dns provider secret. Once the zone is assigned the information of the zone used is stored in the DNSRecord status and used by all requests for this record to the provider thereafter:

"zoneDomainName": "mn.example.com",
"zoneID": "/hostedzone/12345abcd"

Note: CI-E2E / E2E Test Suite (pull_request_target) CI job will fail until it's merged. The e2e test is being tested as a branch job for now see.

ToDo:

• Handle multiple zones with the same dns name when finding a suitable zone to assign to a record

[mikenairn]

ToDo remove before merge

[mikenairn]

ToDo revert before merge

[mikenairn]

I added this provider builder as a public API so it could be used in both the tests here and in kuadrant operator. Unsure of the best location for it, I'm not really sure if an API like this should be inside the api/v1alpha1 package, or just be outside and always work with the latest version of the APIs.

[maleck13]

is it possible to give more info than this? The way I read it, this can happen if we failed to set a zid or domain inside the zone. As this is a delete also makes me wonder if this could happen. I guess if a record was created and there was a bad credential and then you tried to delete it?

[mikenairn]

Yes, if the record is created and for whatever reason it isn't able to assign a zone e.g. invalid credentials, no zone that matches the root host etc... we shouldn't try and cleanup when the record is deleted since it won't have been able to create anything in the first place.