-
Notifications
You must be signed in to change notification settings - Fork 40k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get vagrant $vm_mem value from environment #3792
Get vagrant $vm_mem value from environment #3792
Conversation
I am good with this, and I see no reason to separate master and minion settings at this time. Sent from my iPhone
|
I added this locally to my Vagrantfile as: Give VM 512MB of RAM by default$vm_mem = (ENV['VM_MEM'] || 512).to_i |
@derekwaynecarr you can commit this now! |
but @ryfow would need to rebase first. |
0739508
to
0d6ca95
Compare
Has Vagrant try to read `KUBERNETES_MEMORY` environment varilable when setting $vm_mem. fixes kubernetes#3792
0d6ca95
to
749ae3d
Compare
I rebased and changed default to 1024. On Wed, Mar 4, 2015 at 2:23 PM, Eric Tune notifications@github.com wrote:
|
LGTM |
Get vagrant $vm_mem value from environment
Has Vagrant try to read `KUBERNETES_MEMORY` environment varilable when setting $vm_mem. fixes #3792
I'd like to put something in my environment similar to NUM_MINIONS to control the amount of memory Vagrant VMs get. I'm happy to submit a pull request, but would like feedback on the environment variable names to expedite things.
Some options would be: KUBERNETES_MEMORY, KUBERNETES_RAM, KUBE_MEMORY, KUBE_RAM.
Or, Master and Minion could be split up, lending variable names such as KUBERNETES_MASTER_MEMORY, KUBERNETES_MINION_MEMORY. If we're doing that, it's probably safe to drop the KUBERNETES_ on the thought MASTER_MEMORY is specific enough to Kubernetes.