Re: [kubernetes-users] Rolling restart of pods in deployment

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

Re: [kubernetes-users] Should apps bind to 0.0.0.0 or 127.0.0.1 or pod_ip?

Makes sense. Thanks. -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group,

Re: [kubernetes-users] Should apps bind to 0.0.0.0 or 127.0.0.1 or pod_ip?

Well, binding to 127 addresses means nobody else can access you. Binding to a specific IP is just not the "normal" thing to do in network programming, in my experience. Unless you know something specific, 0 is the best option. E.g. you might have more than one network interface, and 0 is the

Re: [kubernetes-users] Should apps bind to 0.0.0.0 or 127.0.0.1 or pod_ip?

Thanks for your reply. Not port-forwarding from inside. Just from host (using minikube). I happened to write an app that binds to 127.0.0.1 and stumbled on this behavior (inconsistency?) Is there somewhere you could point me to that talks about 0 being the normal way to go? Just trying to

Re: [kubernetes-users] Should apps bind to 0.0.0.0 or 127.0.0.1 or pod_ip?

What are you doing with port-forward inside your pod? Binding to 0 is the "normal" way to do things unless you have reason to dO otherwise. On Fri, Dec 15, 2017 at 4:42 PM, Dietrich Schultz wrote: > Just started exploring kubernetes, and ran into this. Haven't found

[kubernetes-users] Should apps bind to 0.0.0.0 or 127.0.0.1 or pod_ip?

Just started exploring kubernetes, and ran into this. Haven't found any docs or clear statements of best practice. The only thing I found was this note in the container.v1 spec describing the port field: Any port which is listening on the default "0.0.0.0" address inside a > container will be

Re: [kubernetes-users] Rolling restart of pods in deployment

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

[kubernetes-users] Rolling restart of pods in deployment

Hi, We have a simple deployment of 3 replicas. We have a requirement to have a kubernetes cron job , that would need to restart(rolling restart) the pods in the deployment. Use-case: we use certs in our services in