added rolling update to deamonset

[tthebst]

updated cloudwatch-agent-statsd, fluentd and nvidia to perform rolling update in cluster update command.

closes #630

---

checklist:

• [ x] run make test and make lint
• [x ] test manually (i.e. build/push all images, restart operator, and re-deploy APIs)
• [ x] update examples
• [x ] update docs and add any new files to summary.md (view in gitbook after merging)
• [x ] cherry-pick into release branches if applicable
• [ x] alert the dev team if the dev environment changed

[CLAassistant]

All committers have signed the CLA.

[deliahu]

@tthebst thank you for your contribution, this is awesome! I'm glad you were able to get the development workflow set up; although we've tried to document it clearly, it's definitely not a simple process. Feel free to reach out on gitter (https://gitter.im/cortexlabs/cortex) or GitHub issues if you have any questions or run into any issues.

I reviewed the PR, and left a few comments. I'll await your responses, and I plan on testing it out on my end either tomorrow or early next week.

Lastly, do you mind signing the CLA?

Thanks again for your work on this! I think we'll be able to get it in for our next release (we're planning on cutting the release candidate mid to end next week).

[deliahu]

@tthebst Thanks for addressing my comments! I'll try this out on my end soon, and then I'll merge it in.

[tthebst]

@deliahu Thank you for your feedback. These are my first real contributions to an opensource project. I like the project and will try to find some good other addressable issues

[deliahu]

LGTM, thanks again for your contribution!

[deliahu]

@tthebst sounds great! All of the features/improvements/bugs that are on our radar are listed in our GitHub Project. That list may be a bit overwhelming, so (as you probably noticed when you searched for this issue) we have created the "good first issue" label and added it to some of our issues. That said, the other ones are all fair game too, and some of them may be good first issues as well - we plan on making a pass on all of our issues and seeing if we can add the label to more of them.

Feel free to let us know which ones sound interesting to you. We'd be able to advise on which one might be best to start with based on your interests and the scope of the task, as well as point you in the right direction (since some of our descriptions are vague and and some of our issues need additional design thought).