On Wednesday, August 2, 2017, <rgoncal...@gmail.com> wrote: > Hi Rodrigo. Thanks for answering. > > Yes, you're right. I should not talk about the containers but pods.. let > me give another example to clarify. Suppose we have the following resources: > > ----------------POD > apiVersion: v1 > kind: Pod > metadata: > labels: > a: "1" > name: sample-pod > spec: > containers: > - name: sample-test-pod > ... > -------------RC > apiVersion: v1 > kind: ReplicationController > metadata: > name: sample-rc1 > spec: > replicas: 1 > selector: > a: "1" > ... > ---------- > > After creating this two resources we have one single pod (sample-rc1 > "adopts" existing pod...nice). But, if we create another replication > controller with the same selector, changing only the rc name (ex. > sample-rc2), another pod is launched. Didn't expect this second pod > instance...
Hmm, are you sure that is going to happen? If both RCs fight for their resources, it might even be unstable for a while but for sure not 2 containers when there should be only 1. > > I know my scenario does not make much sense. However, in the tutorial > mentioned above this > Didn't see any tutorial. Can you please be more specific? :) > > happens and it's usage is at least reasonable. > Having two RCs fight for their resources is not reasonable. I really doubt this is not a typo or something. Would be really weird. -- 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.
