Question: root?

Asked By
chrislovecnm
Asked At
2017-12-28 20:05:56

Found 15 possible answers.

User Answered At Possible Answer
hnajafi 2017-12-28 20:06:13 I am getting this error now in logs : Dec 28 20:05:26 ip-10-83-179-249 cloud-final[684]: == Failed to curl https://kubeupv2.s3.amazonaws.com/kops/1.8.0/linux/amd64/nodeup.sha1 . Retrying. == I guess it's a network issue (no network to outside) Dec 28 20:05:26 ip-10-83-179-249 cloud-final[684]: All downloads failed; sleeping before retrying
chrislovecnm 2017-12-28 20:07:19 do you need to setup a https proxy?
hnajafi 2017-12-28 20:07:51 now that it's private I guess so
chrislovecnm 2017-12-28 20:08:33 normally the answer is no
hnajafi 2017-12-28 20:08:41 oh. ok
chrislovecnm 2017-12-28 20:08:45 but it depends on how your network is setup love to see you there also we have office hours for developers listed on the README @haad even if you are not a go guru, we are happy to talk you through issues
mrballcb 2017-12-28 20:46:55 @chrislovecnm I just created a feature request for kops (4164) to add a cli option. I am not a go guru so I was able to get the cli parsing and logic to call a function, but I don’t have the go skills (yet) to make the meat of the function. Of course, everything is subject to “that’s a stupid idea Todd, why would you want to do something like that” feedback :slightly_smiling_face: I do have what work I started up in a github repo that I forked from kubernetes/kops. I did the work on master, but master has diverged a bit from the kops 1.8.0 release, so I applied the two commits to the release branch, built a kops binary from that, and verified that it works the same on a rolling-update.
chrislovecnm 2017-12-28 20:56:54 Lol :laughing: Admittedly I am not a go guru Issue? We have just a few already Admittedly I am not a huge fan of more cli options
mrballcb 2017-12-28 20:58:40 4164 :
...and wait for the admin to approve before continuing with the next node.
I would like to add a kops cli option, for example named --interactive, that would pause after each instance gets updated. It should print out a prompt such as:
Continue rolling update? (Y/n) Sometimes when doing a kops rolling-update, I would like to ssh to a new master or new node to check that some component is configured properly, has started, or just in general look around to make sure it’s behaving properly. If I know a breaking change is coming, I’d like to have kops wait after each host for me to allow it to continue with the rolling update.
chrislovecnm 2017-12-28 20:59:41 That actually makes a lot of sense You can also get some of the same effect by doing on ig at a time I do like that a a lot
mrballcb 2017-12-28 21:01:40 I have the framework in place. I was able to grok enough go so that the cli parsing is in place and a function gets called when it gets triggered (feels a lot like perl TBH), but I don’t know enough go (yet) to print out the prompt, wait for an answer, and take action. It shouldn’t be difficult, but I need to figure out the best way to do it. perl…maybe I’m just being inflamatory… lol
chrislovecnm 2017-12-28 21:02:13 Does kubectl have the functionality? OO Perl :runnabear: I have written way to much Perl in my time :P
mrballcb 2017-12-28 21:03:33 Hmmm, don’t think kubectl has a mode like this, but also have not researched kubectl enough. And yeah, perl and shell are my go-to for getting stuff done :slightly_smiling_face:
chrislovecnm 2017-12-28 21:03:33 We vendor kubectl, so we may be able to reuse there code
mrballcb 2017-12-28 21:03:49 Let me dig a bit.

Related Questions