On Fri, Sep 16, 2016 at 11:19 AM, Rodrigo Campos <rodr...@sdfg.com.ar>
wrote:

> On Fri, Sep 16, 2016 at 11:14:41AM -0700, 'Jungho Ahn' via Kubernetes user
> discussion and Q&A wrote:
> > Thanks Rodrigo,
> >
> >
> >
> > On Fri, Sep 16, 2016 at 11:07 AM, Rodrigo Campos <rodr...@sdfg.com.ar>
> > wrote:
> >
> > > On Fri, Sep 16, 2016 at 10:53:45AM -0700, 'Jungho Ahn' via Kubernetes
> user
> > > discussion and Q&A wrote:
> > > > Hello,
> > > >
> > > > I have an app which configuration can be updated dynamically without
> > > > restarting it.
> > > > I'm wondering if there is any way to
> > > >    - send a new configuration to all replicas
> > >
> > > You can use a configmap for your config, and when changing it, it will
> be
> > > updated on the pods.
> > >
> > > But, of course, if you screw up your config (syntax error), it might
> not be
> > > good and crash your app (depends on your app). It's probably safer to
> > > create a
> > > new configmap and deploy again using it.
> > >
> > > It's way better to create again than to keep state and "update", IMHO.
> > > It's part
> > > of doing the switch to containers, IMHO, and takes some time :-)
> > >
> >
> > Yes, that's the reason why I want to update it without restarting it.
>
>
> I don't think we are on the same page. I say it's better to create rather
> than
> "update".
>
>
> > > >    - check the status of all replicas
> > >
> > > What do you mean with this? Not sure I understand.
> > >
> >
> > Sorry, let me explain more details.
> >
> > I have an app that watch a certain resources (like google cloud storage)
> > and then add newly added resources or drop the deleted resources.
> > In this case, I'd like to know whether all replicas finish to add or drop
> > resources after resources has been changed.
>
> You should do that in the same way you do it today, it's totally apart from
> kubernetes.
>

Sorry, I don't understand. I want to make sure all replicas are up to date.
Is there a way to talk to all replicas that are deployed in kubernetes for
this?


>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Kubernetes user discussion and Q&A" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/kubernetes-users/D8b6zT2y4uI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> kubernetes-users+unsubscr...@googlegroups.com.
> To post to this group, send email to kubernetes-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/kubernetes-users.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Jungho Ahn

-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q&A" 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, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to