diff options
| author | Kubernetes Prow Robot <k8s-ci-robot@users.noreply.github.com> | 2019-11-14 23:27:42 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-11-14 23:27:42 -0800 |
| commit | 22274220fac7d132efcc8613a81894aee7e2c85b (patch) | |
| tree | 8bfca9ea0a546f862634aba2227d730b7b4238a9 | |
| parent | 3c9d2ad92d7a649d026d89395007bba3d10fb84f (diff) | |
| parent | b878cb996940619d3d0f4224d189d1617d0ed761 (diff) | |
Merge pull request #4239 from tanalam2411/patch-1
Broken link of Docker's event stream
| -rw-r--r-- | contributors/design-proposals/node/pod-lifecycle-event-generator.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/design-proposals/node/pod-lifecycle-event-generator.md b/contributors/design-proposals/node/pod-lifecycle-event-generator.md index 00f4e10c..42ca80c4 100644 --- a/contributors/design-proposals/node/pod-lifecycle-event-generator.md +++ b/contributors/design-proposals/node/pod-lifecycle-event-generator.md @@ -116,7 +116,7 @@ The upstream container events can come from: (1). *Event stream provided by each container runtime* Docker's API exposes an [event -stream](https://docs.docker.com/reference/api/docker_remote_api_v1.17/#monitor-docker-s-events). +stream](https://docs.docker.com/engine/api/v1.40/#operation/SystemEvents). Nonetheless, rkt does not support this yet, but they will eventually support it (see [coreos/rkt#1193](https://github.com/coreos/rkt/issues/1193)). |