fix: correct service role in helm chart configuration examples (#1881)

Signed-off-by: WenyXu <[email protected]>

Author: WenyXu

docs/user-guide/deployments-administration/deploy-on-kubernetes/common-helm-chart-configurations.md

@@ -165,7 +165,7 @@ frontend:
 For different Role services, youcan inject custom TOML configuration files through the `${role}.configData` field, as shown below:
 
 ```yaml
-frontend:
+datanode:
   configData: |
     [[region_engine]]
     [region_engine.mito]

i18n/zh/docusaurus-plugin-content-docs/current/user-guide/deployments-administration/deploy-on-kubernetes/common-helm-chart-configurations.md

@@ -165,7 +165,7 @@ frontend:
 对于不同 Role 的服务，你可以通过 `${role}.configData` 字段注入自定义的 TOML 配置文件，如下所示：
 
 ```yaml
-frontend:
+datanode:
   configData: |
     [[region_engine]]
     [region_engine.mito]

i18n/zh/docusaurus-plugin-content-docs/version-0.11/user-guide/deployments/deploy-on-kubernetes/common-helm-chart-configurations.md

@@ -165,7 +165,7 @@ frontend:
 对于不同 Role 的服务，你可以通过 `${role}.configData` 字段注入自定义的 TOML 配置文件，如下所示：
 
 ```yaml
-frontend:
+datanode:
   configData: |
     [[region_engine]]
     [region_engine.mito]

i18n/zh/docusaurus-plugin-content-docs/version-0.12/user-guide/deployments/deploy-on-kubernetes/common-helm-chart-configurations.md

@@ -165,7 +165,7 @@ frontend:
 对于不同 Role 的服务，你可以通过 `${role}.configData` 字段注入自定义的 TOML 配置文件，如下所示：
 
 ```yaml
-frontend:
+datanode:
   configData: |
     [[region_engine]]
     [region_engine.mito]

i18n/zh/docusaurus-plugin-content-docs/version-0.13/user-guide/deployments/deploy-on-kubernetes/common-helm-chart-configurations.md

@@ -165,7 +165,7 @@ frontend:
 对于不同 Role 的服务，你可以通过 `${role}.configData` 字段注入自定义的 TOML 配置文件，如下所示：
 
 ```yaml
-frontend:
+datanode:
   configData: |
     [[region_engine]]
     [region_engine.mito]

i18n/zh/docusaurus-plugin-content-docs/version-0.14/user-guide/deployments/deploy-on-kubernetes/common-helm-chart-configurations.md

@@ -165,7 +165,7 @@ frontend:
 对于不同 Role 的服务，你可以通过 `${role}.configData` 字段注入自定义的 TOML 配置文件，如下所示：
 
 ```yaml
-frontend:
+datanode:
   configData: |
     [[region_engine]]
     [region_engine.mito]

versioned_docs/version-0.11/user-guide/deployments/deploy-on-kubernetes/common-helm-chart-configurations.md

@@ -165,7 +165,7 @@ frontend:
 For different Role services, youcan inject custom TOML configuration files through the `${role}.configData` field, as shown below:
 
 ```yaml
-frontend:
+datanode:
   configData: |
     [[region_engine]]
     [region_engine.mito]

versioned_docs/version-0.12/user-guide/deployments/deploy-on-kubernetes/common-helm-chart-configurations.md

@@ -165,7 +165,7 @@ frontend:
 For different Role services, youcan inject custom TOML configuration files through the `${role}.configData` field, as shown below:
 
 ```yaml
-frontend:
+datanode:
   configData: |
     [[region_engine]]
     [region_engine.mito]

versioned_docs/version-0.13/user-guide/deployments/deploy-on-kubernetes/common-helm-chart-configurations.md

@@ -165,7 +165,7 @@ frontend:
 For different Role services, youcan inject custom TOML configuration files through the `${role}.configData` field, as shown below:
 
 ```yaml
-frontend:
+datanode:
   configData: |
     [[region_engine]]
     [region_engine.mito]

versioned_docs/version-0.14/user-guide/deployments/deploy-on-kubernetes/common-helm-chart-configurations.md

@@ -165,7 +165,7 @@ frontend:
 For different Role services, youcan inject custom TOML configuration files through the `${role}.configData` field, as shown below:
 
 ```yaml
-frontend:
+datanode:
   configData: |
     [[region_engine]]
     [region_engine.mito]