Merge pull request #51189 from asa3311/sync-zh-184

[zh] sync system-traces finalizers deploy-intro
pull/51102/head
Kubernetes Prow Robot 2025-06-06 17:14:39 -07:00 committed by GitHub
commit e2616e18c8
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 19 additions and 7 deletions

View File

@ -74,13 +74,14 @@ receivers:
grpc:
exporters:
# Replace this exporter with the exporter for your backend
logging:
logLevel: debug
exporters:
debug:
verbosity: detailed
service:
pipelines:
traces:
receivers: [otlp]
exporters: [logging]
exporters: [debug]
```
-->
```yaml
@ -90,13 +91,14 @@ receivers:
grpc:
exporters:
# 用适合你后端环境的导出器替换此处的导出器
logging:
logLevel: debug
exporters:
debug:
verbosity: detailed
service:
pipelines:
traces:
receivers: [otlp]
exporters: [logging]
exporters: [debug]
```
<!--

View File

@ -100,6 +100,16 @@ object once it is set.
* 删除请求已被发出之后,你无法复活该对象。唯一的方法是删除它并创建一个新的相似对象。
{{</note>}}
{{<note>}}
<!--
Custom finalizer names **must** be publicly qualified finalizer names, such as `example.com/finalizer-name`.
Kubernetes enforces this format; the API server rejects writes to objects where the change does not use qualified finalizer names for any custom finalizer.
-->
自定义的 finalizer 名称**必须**是具有公共限定前缀的 finalizer 名称,
例如 `example.com/finalizer-name`。Kubernetes 强制要求使用这种格式;
如果对象中的更改未使用合规的限定格式API 服务器将拒绝写入包含自定义 finalizer 的对象。
{{</note>}}
<!--
## Owner references, labels, and finalizers {#owners-labels-finalizers}

View File

@ -123,7 +123,7 @@ that first by following the instructions from the [Hello Minikube tutorial](/doc
<!--
You will need to have installed kubectl as well. If you need to install it, visit
[install tools](/docs/tasks/tools/#kubectl) install tools.
[install tools](/docs/tasks/tools/#kubectl).
Now that you know what Deployments are, let's deploy our first app!
-->