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
The Pod should be showing as having started successfully:
474
+
-->
475
+
此 Pod 应该显示为已成功启动:
476
+
477
+
```
478
+
NAME READY STATUS RESTARTS AGE
479
+
default-pod 1/1 Running 0 20s
480
+
```
481
+
482
+
<!--
483
+
Finally, now that you saw that work OK, clean up:
484
+
-->
485
+
最后,你看到一切正常之后,请清理:
486
+
487
+
```shell
488
+
kubectl delete pod default-pod --wait --now
489
+
```
490
+
427
491
<!--
428
492
## Create a Pod with a seccomp profile for syscall auditing
429
493
@@ -772,69 +836,6 @@ kubectl delete service fine-pod --wait
772
836
kubectl delete pod fine-pod --wait --now
773
837
```
774
838
775
-
<!--
776
-
## Create Pod that uses the container runtime default seccomp profile
777
-
778
-
Most container runtimes provide a sane set of default syscalls that are allowed
779
-
or not. You can adopt these defaults for your workload by setting the seccomp
780
-
type in the security context of a pod or container to `RuntimeDefault`.
781
-
-->
782
-
## 创建使用容器运行时默认 seccomp 配置文件的 Pod {#create-pod-that-uses-the-container-runtime-default-seccomp-profile}
783
-
784
-
大多数容器运行时都提供了一组合理的默认系统调用,以及是否允许执行这些系统调用。
785
-
你可以通过将 Pod 或容器的安全上下文中的 seccomp 类型设置为 `RuntimeDefault`
786
-
来为你的工作负载采用这些默认值。
787
-
788
-
{{< note >}}
789
-
<!--
790
-
If you have the `SeccompDefault` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) enabled, then Pods use the `RuntimeDefault` seccomp profile whenever
791
-
no other seccomp profile is specified. Otherwise, the default is `Unconfined`.
0 commit comments