PS

> 
> Think of it this way - if the deployment scales up, clearly we should add 
> more volumes.  What do I do if it scales down?  Delete the volumes?  Hold on 
> to them for some later scale-up?  For how long?  How many volumes?   


Seeing that scaling happens 1 pod at a time, having n+1 volumes where n is the 
number of current pod replicas would make the most sense. Especially if time to 
provision a volume < time to determine another pod is needed and to scale up by 
1 pod.

-- 
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.
  • Re: [kubernetes-us... 'Tim Hockin' via Kubernetes user discussion and Q&A
    • Re: [kubernet... Naseem Ullah
      • Re: [kube... 'Tim Hockin' via Kubernetes user discussion and Q&A
        • Re: [... Naseem Ullah
          • R... 'Jing Xu' via Kubernetes user discussion and Q&A
            • ... Naseem Ullah
              • ... 'Tim Hockin' via Kubernetes user discussion and Q&A
              • ... Naseem Ullah
          • R... 'Tim Hockin' via Kubernetes user discussion and Q&A
            • ... Naseem Ullah
            • ... Naseem Ullah
        • Re: [... David Rosenstrauch
          • R... 'Tim Hockin' via Kubernetes user discussion and Q&A
            • ... David Rosenstrauch
          • R... Naseem Ullah

Reply via email to