This repository has been archived by the owner on Dec 16, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 23
DNSRecord is not deleted when DNSPolicy is deleted #628
Labels
kind/bug
Something isn't working
Comments
laurafitzgerald
added a commit
to laurafitzgerald/multicluster-gateway-controller
that referenced
this issue
Oct 20, 2023
… of gateway target for dnspolicy and tlspolicy
laurafitzgerald
added a commit
to laurafitzgerald/multicluster-gateway-controller
that referenced
this issue
Oct 20, 2023
…n of gateway target for dnspolicy and tlspolicy
laurafitzgerald
added a commit
to laurafitzgerald/multicluster-gateway-controller
that referenced
this issue
Oct 25, 2023
…n of gateway target for dnspolicy and tlspolicy
laurafitzgerald
added a commit
to laurafitzgerald/multicluster-gateway-controller
that referenced
this issue
Oct 25, 2023
…n of gateway target for dnspolicy and tlspolicy
laurafitzgerald
added a commit
to laurafitzgerald/multicluster-gateway-controller
that referenced
this issue
Oct 25, 2023
…n of gateway target for dnspolicy and tlspolicy
laurafitzgerald
added a commit
to laurafitzgerald/multicluster-gateway-controller
that referenced
this issue
Oct 25, 2023
…n of gateway target for dnspolicy and tlspolicy
openshift-ci bot
added a commit
that referenced
this issue
Nov 1, 2023
gh-628 fix deletion of dnsrecord and certificates on deletion of gateway target for dnspolicy and tlspolicy
github-project-automation
bot
moved this from In Progress
to Done
in Multicluster Gateway Controller
Nov 2, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When Gateway with bound DNSPolicy and HTTPRoute is deleted and then HTTPRoute and DNSPolicy are deleted associated DNSRecord object stays present and unchanged still referencing deleted gateway.
Steps to reproduce:
The text was updated successfully, but these errors were encountered: