We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I was thinking this could be done using an annotation on a deployment or RC, something like:
annotations: konfd.io/track-configmaps: foo, blah, blerg konfd.io/track-secrets: asdf
Or possibly by inspecting the resource to find any references to configmap/secret volumes or field refs.
annotations: konfd.io/update-on-changes: true
I imagine this could eventually apply to jobs, daemonsets, statefulsets, etc. also.
The text was updated successfully, but these errors were encountered:
@blakebarnett I love this idea, let me think about it a bit more and flush out a design.
Sorry, something went wrong.
No branches or pull requests
I was thinking this could be done using an annotation on a deployment or RC, something like:
Or possibly by inspecting the resource to find any references to configmap/secret volumes or field refs.
I imagine this could eventually apply to jobs, daemonsets, statefulsets, etc. also.
The text was updated successfully, but these errors were encountered: