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

RFC 00010 distributed DNS #70

Open
wants to merge 41 commits into
base: main
Choose a base branch
from
Open

RFC 00010 distributed DNS #70

wants to merge 41 commits into from

Conversation

maleck13
Copy link
Collaborator

@maleck13 maleck13 commented Mar 4, 2024

Replaces #55

@maleck13 maleck13 changed the title Update rfc 0008 Update rfc 0008 distributed DNS Mar 5, 2024
rfcs/0008-distributed-dns.md Outdated Show resolved Hide resolved
rfcs/0008-distributed-dns.md Outdated Show resolved Hide resolved
rfcs/0008-distributed-dns.md Outdated Show resolved Hide resolved
rfcs/0008-distributed-dns.md Outdated Show resolved Hide resolved
rfcs/0008-distributed-dns.md Outdated Show resolved Hide resolved
rfcs/0008-distributed-dns.md Outdated Show resolved Hide resolved
@mikenairn
Copy link
Member

Couple of questions/thoughts, but nothing major.

/lgtm

rfcs/0008-distributed-dns.md Outdated Show resolved Hide resolved
@maleck13
Copy link
Collaborator Author

@ficap I think your change requests are complete now

When a DNSRecord is being removed, the following must be successfully completed before the finalizer can be removed:
- Remove the local clusters records and targets from the relevant zone
- Perform a prune on the relevant root host
- Apply the results of the prune to the DNS Provider
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also delete healthchecks if needed (how to detect it - no records left?)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a good point. @philbrookes any thoughts on when we delete a health check? I would think it is part of the dead end check? IE if there is no endpoints for a given rootHost then remove?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

had to change the rfc number which is why this shows as outdated

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ficap I have updated this now. Note I had to change the file name due to the rfc number changing

@david-martin
Copy link
Contributor

@philbrookes I noticed rfc 8 is already on main while looking through a couple other prs https://github.com/Kuadrant/architecture/blob/main/rfcs/0008-kuadrant-release-process.md

@maleck13 maleck13 changed the title Update rfc 0008 distributed DNS Update rfc 0009 distributed DNS Mar 12, 2024
@ficap
Copy link

ficap commented Mar 12, 2024

@maleck13 I think it would be also beneficial to list here all cases that can happen during plan creation and how they should be resolved. So that we can discuss possible ambiguous cases prior to implementation here.

@maleck13
Copy link
Collaborator Author

@maleck13 I think it would be also beneficial to list here all cases that can happen during plan creation and how they should be resolved. So that we can discuss possible ambiguous cases prior to implementation here.

Can you give an example of what you are expecting

@ficap
Copy link

ficap commented Mar 12, 2024

@maleck13 I think it would be also beneficial to list here all cases that can happen during plan creation and how they should be resolved. So that we can discuss possible ambiguous cases prior to implementation here.

Can you give an example of what you are expecting

Something like the "use cases to ensure" in this issue Kuadrant/dns-operator#49 . Basically have a set of rules that would apply during plan creation.

@maleck13 maleck13 changed the title Update rfc 0009 distributed DNS RFC 0009 distributed DNS Mar 14, 2024
@maleck13 maleck13 self-assigned this Mar 14, 2024
@@ -0,0 +1,291 @@
# Distributed DNS Load Balancing
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

'0009' already taken.

@maleck13 maleck13 changed the title RFC 0009 distributed DNS RFC 00010 distributed DNS Jun 27, 2024
@alexsnaps alexsnaps added the RFC Request For Comments label Aug 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
RFC Request For Comments
Projects
Status: Ready For Review
Development

Successfully merging this pull request may close these issues.

7 participants