You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
log.G(ctx).Warning("`untrusted_workload_runtime` is deprecated, please use `untrusted` runtime in `runtimes` instead")
123
+
if_, ok:=c.ContainerdConfig.Runtimes[criconfig.RuntimeUntrusted]; ok {
124
+
returnerrors.Errorf("conflicting definitions: configuration includes both `untrusted_workload_runtime` and `runtimes[%q]`", criconfig.RuntimeUntrusted)
// Validation for deprecated default_runtime field.
130
+
ifc.ContainerdConfig.DefaultRuntime.Type!="" {
131
+
log.G(ctx).Warning("`default_runtime` is deprecated, please use `default_runtime_name` to reference the default configuration you have defined in `runtimes`")
The recommended way to run untrusted workload is to use
174
+
[`RuntimeClass`](https://kubernetes.io/docs/concepts/containers/runtime-class/) api
175
+
introduced in Kubernetes 1.12 to select RuntimeHandlers configured to run
176
+
untrusted workload in `plugins.cri.containerd.runtimes`.
177
+
178
+
However, if you are using the legacy `io.kubernetes.cri.untrusted-workload`pod annotation
179
+
to request a pod be run using a runtime for untrusted workloads, the RuntimeHandler
180
+
`plugins.cri.containerd.runtimes.untrusted` must be defined first. When the annotation
181
+
`io.kubernetes.cri.untrusted-workload` is set to `true` the `untrusted` runtime will be
182
+
used. For example, see
183
+
[Create an untrusted pod using Kata Containers](https://github.com/kata-containers/documentation/blob/master/how-to/how-to-use-k8s-with-cri-containerd-and-kata.md#create-an-untrusted-pod-using-kata-containers).
184
+
185
+
## Deprecation
186
+
The config options of the CRI plugin follow the [Kubernetes deprecation
187
+
policy of "admin-facing CLI components"](https://kubernetes.io/docs/reference/using-api/deprecation-policy/#deprecating-a-flag-or-cli).
188
+
189
+
In summary, when a config option is announced to be deprecated:
190
+
* It is kept functional for 6 months or 1 release (whichever is longer);
0 commit comments