On 20 September 2017 at 01:05, Rodrigo Campos <rodr...@sdfg.com.ar> wrote: > On Tue, Sep 19, 2017 at 09:08:22PM +0300, Lubomir I. Ivanov wrote: >> On 19 September 2017 at 17:54, Rodrigo Campos <rodrig...@gmail.com> wrote: >> > >> > >> > On Tuesday, September 19, 2017, Lubomir I. Ivanov <neolit...@gmail.com> >> > wrote: >> >> >> > >> > To make sure your setup is okay, checkout an stable branch or tag, and try >> > to make that work first. >> >> it was ok with 1.7.5 and the cni worked fine, but i guess i need to >> try a more recent stable build. >> my suspicion is that this issue lies deep and i won't be able to solve >> it easily. >> >> i really need to be able to run the upstream cluster, though. >> so that my patches are not irrelevant compared to the latest master. > > Sure, but to rule out options, can help. That is what I was trying to say (and > the more we can rule out easily is the best, as email for this is not the best > tool :)) >
ok, i will see if someone posts an update in the github issue thread and try building the previous stable release. >> > And just in case, have you checked the guide and links on the readme? >> > https://github.com/kubernetes/kubernetes/blob/master/README.md#to-start-developing-kubernetes >> > >> >> things like the dev. guide is a lot of information to process. >> https://github.com/kubernetes/community/blob/master/contributors/devel/development.md >> i need to take a careful read at that. > > It seems longer than it is if you read it and follow the steps :) > >> > I used the guides linked there when writing patches. That goes in more >> > detail, but basically compile and some scripts in "hack/" will help you do >> > the trick, probably (local cluster up, for example). >> > >> >> thanks, will have a look. >> >> > Don't hesitate to contact again! :-) >> > >> >> out of interest what contributions have you made? > > My github handle is @rata. I've contributed some proposals, simple patches to > kubernetes and the documentation > >> any tips and suggestions for starters? > > My first PR was a documentation fix. If you want to code, there are lot of > projects outside of core kubernetes (like kops, autoscaler, etc.) and of > course, > kubernetes. > > For core kubernetes, I'd look at issues with the for-new-contributors label. > For > example: https://github.com/kubernetes/kubernetes/labels/for-new-contributors > > >> also, what (preferably simpler) areas of kubernetes need work, in your >> opinion? > > I don't really know. Probably all =) > > Feel free to join slack and start participating in some SIG or something too! > :) > thanks a lot, that's valuable info! lubomir -- -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
