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

A question about maps #116

Open
tuxillo opened this issue Jan 30, 2025 · 2 comments
Open

A question about maps #116

tuxillo opened this issue Jan 30, 2025 · 2 comments

Comments

@tuxillo
Copy link
Contributor

tuxillo commented Jan 30, 2025

Acording to the README file, it is possible to use maps but in the example given the map files are assumed to be there.

Now, there are a couple ways to get maps but the most simplest might be just updating the map files (for example, updating a configmap from which a projected volume is created) and then triggering a reload, so I was wondering if there are any plans to add a functionality to handle maps so that any change in them produces a reload. If not, do you know of any solution that we could use?

@m-terra
Copy link
Collaborator

m-terra commented Mar 10, 2025

hi @tuxillo
in kubernetes, when any file is changed in a mounted config map, this triggers a new symlink to be made on parent level. so to the container all files have changed and in combination with the reload wrapper this always triggers a reload. it's not quite transparent but please feel free to PR on the readme or any other files
cheers

@tuxillo
Copy link
Contributor Author

tuxillo commented Mar 10, 2025

Ok thanks @m-terra, I'll have a look and see how it behaves. The problem I have is that I am going to have a large amount of maps in a file that at some point will exceed the 1MB configmap/secret limit so I have to combine several into a projected volume (that's what I'm doing now without the operator with haproxy from its helm chart).

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

2 participants