Some users found other creative places to carry information, such as scheduling preferences, in which arbitrary key/value strings could be stored. Arbitrary protobuf extensions were eventually supported.
Show this thread
Kubernetes Borg/Omega history topic 3: Annotations. Borg's Job type had a single notes field. Like the DNS TXT record, that proved insufficient. For example, layers of client libraries and tools wanted to attach additional information.
-
-
-
That's a common theme in many parts of the Kubernetes API: consider when multiple values or key/value pairs may be needed rather than just singleton values. I proposed annotations inhttp://issues.k8s.io/1201
Show this thread -
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 )
Show this thread -
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.
Show this thread
End of conversation
New conversation -
-
-
Hello, you can read it here: Thread by
@bgrant0607: "Kubernetes Borg/Omega history topic 3: Annotations. Borg's Job type had a single notes field. Like the DNS TXT record, t […]" https://threadreaderapp.com/thread/1106651847962443776.html … Have a good day.
End of conversation
New conversation -
-
This Tweet is unavailable.
-
Hello Julian, the whole thread from
@bgrant0607 is compiled now. Read it here:https://threader.app/thread/1106651847962443776 …
End of conversation
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.