Skip to content
This repository has been archived by the owner on Mar 17, 2024. It is now read-only.

Automatically roll Deployment when ConfigMap change #176

Merged
merged 1 commit into from
Nov 2, 2020
Merged

Automatically roll Deployment when ConfigMap change #176

merged 1 commit into from
Nov 2, 2020

Conversation

robsonpeixoto
Copy link
Contributor

No description provided.

@lightbend-cla-validator
Copy link

Hi @robsonpeixoto,

Thank you for your contribution! We really value the time you've taken to put this together.

Before we proceed with reviewing this pull request, please sign the Lightbend Contributors License Agreement:

https://www.lightbend.com/contribute/cla

@seglo
Copy link
Owner

seglo commented Nov 2, 2020

Interesting. IIUC this will recreate the replicaset any time the configmap is changed (via helm or otherwise).

For reference: https://medium.com/flant-com/configmaps-in-kubernetes-f9f6d0081dcb

@seglo seglo merged commit fb0aaaa into seglo:master Nov 2, 2020
@robsonpeixoto robsonpeixoto deleted the chart/force-new-deployment-if-cm-changes branch January 31, 2021 11:51
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants