amazon web services - Increase ROOT_SIZE of minion in aws kubernetes cluster -

-

i making kubernetes cluster in aws. using kubernetes version 1.0.6. things necessary running cluster works fine in version. need increae root disk size of minions. created default 8gb. want them 40gb instead. using t2.micro cluster.

the problem there env variable minion_root_disk_size in version : master, 1.1.0-alpha.1. in 1.0.6 there no env variable in name. , setting variable in 1.0.6 did not work work 1.1.0-alpha.1. can't use pre release or can't jump 1.0.6 1.1.0-alpha.1. need increase minions , masters root disk size.

how can achive that?

the config file both version here:

v1.1.0-alpha1

v1.0.6 using

for still have problem here solution. if have kubernetes file u can achive editing

"cluster/aws/util.sh" file.

find block_device_mappings , add this

{"devicename":"/dev/sda1","ebs":{"volumesize":40, "volumetype": "gp2"}

this feild string u need add \ before every "

{\"devicename\":\"/dev/sda1\",\"ebs\":{\"volumesize\":40, \"volumetype\": \"gp2\"}

this create gp2 volume 40gb of size , minion , master's root disk.


Comments

Post a Comment

Popular posts from this blog

java - Date formats difference between yyyy-MM-dd'T'HH:mm:ss and yyyy-MM-dd'T'HH:mm:ssXXX -

-
i trying parse date 2014-12-03t10:05:59.5646+08:00 using these 2 formats: yyyy-mm-dd't'hh:mm:ss yyyy-mm-dd't'hh:mm:ssxxx when parse using yyyy-mm-dd't'hh:mm:ss works fine, when parse yyyy-mm-dd't'hh:mm:ssxxx parseexception thrown. which correct format parse date , difference between these 2 formats? note : cannot use joda :( those valid formats: yyyy-mm-dd't'hh:mm:ss.sssz >>> e.g.: 2001-07-04t12:08:56.235-0700 yyyy-mm-dd't'hh:mm:ss.sssxxx >>> e.g.: 2001-07-04t12:08:56.235-07:00 edit: btw, "x" refer (iso 8601 time zone)
Read more

c# - Get rid of xmlns attribute when adding node to existing xml -

-
i have xml-file: <ns2:root xmlns:ns2="namespace"> <ns2:a> <ns2:b>some content</b> <ns2:c>some content</c> <ns2:d>some content</d> </a> </root> i need add new node in specific place, code is: var doc = xdocument.load(file); xnamespace ns2 = "namespace"; doc.element(ns2 + "root").element(ns2 + "a").element(ns2 + "c").addafterself( new xelement(ns2+"new", new xelement("new1", new xelement("new2","some content"), new xelement("new3", "some content")))); the output is: <ns2:root xmlns:ns2="namespace"> <ns2:a> <ns2:b>some content</b> <ns2:c>some content</c> <ns2:new> <new1 xmlns=""> <new2>some content</new2> ...
Read more