Skip to content

Conversation

gifff
Copy link
Contributor

@gifff gifff commented May 17, 2025

Fix #70

Rough idea for getting the hostnames diff between current state and previous state.

configmap *corev1.ConfigMap
fallbackTarget string
cfAPI *cf.API
removedHostnames []string
Copy link
Owner

Choose a reason for hiding this comment

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

Would this have hostnames from all tunnel bindings? I don't particularly like that tbh, where modifying one can result in a cleanup from another binding.

Could we do something per tunnelBinding utilizing status to keep track of previous, and delete them if the spec is changed to a new one?

Copy link
Contributor Author

@gifff gifff May 19, 2025

Choose a reason for hiding this comment

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

No, it only holds removed hostnames for a particular tunnelBinding.

But the way the code is put together, the removedHostnames are shared across tunnelBinding reconciliation. This is fine as long as the MaxConcurrentReconciles is not set (defaults to 1) which it is now, and would get problematic if the concurrency is set larger than 1.

@gifff gifff force-pushed the feat/cleanup-dns branch from 6ef27cb to 5bfb355 Compare July 6, 2025 10:04
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.

Modifying fqdn in an existing TunnelBinding does not clean up DNS records

2 participants