You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Annotations provided a place to store the configured state for apply, as discussed in http://issues.k8s.io/1178 and http://issues.k8s.io/1702 , and subsumed Openshift's description field, in the v1beta3 API overhaul (http://prs.k8s.io/1225 )
Some believed that having 2 kinds of key/value string metadata, labels and annotations, would be confusing, so I put some effort into clarifying the distinction in documentation early on, such as in http://prs.k8s.io/1817 . I think unifying them would have reduced usability.
I think that separation of concerns between how to query/select resources and how to convey information on resources to enable specific behaviors was a really good call
Would it be quite correct to summarize, saying labels ~= indexes whereas annotations ~= metadata? The former being used fir queries, the latter for additional info
Annotations are the single most valuable tool in kubernetes for layering. They provide easy stateful glue and inherit all our consistency guarantees. I find them easier than crds for many quick and fast integrations. Idea: something like CRD for annotations with tooling integ
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
