Re: Proposal: Metadata for API resources
toggle quoted message Show quoted text
Thanks for taking the time to read through it.
There was no specific consideration around API similarity in general. It just seemed to make sense for this specific use case. Kube has a nice partitioning of different types of data -- labels vs annotations -- that matched up well with what we have heard regarding what folks would use metadata for. It also made sense to consider for these specific APIs since a large reason for metadata is third party system integration. I've spoken with several folks that are building systems that manipulate objects in both systems, so having low cognitive overhead for cross-platform integration felt like a good path to pursue.
On Fri, Jun 8, 2018 at 2:15 AM David McClure <dmcclure@...> wrote: