Why is TiCDC not bound to PV volumes in a k8s environment?

This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: 在k8s环境下,为什么ticdc没有绑定pv卷

| username: TiDB_Paper

[TiDB Usage Environment] Production Environment
[TiDB Version] v6.1.0
[Encountered Problem: Phenomenon and Impact] According to the original documentation, persistent storage is required, but after deployment, it was found that PV was not bound.
[Attachments: Screenshots/Logs/Monitoring]

| username: yiduoyunQ | Original post link

By default, only PD & TiKV have mounted disks. For mounting disks to TiCDC, refer to the TiCDC section in the documentation at 配置 TiDB 集群 | PingCAP 文档中心.

The above is automatically mounted by the operator calling CSI. If you wish to mount your own maintained disks, you can use tidb-operator/pkg/apis/pingcap/v1alpha1/types.go at v1.4.4 · pingcap/tidb-operator · GitHub.

| username: TiDB_Paper | Original post link

Thank you for the clarification, because ticdc is a component that was added later :upside_down_face:

| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.