Merge pull request #95925 from deads2k/doc-events

Event: Document TTL and best-effort-ness
This commit is contained in:
Kubernetes Prow Robot
2020-10-29 17:40:22 -07:00
committed by GitHub
11 changed files with 44 additions and 9 deletions

View File

@@ -6574,7 +6574,7 @@
"type": "object"
},
"io.k8s.api.core.v1.Event": {
"description": "Event is a report of an event somewhere in the cluster.",
"description": "Event is a report of an event somewhere in the cluster. Events have a limited retention time and triggers and messages may evolve with time. Event consumers should not rely on the timing of an event with a given Reason reflecting a consistent underlying trigger, or the continued existence of events with that Reason. Events should be treated as informative, best-effort, supplemental data.",
"properties": {
"action": {
"description": "What action was taken/failed regarding to the Regarding object.",
@@ -11028,7 +11028,7 @@
]
},
"io.k8s.api.events.v1.Event": {
"description": "Event is a report of an event somewhere in the cluster. It generally denotes some state change in the system.",
"description": "Event is a report of an event somewhere in the cluster. It generally denotes some state change in the system. Events have a limited retention time and triggers and messages may evolve with time. Event consumers should not rely on the timing of an event with a given Reason reflecting a consistent underlying trigger, or the continued existence of events with that Reason. Events should be treated as informative, best-effort, supplemental data.",
"properties": {
"action": {
"description": "action is what action was taken/failed regarding to the regarding object. It is machine-readable. This field cannot be empty for new Events and it can have at most 128 characters.",
@@ -11167,7 +11167,7 @@
"type": "object"
},
"io.k8s.api.events.v1beta1.Event": {
"description": "Event is a report of an event somewhere in the cluster. It generally denotes some state change in the system.",
"description": "Event is a report of an event somewhere in the cluster. It generally denotes some state change in the system. Events have a limited retention time and triggers and messages may evolve with time. Event consumers should not rely on the timing of an event with a given Reason reflecting a consistent underlying trigger, or the continued existence of events with that Reason. Events should be treated as informative, best-effort, supplemental data.",
"properties": {
"action": {
"description": "action is what action was taken/failed regarding to the regarding object. It is machine-readable. This field can have at most 128 characters.",