cAdvisor Release Plan (EXTERNAL) - Invitation to comment

22 views
Skip to first unread message

Tim St. Clair (via Google Docs)

unread,
Jul 8, 2016, 1:33:44 PM7/8/16
to kuberne...@googlegroups.com, google-c...@googlegroups.com, kubernete...@googlegroups.com
Tim St. Clair has invited you to comment on the following document:
Sender's profile photoThere have been several conversations around modifying the cAdvisor release plan, so I am consolidating the plan into a single doc.
Google Docs: Create and edit documents online.Logo for Google Docs

Brandon Philips

unread,
Jul 14, 2016, 1:16:20 AM7/14/16
to Tim St. Clair, kuberne...@googlegroups.com, google-c...@googlegroups.com, kubernete...@googlegroups.com, Fabian Reinartz
Hey Tim-

This plan looks reasonable. Thanks for putting it together.

Would inverting the cAdvisor and Kubernetes relationship help development? By that I mean putting the core of cAdvisor into kubernetes.git and then making standalone cAdvisor consume exported libraries.

Cheers,

Brandon

--
You received this message because you are subscribed to the Google Groups "kubernetes-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-de...@googlegroups.com.
To post to this group, send email to kuberne...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/001a114ab9c2374eb90537233484%40google.com.
For more options, visit https://groups.google.com/d/optout.

Tim St. Clair

unread,
Jul 14, 2016, 4:41:23 PM7/14/16
to Brandon Philips, kuberne...@googlegroups.com, Containers at Google, kubernetes-sig-node, Fabian Reinartz
That's an interesting suggestion, but at the moment the trend is to move things out of Kubernetes. I will keep this in mind as a possibility, but probably not for 1.4.
Reply all
Reply to author
Forward
0 new messages