Commit 82d64895 authored by Daniel Smith's avatar Daniel Smith

Manually fixing docs, since gendocs messes up the links.

parent b225c1d4
...@@ -60,7 +60,7 @@ Instead of a single Timestamp, each event object [contains](http://releases.k8s. ...@@ -60,7 +60,7 @@ Instead of a single Timestamp, each event object [contains](http://releases.k8s.
Each binary that generates events: Each binary that generates events:
* Maintains a historical record of previously generated events: * Maintains a historical record of previously generated events:
* Implemented with ["Least Recently Used Cache"](https://github.com/golang/groupcache/blob/master/lru/lru.go) in [`pkg/client/unversioned/record/events_cache.go`](../../pkg/client/unversioned/record/events_cache.go). * Implemented with ["Least Recently Used Cache"](https://github.com/golang/groupcache/blob/master/lru/lru.go) in [`pkg/client/record/events_cache.go`](../../pkg/client/record/events_cache.go).
* The key in the cache is generated from the event object minus timestamps/count/transient fields, specifically the following events fields are used to construct a unique key for an event: * The key in the cache is generated from the event object minus timestamps/count/transient fields, specifically the following events fields are used to construct a unique key for an event:
* `event.Source.Component` * `event.Source.Component`
* `event.Source.Host` * `event.Source.Host`
......
...@@ -166,7 +166,7 @@ the same time, we can introduce an additional etcd event type: ...@@ -166,7 +166,7 @@ the same time, we can introduce an additional etcd event type:
Thus, we need to create the EtcdResync event, extend watch.Interface and Thus, we need to create the EtcdResync event, extend watch.Interface and
its implementations to support it and handle those events appropriately its implementations to support it and handle those events appropriately
in places like in places like
[Reflector](../../pkg/client/unversioned/cache/reflector.go) [Reflector](../../pkg/client/cache/reflector.go)
However, this might turn out to be unnecessary optimization if apiserver However, this might turn out to be unnecessary optimization if apiserver
will always keep up (which is possible in the new design). We will work will always keep up (which is possible in the new design). We will work
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment