Thanks for the inputs. Using annotations and updating them using patch
serves the purpose.
- Keshava
On Saturday, December 16, 2017 at 1:31:51 PM UTC+5:30, Timo Reimann wrote:
>
> Actually, it's the Deployment's pod template (.spec.template) that needs
> to host the annotation. Always gettin
Actually, it's the Deployment's pod template (.spec.template) that needs to
host the annotation. Always getting confused.
https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#updating-a-deployment
has it formally defined.
--
You received this message because you are subscribed
I believe you can also update / create an annotation inside the pod spec's
metadata section if you fear that an environment variable might collide or just
pollute your application's env var space.
More discussions, tips, and related issues regarding the subject of forced
restarts can be found i
What I have seen several people do for this is to increment an env
var, or use a timestamp - something trivial that doesn't impact the
app, but forces a restart. Updating an env var can not ever be done
without restart.
On Fri, Dec 15, 2017 at 2:00 AM, Keshava Bharadwaj
wrote:
> Hi,
>
> We have
