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
Explicitly representing the PodTemplate as a separate object, as proposed in http://issues.k8s.io/170 , may also have been useful for these third-party controllers, but in practice the lack of support for that hasn't been a huge obstacle. (Well, the API exists, but is unused.)
I proposed the idea of modeling workload controllers as loosely coupled sets of instances grouped using a label selector in June 2013, based on an 11-page analysis of Borg Job use cases, around the same timeframe as the original labels proposal.
That partly inspired http://replicapool.googleapis.com also, though the lack of labels in GCE at the time made implementing the full model infeasible.
Aside on "template": a "template" is a pattern used to make copies of the same shape. I think the Kubernetes "Pod template" usage is true to that colloquial definition, but typical CS usage implies parameterization and/or macro expansion, so maybe "prototype" would be better
The idea of explicitly modeling state so that it can be externally controlled and observed is a key principle of Cloud Native. I originally included it in a longer form of the definition I wrote for CNCF: https://github.com/cncf/toc/blob/master/DEFINITION.md …
The principle can also be applied to workflow systems and configuration management (e.g., see https://github.com/kubernetes/community/blob/master/contributors/design-proposals/architecture/declarative-application-management.md …). Embodying these as code is powerful, but with great power comes great responsibility, since it obstructs external tooling and automation
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
