As a platform engineer setting up RHCL to manage my DNS using the new DNS delegation feature, I want to decide which of the clusters I am managing will be the primaries and responsible for publishing my records and which will be secondary so that I can manage credentials and monitoring accordingly. 

A primary is responsible for ensuring the records it discovers are reconciled into the correct state and published to the configured provider.

A secondary is responsible for the finalizer on the records it discovers , the health checks for that record and the status of that record, by definition it does not interact with a provider.

What

When delegating DNSRecords to be reconciled and published by a primary instance of RHCL (from a user perspective)  the platform engineer will need to specify what the role of the DNS Operator is in a particular cluster to ensure consistent behaviour with the DNSRecords in that cluster. There will be two options to chose from, either the DNS Operator is a primary or a secondary. When a DNSOperator is a primary (the default role) it will publish all records that finds whether delegated or not. So effectively it will act as it does now with regular records and when a record is marked as delegated, it will use that record to form an Authoritative record, which is the combined endpoints of all delegated records matched on namespace and the root dns host.

Acceptance Criterea  (done)

• [ ] I can configure the DNS Operator to be a secondary
• [ ]There is documentation provided for how to configure a DNS operator to be a primary or a secondary 
• [ ]When configured as a secondary I should see a status indicating the secondary has reconciled the record and it is ready to be delegated 
• [ ]I can configure a DNS operator to be a primary 
• [ ]When configured as a primary (the default state) I should see DNS records published as normal

Github Issues

GitHub Issues