-
Notifications
You must be signed in to change notification settings - Fork 996
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
runtime-rs: Support event mechanism #7881
Projects
Comments
justxuewei
changed the title
runtime-rs: Support event machanism
runtime-rs: Support event mechanism
Jan 6, 2024
justxuewei
added a commit
to justxuewei/kata-containers
that referenced
this issue
Jan 6, 2024
It is a little bit heavy for the runtime-rs to forwards events via containerd CLI, contrast to the ttrpc way. Plus, for runtimes that haven't this mechanism, e.g. CRI-O, we can't get those events anywhere. This patch introduces two types of forwarders: - `ContainerdForwarder`: Acquire ttrpc address from environment variables and forward events via ttrpc connection. - `LogForwarder`: Write event info into logs. Fixes: kata-containers#7881 Signed-off-by: Xuewei Niu <niuxuewei.nxw@antgroup.com>
justxuewei
added a commit
to justxuewei/kata-containers
that referenced
this issue
Jan 6, 2024
It is a little bit heavy for the runtime-rs to forwards events via containerd CLI, contrast to the ttrpc way. Plus, for runtimes that haven't this mechanism, e.g. CRI-O, we can't get those events anywhere. This patch introduces two types of forwarders: - `ContainerdForwarder`: Acquire ttrpc address from environment variables and forward events via ttrpc connection. - `LogForwarder`: Write event info into logs. Fixes: kata-containers#7881 Signed-off-by: Xuewei Niu <niuxuewei.nxw@antgroup.com>
justxuewei
added a commit
to justxuewei/kata-containers
that referenced
this issue
Jan 6, 2024
It is a little bit heavy for the runtime-rs to forwards events via containerd CLI, contrast to the ttrpc way. Plus, for runtimes that haven't this mechanism, e.g. CRI-O, we can't get those events anywhere. This patch introduces two types of forwarders: - `ContainerdForwarder`: Acquire ttrpc address from environment variables and forward events via ttrpc connection. - `LogForwarder`: Write event info into logs. Fixes: kata-containers#7881 Signed-off-by: Xuewei Niu <niuxuewei.nxw@antgroup.com>
justxuewei
added a commit
to justxuewei/kata-containers
that referenced
this issue
Jan 6, 2024
It is a little bit heavy for the runtime-rs to forwards events via containerd CLI, contrast to the ttrpc way. Plus, for runtimes that haven't this mechanism, e.g. CRI-O, we can't get those events anywhere. This patch introduces two types of forwarders: - `ContainerdForwarder`: Acquire ttrpc address from environment variables and forward events via ttrpc connection. - `LogForwarder`: Write event info into logs. Fixes: kata-containers#7881 Signed-off-by: Xuewei Niu <niuxuewei.nxw@antgroup.com>
justxuewei
added a commit
to justxuewei/kata-containers
that referenced
this issue
Jan 6, 2024
It is a little bit heavy for the runtime-rs to forwards events via containerd CLI, contrast to the ttrpc way. Plus, for runtimes that haven't this mechanism, e.g. CRI-O, we can't get those events anywhere. This patch introduces two types of forwarders: - `ContainerdForwarder`: Acquire ttrpc address from environment variables and forward events via ttrpc connection. - `LogForwarder`: Write event info into logs. Fixes: kata-containers#7881 Signed-off-by: Xuewei Niu <niuxuewei.nxw@antgroup.com>
justxuewei
added a commit
to justxuewei/kata-containers
that referenced
this issue
Jan 10, 2024
It is a little bit heavy for the runtime-rs to forwards events via containerd CLI, contrast to the ttrpc way. Plus, for runtimes that haven't this mechanism, e.g. CRI-O, we can't get those events anywhere. This patch introduces two types of forwarders: - `ContainerdForwarder`: Acquire ttrpc address from environment variables and forward events via ttrpc connection. - `LogForwarder`: Write event info into logs. Fixes: kata-containers#7881 Signed-off-by: Xuewei Niu <niuxuewei.nxw@antgroup.com>
justxuewei
added a commit
to justxuewei/kata-containers
that referenced
this issue
Jan 11, 2024
It is a little bit heavy for the runtime-rs to forwards events via containerd CLI, contrast to the ttrpc way. Plus, for runtimes that haven't this mechanism, e.g. CRI-O, we can't get those events anywhere. This patch introduces two types of forwarders: - `ContainerdForwarder`: Acquire ttrpc address from environment variables and forward events via ttrpc connection. - `LogForwarder`: Write event info into logs. Fixes: kata-containers#7881 Signed-off-by: Xuewei Niu <niuxuewei.nxw@antgroup.com>
justxuewei
added a commit
to justxuewei/kata-containers
that referenced
this issue
Jan 11, 2024
It is a little bit heavy for the runtime-rs to forwards events via containerd CLI, contrast to the ttrpc way. Plus, for runtimes that haven't this mechanism, e.g. CRI-O, we can't get those events anywhere. This patch introduces two types of forwarders: - `ContainerdForwarder`: Acquire ttrpc address from environment variables and forward events via ttrpc connection. - `LogForwarder`: Write event info into logs. Fixes: kata-containers#7881 Signed-off-by: Xuewei Niu <niuxuewei.nxw@antgroup.com>
justxuewei
added a commit
to justxuewei/kata-containers
that referenced
this issue
Jan 11, 2024
It is a little bit heavy for the runtime-rs to forwards events via containerd CLI, contrast to the ttrpc way. Plus, for runtimes that haven't this mechanism, e.g. CRI-O, we can't get those events anywhere. This patch introduces two types of forwarders: - `ContainerdForwarder`: Acquire ttrpc address from environment variables and forward events via ttrpc connection. - `LogForwarder`: Write event info into logs. Fixes: kata-containers#7881 Signed-off-by: Xuewei Niu <niuxuewei.nxw@antgroup.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The Runtime-rs doesn't support event machanism so far. The events include OOM event, task exit event, etc. See:
kata-containers/src/runtime/pkg/containerd-shim-v2/service.go
Lines 294 to 320 in 6cd5d83
The text was updated successfully, but these errors were encountered: