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

Proposal: store DNS state in ConfigMap #130

Open
GrigoriyMikhalkin opened this issue Nov 30, 2022 · 0 comments
Open

Proposal: store DNS state in ConfigMap #130

GrigoriyMikhalkin opened this issue Nov 30, 2022 · 0 comments

Comments

@GrigoriyMikhalkin
Copy link
Contributor

At the moment we store DNS state in the CWNP status. DNS state is required to quickly restore nftables rules in case of machine reboot. Here is a response about Status field limit, which is limited only by etcd entry size(by default 1.5MB). So the there shouldn't be any restrictions to store the state in the object's Status.

Still, there's question if it can be optimized in terms of user experience. Aforementioned response proposes to use ConfigMap for storing big statuses. Which(potentially) can lead to some performance improvements. Also, Status intention is to show the operational state. And in our case it's used for caching. Moving caching to ConfigMap looks like a more "clean" solution.

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

No branches or pull requests

1 participant