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.

Sign up for GitHub

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

Jump to bottom

DNSEntries with existing DNS recordsets should go to state "stale" if no DNSProvider is available #314

Open
MartinWeindel opened this issue Aug 21, 2023 · 0 comments
Open

DNSEntries with existing DNS recordsets should go to state "stale" if no DNSProvider is available #314

MartinWeindel opened this issue Aug 21, 2023 · 0 comments
Labels
kind/bug Bug lifecycle/stale Nobody worked on this for 6 months (will further age)

Comments

@MartinWeindel
Copy link
Member

What happened:
A DNSEntry should not go to state Error if its DNSProvider is deleted and the DNS recordset is already existing. Instead if should go to state Stale. The difference is that in state Stale the DNS recordset is kept, but for Error it is cleaned up.

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know:

Environment:
@gardener-robot gardener-robot added the lifecycle/stale Nobody worked on this for 6 months (will further age) label Apr 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug Bug lifecycle/stale Nobody worked on this for 6 months (will further age)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@MartinWeindel @gardener-robot