Add initial resources.md for discussion

The first draft of a Kubernetes resource model.
E-notation produces a float value.  For int fields, this imposes conversions and corner cases I don't think we need.  Can we drop E-notation?  Or do you think that level of input-friendliness is really important?  We do not go out of our way to be this friendly anywhere else.

http://play.golang.org/p/Xw2Y6xR8zT