Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[spike] Configuring alternative registries #321

Open
philbrookes opened this issue Nov 28, 2024 · 0 comments
Open

[spike] Configuring alternative registries #321

philbrookes opened this issue Nov 28, 2024 · 0 comments

Comments

@philbrookes
Copy link
Collaborator

philbrookes commented Nov 28, 2024

We need to answer some questions around what having multiple registry options in the dns operator should look like:

  • how does the DNS Operator know which registry to use (runtime, policy, etc.)
  • how to send configuration information for registries to the DNS Operator (i.e. redis auth details)
  • what happens if DNS Operators are configured on the same zone but with different registries (register registries in a TXT record to ensure congruency?)
  • Are there any issues we might find, based on our existing assumption of a TXT registry
  • What happens when more than 20 controllers run against the same zone when that limit is lifted (e.g. 50 controllers using redis registry)

As DynamoDB is already coded as a registry in externalDNS it might be faster to answer these questions using DynamoDB before moving to #322

@philbrookes philbrookes transferred this issue from Kuadrant/kuadrant-operator Nov 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

1 participant