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

Prevent random deletions when non-type a record exists. #67

Merged
merged 1 commit into from
Apr 19, 2017
Merged

Prevent random deletions when non-type a record exists. #67

merged 1 commit into from
Apr 19, 2017

Conversation

joshrosso
Copy link

  • ListResourceRecord sets will return another record when the start
    record isn't present, based on current logic this will cause non type-a
    record to be deleted, which can cause cascading delete over time of
    many records.

  • This fix ensures when looking up resource reocord sets, only the rrs
    with the exact hostname requested is returned.

/cc @bigkraig

Resolves #65

- ListResourceRecord sets will return another record when the start
record isn't present, based on current logic this will cause non type-a
record to be deleted, which can cause cascading delete over time of
many records.

- This fix ensures when looking up resource reocord sets, only the rrs
with the exact hostname requested is returned.

Resolves #65
@joshrosso joshrosso self-assigned this Apr 19, 2017
@bigkraig bigkraig merged commit 1adffb1 into kubernetes-sigs:master Apr 19, 2017
bigkraig added a commit that referenced this pull request Oct 1, 2018
Prevent random deletions when non-type a record exists.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

controller deletes route53 entries not created by ingress
2 participants