You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by ur...@apache.org on 2022/07/01 12:01:36 UTC
[pulsar-site] branch main updated: Docs sync done from apache/pulsar(#46e33d1)
This is an automated email from the ASF dual-hosted git repository.
urfree pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/pulsar-site.git
The following commit(s) were added to refs/heads/main by this push:
new 93baff0cfff Docs sync done from apache/pulsar(#46e33d1)
93baff0cfff is described below
commit 93baff0cfff17a3061f95d2dacdb757fc06e1d8a
Author: Pulsar Site Updater <de...@pulsar.apache.org>
AuthorDate: Fri Jul 1 12:01:31 2022 +0000
Docs sync done from apache/pulsar(#46e33d1)
---
site2/website-next/docs/io-cli.md | 4 ++--
site2/website-next/docs/reference-metrics.md | 4 ++--
site2/website-next/versioned_docs/version-2.10.0/functions-runtime.md | 2 +-
site2/website-next/versioned_docs/version-2.10.0/io-cli.md | 4 ++--
site2/website-next/versioned_docs/version-2.10.0/reference-metrics.md | 4 ++--
.../versioned_docs/version-2.4.1/reference-connector-admin.md | 4 ++--
.../versioned_docs/version-2.4.2/reference-connector-admin.md | 4 ++--
site2/website-next/versioned_docs/version-2.5.0/io-cli.md | 4 ++--
site2/website-next/versioned_docs/version-2.5.1/io-cli.md | 4 ++--
site2/website-next/versioned_docs/version-2.5.2/io-cli.md | 4 ++--
site2/website-next/versioned_docs/version-2.6.0/io-cli.md | 4 ++--
site2/website-next/versioned_docs/version-2.6.0/reference-metrics.md | 2 +-
site2/website-next/versioned_docs/version-2.6.1/io-cli.md | 4 ++--
site2/website-next/versioned_docs/version-2.6.1/reference-metrics.md | 2 +-
site2/website-next/versioned_docs/version-2.6.2/io-cli.md | 4 ++--
site2/website-next/versioned_docs/version-2.6.2/reference-metrics.md | 2 +-
site2/website-next/versioned_docs/version-2.6.3/io-cli.md | 4 ++--
site2/website-next/versioned_docs/version-2.6.3/reference-metrics.md | 2 +-
site2/website-next/versioned_docs/version-2.6.4/io-cli.md | 4 ++--
site2/website-next/versioned_docs/version-2.6.4/reference-metrics.md | 2 +-
site2/website-next/versioned_docs/version-2.7.0/functions-runtime.md | 2 +-
site2/website-next/versioned_docs/version-2.7.0/io-cli.md | 4 ++--
site2/website-next/versioned_docs/version-2.7.0/reference-metrics.md | 2 +-
site2/website-next/versioned_docs/version-2.7.1/functions-runtime.md | 2 +-
site2/website-next/versioned_docs/version-2.7.1/io-cli.md | 4 ++--
site2/website-next/versioned_docs/version-2.7.1/reference-metrics.md | 2 +-
site2/website-next/versioned_docs/version-2.7.2/functions-runtime.md | 2 +-
site2/website-next/versioned_docs/version-2.7.2/io-cli.md | 4 ++--
site2/website-next/versioned_docs/version-2.7.2/reference-metrics.md | 2 +-
site2/website-next/versioned_docs/version-2.7.3/functions-runtime.md | 2 +-
site2/website-next/versioned_docs/version-2.7.3/io-cli.md | 4 ++--
site2/website-next/versioned_docs/version-2.7.3/reference-metrics.md | 2 +-
site2/website-next/versioned_docs/version-2.7.4/functions-runtime.md | 2 +-
site2/website-next/versioned_docs/version-2.7.4/io-cli.md | 4 ++--
site2/website-next/versioned_docs/version-2.7.4/reference-metrics.md | 2 +-
site2/website-next/versioned_docs/version-2.8.0/functions-runtime.md | 2 +-
site2/website-next/versioned_docs/version-2.8.0/io-cli.md | 4 ++--
site2/website-next/versioned_docs/version-2.8.0/reference-metrics.md | 4 ++--
site2/website-next/versioned_docs/version-2.8.1/functions-runtime.md | 2 +-
site2/website-next/versioned_docs/version-2.8.1/io-cli.md | 4 ++--
site2/website-next/versioned_docs/version-2.8.1/reference-metrics.md | 4 ++--
site2/website-next/versioned_docs/version-2.8.2/functions-runtime.md | 2 +-
site2/website-next/versioned_docs/version-2.8.2/io-cli.md | 4 ++--
site2/website-next/versioned_docs/version-2.8.2/reference-metrics.md | 4 ++--
site2/website-next/versioned_docs/version-2.8.3/functions-runtime.md | 2 +-
site2/website-next/versioned_docs/version-2.8.3/io-cli.md | 4 ++--
site2/website-next/versioned_docs/version-2.8.3/reference-metrics.md | 4 ++--
site2/website-next/versioned_docs/version-2.9.0/functions-runtime.md | 2 +-
site2/website-next/versioned_docs/version-2.9.0/io-cli.md | 4 ++--
site2/website-next/versioned_docs/version-2.9.0/reference-metrics.md | 2 +-
site2/website-next/versioned_docs/version-2.9.1/functions-runtime.md | 2 +-
site2/website-next/versioned_docs/version-2.9.1/io-cli.md | 4 ++--
site2/website-next/versioned_docs/version-2.9.1/reference-metrics.md | 2 +-
site2/website-next/versioned_docs/version-2.9.2/functions-runtime.md | 2 +-
site2/website-next/versioned_docs/version-2.9.2/io-cli.md | 4 ++--
site2/website-next/versioned_docs/version-2.9.2/reference-metrics.md | 2 +-
56 files changed, 86 insertions(+), 86 deletions(-)
diff --git a/site2/website-next/docs/io-cli.md b/site2/website-next/docs/io-cli.md
index afd11689022..409521221b6 100644
--- a/site2/website-next/docs/io-cli.md
+++ b/site2/website-next/docs/io-cli.md
@@ -176,7 +176,7 @@ $ pulsar-admin sources status options
|Flag|Description|
|---|---|
-|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The source's name.|
|`--namespace`|The source's namespace.|
|`--tenant`|The source's tenant.|
@@ -500,7 +500,7 @@ $ pulsar-admin sinks status options
|Flag|Description|
|---|---|
-|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The sink's name.|
|`--namespace`|The sink's namespace.|
|`--tenant`|The sink's tenant.|
diff --git a/site2/website-next/docs/reference-metrics.md b/site2/website-next/docs/reference-metrics.md
index ed4314aa52a..88fb2b11556 100644
--- a/site2/website-next/docs/reference-metrics.md
+++ b/site2/website-next/docs/reference-metrics.md
@@ -27,7 +27,7 @@ The following types of metrics are available:
The ZooKeeper metrics are exposed under "/metrics" at port `8000`. You can use a different port by configuring the `metricsProvider.httpPort` in conf/zookeeper.conf.
-ZooKeeper provides a New Metrics System since 3.6.0, more detailed metrics can refer [ZooKeeper Monitor Guide](https://zookeeper.apache.org/doc/r3.7.0/zookeeperMonitor.html).
+ZooKeeper provides a New Metrics System since 3.6.0. For more detailed metrics, refer to the [ZooKeeper Monitor Guide](https://zookeeper.apache.org/doc/r3.7.0/zookeeperMonitor.html).
## BookKeeper
@@ -610,7 +610,7 @@ Connector metrics contain **source** metrics and **sink** metrics.
All the proxy metrics are labelled with the following labels:
- *cluster*: `cluster=${pulsar_cluster}`. `${pulsar_cluster}` is the cluster name that you have configured in the `broker.conf` file.
-- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the kubernetes pod name.
+- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the Kubernetes pod name.
| Name | Type | Description |
|---|---|---|
diff --git a/site2/website-next/versioned_docs/version-2.10.0/functions-runtime.md b/site2/website-next/versioned_docs/version-2.10.0/functions-runtime.md
index eec4f6d4e6e..9a01dbf4da1 100644
--- a/site2/website-next/versioned_docs/version-2.10.0/functions-runtime.md
+++ b/site2/website-next/versioned_docs/version-2.10.0/functions-runtime.md
@@ -242,7 +242,7 @@ io.kubernetes.client.ApiException: Forbidden
### Integrate Kubernetes secrets
-In order to safely distribute secrets, Pulasr Functions can reference Kubernetes secrets. To enable this, set the `secretsProviderConfiguratorClassName` to `org.apache.pulsar.functions.secretsproviderconfigurator.KubernetesSecretsProviderConfigurator`.
+In order to safely distribute secrets, Pulsar Functions can reference Kubernetes secrets. To enable this, set the `secretsProviderConfiguratorClassName` to `org.apache.pulsar.functions.secretsproviderconfigurator.KubernetesSecretsProviderConfigurator`.
You can create a secret in the namespace where your functions are deployed. For example, you deploy functions to the `pulsar-func` Kubernetes namespace, and you have a secret named `database-creds` with a field name `password`, which you want to mount in the pod as an environment variable called `DATABASE_PASSWORD`. The following functions configuration enables you to reference that secret and mount the value as an environment variable in the pod.
diff --git a/site2/website-next/versioned_docs/version-2.10.0/io-cli.md b/site2/website-next/versioned_docs/version-2.10.0/io-cli.md
index 87974d03803..f79d301c30b 100644
--- a/site2/website-next/versioned_docs/version-2.10.0/io-cli.md
+++ b/site2/website-next/versioned_docs/version-2.10.0/io-cli.md
@@ -177,7 +177,7 @@ $ pulsar-admin sources status options
|Flag|Description|
|---|---|
-|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The source's name.|
|`--namespace`|The source's namespace.|
|`--tenant`|The source's tenant.|
@@ -501,7 +501,7 @@ $ pulsar-admin sinks status options
|Flag|Description|
|---|---|
-|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The sink's name.|
|`--namespace`|The sink's namespace.|
|`--tenant`|The sink's tenant.|
diff --git a/site2/website-next/versioned_docs/version-2.10.0/reference-metrics.md b/site2/website-next/versioned_docs/version-2.10.0/reference-metrics.md
index 75c3dc1bff9..c0c67c3bfd2 100644
--- a/site2/website-next/versioned_docs/version-2.10.0/reference-metrics.md
+++ b/site2/website-next/versioned_docs/version-2.10.0/reference-metrics.md
@@ -28,7 +28,7 @@ The following types of metrics are available:
The ZooKeeper metrics are exposed under "/metrics" at port `8000`. You can use a different port by configuring the `metricsProvider.httpPort` in conf/zookeeper.conf.
-ZooKeeper provides a New Metrics System since 3.6.0, more detailed metrics can refer [ZooKeeper Monitor Guide](https://zookeeper.apache.org/doc/r3.7.0/zookeeperMonitor.html).
+ZooKeeper provides a New Metrics System since 3.6.0. For more detailed metrics, refer to the [ZooKeeper Monitor Guide](https://zookeeper.apache.org/doc/r3.7.0/zookeeperMonitor.html).
## BookKeeper
@@ -562,7 +562,7 @@ Connector metrics contain **source** metrics and **sink** metrics.
All the proxy metrics are labelled with the following labels:
- *cluster*: `cluster=${pulsar_cluster}`. `${pulsar_cluster}` is the cluster name that you have configured in the `broker.conf` file.
-- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the kubernetes pod name.
+- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the Kubernetes pod name.
| Name | Type | Description |
|---|---|---|
diff --git a/site2/website-next/versioned_docs/version-2.4.1/reference-connector-admin.md b/site2/website-next/versioned_docs/version-2.4.1/reference-connector-admin.md
index 01d5ea453ca..dca47457fe9 100644
--- a/site2/website-next/versioned_docs/version-2.4.1/reference-connector-admin.md
+++ b/site2/website-next/versioned_docs/version-2.4.1/reference-connector-admin.md
@@ -172,7 +172,7 @@ $ pulsar-admin sources status options
|Flag|Description|
|---|---|
-|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The source's name.|
|`--namespace`|The source's namespace.|
|`--tenant`|The source's tenant.|
@@ -495,7 +495,7 @@ $ pulsar-admin sinks status options
|Flag|Description|
|---|---|
-|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The sink's name.|
|`--namespace`|The sink's namespace.|
|`--tenant`|The sink's tenant.|
diff --git a/site2/website-next/versioned_docs/version-2.4.2/reference-connector-admin.md b/site2/website-next/versioned_docs/version-2.4.2/reference-connector-admin.md
index 9d1bca15561..8e5d2c9df19 100644
--- a/site2/website-next/versioned_docs/version-2.4.2/reference-connector-admin.md
+++ b/site2/website-next/versioned_docs/version-2.4.2/reference-connector-admin.md
@@ -173,7 +173,7 @@ $ pulsar-admin sources status options
|Flag|Description|
|---|---|
-|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The source's name.|
|`--namespace`|The source's namespace.|
|`--tenant`|The source's tenant.|
@@ -496,7 +496,7 @@ $ pulsar-admin sinks status options
|Flag|Description|
|---|---|
-|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The sink's name.|
|`--namespace`|The sink's namespace.|
|`--tenant`|The sink's tenant.|
diff --git a/site2/website-next/versioned_docs/version-2.5.0/io-cli.md b/site2/website-next/versioned_docs/version-2.5.0/io-cli.md
index c0f66d62472..e4dfa548016 100644
--- a/site2/website-next/versioned_docs/version-2.5.0/io-cli.md
+++ b/site2/website-next/versioned_docs/version-2.5.0/io-cli.md
@@ -168,7 +168,7 @@ $ pulsar-admin sources status options
|Flag|Description|
|---|---|
-|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The source's name.|
|`--namespace`|The source's namespace.|
|`--tenant`|The source's tenant.|
@@ -491,7 +491,7 @@ $ pulsar-admin sinks status options
|Flag|Description|
|---|---|
-|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The sink's name.|
|`--namespace`|The sink's namespace.|
|`--tenant`|The sink's tenant.|
diff --git a/site2/website-next/versioned_docs/version-2.5.1/io-cli.md b/site2/website-next/versioned_docs/version-2.5.1/io-cli.md
index c0f66d62472..e4dfa548016 100644
--- a/site2/website-next/versioned_docs/version-2.5.1/io-cli.md
+++ b/site2/website-next/versioned_docs/version-2.5.1/io-cli.md
@@ -168,7 +168,7 @@ $ pulsar-admin sources status options
|Flag|Description|
|---|---|
-|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The source's name.|
|`--namespace`|The source's namespace.|
|`--tenant`|The source's tenant.|
@@ -491,7 +491,7 @@ $ pulsar-admin sinks status options
|Flag|Description|
|---|---|
-|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The sink's name.|
|`--namespace`|The sink's namespace.|
|`--tenant`|The sink's tenant.|
diff --git a/site2/website-next/versioned_docs/version-2.5.2/io-cli.md b/site2/website-next/versioned_docs/version-2.5.2/io-cli.md
index c0f66d62472..e4dfa548016 100644
--- a/site2/website-next/versioned_docs/version-2.5.2/io-cli.md
+++ b/site2/website-next/versioned_docs/version-2.5.2/io-cli.md
@@ -168,7 +168,7 @@ $ pulsar-admin sources status options
|Flag|Description|
|---|---|
-|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The source's name.|
|`--namespace`|The source's namespace.|
|`--tenant`|The source's tenant.|
@@ -491,7 +491,7 @@ $ pulsar-admin sinks status options
|Flag|Description|
|---|---|
-|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The sink's name.|
|`--namespace`|The sink's namespace.|
|`--tenant`|The sink's tenant.|
diff --git a/site2/website-next/versioned_docs/version-2.6.0/io-cli.md b/site2/website-next/versioned_docs/version-2.6.0/io-cli.md
index 32ec16524de..15fe73ff2a3 100644
--- a/site2/website-next/versioned_docs/version-2.6.0/io-cli.md
+++ b/site2/website-next/versioned_docs/version-2.6.0/io-cli.md
@@ -168,7 +168,7 @@ $ pulsar-admin sources status options
|Flag|Description|
|---|---|
-|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The source's name.|
|`--namespace`|The source's namespace.|
|`--tenant`|The source's tenant.|
@@ -491,7 +491,7 @@ $ pulsar-admin sinks status options
|Flag|Description|
|---|---|
-|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The sink's name.|
|`--namespace`|The sink's namespace.|
|`--tenant`|The sink's tenant.|
diff --git a/site2/website-next/versioned_docs/version-2.6.0/reference-metrics.md b/site2/website-next/versioned_docs/version-2.6.0/reference-metrics.md
index 238a1b5b89a..8921123c136 100644
--- a/site2/website-next/versioned_docs/version-2.6.0/reference-metrics.md
+++ b/site2/website-next/versioned_docs/version-2.6.0/reference-metrics.md
@@ -397,7 +397,7 @@ All the Pulsar Functions metrics are labelled with the following labels:
All the proxy metrics are labelled with the following labels:
- *cluster*: `cluster=${pulsar_cluster}`. `${pulsar_cluster}` is the cluster name that you configured in `broker.conf`.
-- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the kubernetes pod name.
+- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the Kubernetes pod name.
| Name | Type | Description |
|---|---|---|
diff --git a/site2/website-next/versioned_docs/version-2.6.1/io-cli.md b/site2/website-next/versioned_docs/version-2.6.1/io-cli.md
index d29df8c4eae..6637f20a345 100644
--- a/site2/website-next/versioned_docs/version-2.6.1/io-cli.md
+++ b/site2/website-next/versioned_docs/version-2.6.1/io-cli.md
@@ -168,7 +168,7 @@ $ pulsar-admin sources status options
|Flag|Description|
|---|---|
-|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The source's name.|
|`--namespace`|The source's namespace.|
|`--tenant`|The source's tenant.|
@@ -491,7 +491,7 @@ $ pulsar-admin sinks status options
|Flag|Description|
|---|---|
-|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The sink's name.|
|`--namespace`|The sink's namespace.|
|`--tenant`|The sink's tenant.|
diff --git a/site2/website-next/versioned_docs/version-2.6.1/reference-metrics.md b/site2/website-next/versioned_docs/version-2.6.1/reference-metrics.md
index 238a1b5b89a..8921123c136 100644
--- a/site2/website-next/versioned_docs/version-2.6.1/reference-metrics.md
+++ b/site2/website-next/versioned_docs/version-2.6.1/reference-metrics.md
@@ -397,7 +397,7 @@ All the Pulsar Functions metrics are labelled with the following labels:
All the proxy metrics are labelled with the following labels:
- *cluster*: `cluster=${pulsar_cluster}`. `${pulsar_cluster}` is the cluster name that you configured in `broker.conf`.
-- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the kubernetes pod name.
+- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the Kubernetes pod name.
| Name | Type | Description |
|---|---|---|
diff --git a/site2/website-next/versioned_docs/version-2.6.2/io-cli.md b/site2/website-next/versioned_docs/version-2.6.2/io-cli.md
index d29df8c4eae..6637f20a345 100644
--- a/site2/website-next/versioned_docs/version-2.6.2/io-cli.md
+++ b/site2/website-next/versioned_docs/version-2.6.2/io-cli.md
@@ -168,7 +168,7 @@ $ pulsar-admin sources status options
|Flag|Description|
|---|---|
-|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The source's name.|
|`--namespace`|The source's namespace.|
|`--tenant`|The source's tenant.|
@@ -491,7 +491,7 @@ $ pulsar-admin sinks status options
|Flag|Description|
|---|---|
-|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The sink's name.|
|`--namespace`|The sink's namespace.|
|`--tenant`|The sink's tenant.|
diff --git a/site2/website-next/versioned_docs/version-2.6.2/reference-metrics.md b/site2/website-next/versioned_docs/version-2.6.2/reference-metrics.md
index 238a1b5b89a..8921123c136 100644
--- a/site2/website-next/versioned_docs/version-2.6.2/reference-metrics.md
+++ b/site2/website-next/versioned_docs/version-2.6.2/reference-metrics.md
@@ -397,7 +397,7 @@ All the Pulsar Functions metrics are labelled with the following labels:
All the proxy metrics are labelled with the following labels:
- *cluster*: `cluster=${pulsar_cluster}`. `${pulsar_cluster}` is the cluster name that you configured in `broker.conf`.
-- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the kubernetes pod name.
+- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the Kubernetes pod name.
| Name | Type | Description |
|---|---|---|
diff --git a/site2/website-next/versioned_docs/version-2.6.3/io-cli.md b/site2/website-next/versioned_docs/version-2.6.3/io-cli.md
index d29df8c4eae..6637f20a345 100644
--- a/site2/website-next/versioned_docs/version-2.6.3/io-cli.md
+++ b/site2/website-next/versioned_docs/version-2.6.3/io-cli.md
@@ -168,7 +168,7 @@ $ pulsar-admin sources status options
|Flag|Description|
|---|---|
-|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The source's name.|
|`--namespace`|The source's namespace.|
|`--tenant`|The source's tenant.|
@@ -491,7 +491,7 @@ $ pulsar-admin sinks status options
|Flag|Description|
|---|---|
-|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The sink's name.|
|`--namespace`|The sink's namespace.|
|`--tenant`|The sink's tenant.|
diff --git a/site2/website-next/versioned_docs/version-2.6.3/reference-metrics.md b/site2/website-next/versioned_docs/version-2.6.3/reference-metrics.md
index 238a1b5b89a..8921123c136 100644
--- a/site2/website-next/versioned_docs/version-2.6.3/reference-metrics.md
+++ b/site2/website-next/versioned_docs/version-2.6.3/reference-metrics.md
@@ -397,7 +397,7 @@ All the Pulsar Functions metrics are labelled with the following labels:
All the proxy metrics are labelled with the following labels:
- *cluster*: `cluster=${pulsar_cluster}`. `${pulsar_cluster}` is the cluster name that you configured in `broker.conf`.
-- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the kubernetes pod name.
+- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the Kubernetes pod name.
| Name | Type | Description |
|---|---|---|
diff --git a/site2/website-next/versioned_docs/version-2.6.4/io-cli.md b/site2/website-next/versioned_docs/version-2.6.4/io-cli.md
index d29df8c4eae..6637f20a345 100644
--- a/site2/website-next/versioned_docs/version-2.6.4/io-cli.md
+++ b/site2/website-next/versioned_docs/version-2.6.4/io-cli.md
@@ -168,7 +168,7 @@ $ pulsar-admin sources status options
|Flag|Description|
|---|---|
-|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The source's name.|
|`--namespace`|The source's namespace.|
|`--tenant`|The source's tenant.|
@@ -491,7 +491,7 @@ $ pulsar-admin sinks status options
|Flag|Description|
|---|---|
-|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The sink's name.|
|`--namespace`|The sink's namespace.|
|`--tenant`|The sink's tenant.|
diff --git a/site2/website-next/versioned_docs/version-2.6.4/reference-metrics.md b/site2/website-next/versioned_docs/version-2.6.4/reference-metrics.md
index f33a969f53d..0e47ef05e6f 100644
--- a/site2/website-next/versioned_docs/version-2.6.4/reference-metrics.md
+++ b/site2/website-next/versioned_docs/version-2.6.4/reference-metrics.md
@@ -397,7 +397,7 @@ All the Pulsar Functions metrics are labelled with the following labels:
All the proxy metrics are labelled with the following labels:
- *cluster*: `cluster=${pulsar_cluster}`. `${pulsar_cluster}` is the cluster name that you configured in `broker.conf`.
-- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the kubernetes pod name.
+- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the Kubernetes pod name.
| Name | Type | Description |
|---|---|---|
diff --git a/site2/website-next/versioned_docs/version-2.7.0/functions-runtime.md b/site2/website-next/versioned_docs/version-2.7.0/functions-runtime.md
index 1806028f003..6746f3336b7 100644
--- a/site2/website-next/versioned_docs/version-2.7.0/functions-runtime.md
+++ b/site2/website-next/versioned_docs/version-2.7.0/functions-runtime.md
@@ -198,7 +198,7 @@ io.kubernetes.client.ApiException: Forbidden
### Integrate Kubernetes secrets
-In order to safely distribute secrets, Pulasr Functions can reference Kubernetes secrets. To enable this, set the `secretsProviderConfiguratorClassName` to `org.apache.pulsar.functions.secretsproviderconfigurator.KubernetesSecretsProviderConfigurator`.
+In order to safely distribute secrets, Pulsar Functions can reference Kubernetes secrets. To enable this, set the `secretsProviderConfiguratorClassName` to `org.apache.pulsar.functions.secretsproviderconfigurator.KubernetesSecretsProviderConfigurator`.
You can create a secret in the namespace where your functions are deployed. For example, you deploy functions to the `pulsar-func` Kubernetes namespace, and you have a secret named `database-creds` with a field name `password`, which you want to mount in the pod as an environment variable called `DATABASE_PASSWORD`. The following functions configuration enables you to reference that secret and mount the value as an environment variable in the pod.
diff --git a/site2/website-next/versioned_docs/version-2.7.0/io-cli.md b/site2/website-next/versioned_docs/version-2.7.0/io-cli.md
index 1763839c234..3d54bb61875 100644
--- a/site2/website-next/versioned_docs/version-2.7.0/io-cli.md
+++ b/site2/website-next/versioned_docs/version-2.7.0/io-cli.md
@@ -169,7 +169,7 @@ $ pulsar-admin sources status options
|Flag|Description|
|---|---|
-|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The source's name.|
|`--namespace`|The source's namespace.|
|`--tenant`|The source's tenant.|
@@ -493,7 +493,7 @@ $ pulsar-admin sinks status options
|Flag|Description|
|---|---|
-|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The sink's name.|
|`--namespace`|The sink's namespace.|
|`--tenant`|The sink's tenant.|
diff --git a/site2/website-next/versioned_docs/version-2.7.0/reference-metrics.md b/site2/website-next/versioned_docs/version-2.7.0/reference-metrics.md
index b91419dd445..03457f0d0ec 100644
--- a/site2/website-next/versioned_docs/version-2.7.0/reference-metrics.md
+++ b/site2/website-next/versioned_docs/version-2.7.0/reference-metrics.md
@@ -394,7 +394,7 @@ All the Pulsar Functions metrics are labelled with the following labels:
All the proxy metrics are labelled with the following labels:
- *cluster*: `cluster=${pulsar_cluster}`. `${pulsar_cluster}` is the cluster name that you have configured in the `broker.conf` file.
-- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the kubernetes pod name.
+- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the Kubernetes pod name.
| Name | Type | Description |
|---|---|---|
diff --git a/site2/website-next/versioned_docs/version-2.7.1/functions-runtime.md b/site2/website-next/versioned_docs/version-2.7.1/functions-runtime.md
index f5c478baffb..d9eba67ac17 100644
--- a/site2/website-next/versioned_docs/version-2.7.1/functions-runtime.md
+++ b/site2/website-next/versioned_docs/version-2.7.1/functions-runtime.md
@@ -198,7 +198,7 @@ io.kubernetes.client.ApiException: Forbidden
### Integrate Kubernetes secrets
-In order to safely distribute secrets, Pulasr Functions can reference Kubernetes secrets. To enable this, set the `secretsProviderConfiguratorClassName` to `org.apache.pulsar.functions.secretsproviderconfigurator.KubernetesSecretsProviderConfigurator`.
+In order to safely distribute secrets, Pulsar Functions can reference Kubernetes secrets. To enable this, set the `secretsProviderConfiguratorClassName` to `org.apache.pulsar.functions.secretsproviderconfigurator.KubernetesSecretsProviderConfigurator`.
You can create a secret in the namespace where your functions are deployed. For example, you deploy functions to the `pulsar-func` Kubernetes namespace, and you have a secret named `database-creds` with a field name `password`, which you want to mount in the pod as an environment variable called `DATABASE_PASSWORD`. The following functions configuration enables you to reference that secret and mount the value as an environment variable in the pod.
diff --git a/site2/website-next/versioned_docs/version-2.7.1/io-cli.md b/site2/website-next/versioned_docs/version-2.7.1/io-cli.md
index 1763839c234..3d54bb61875 100644
--- a/site2/website-next/versioned_docs/version-2.7.1/io-cli.md
+++ b/site2/website-next/versioned_docs/version-2.7.1/io-cli.md
@@ -169,7 +169,7 @@ $ pulsar-admin sources status options
|Flag|Description|
|---|---|
-|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The source's name.|
|`--namespace`|The source's namespace.|
|`--tenant`|The source's tenant.|
@@ -493,7 +493,7 @@ $ pulsar-admin sinks status options
|Flag|Description|
|---|---|
-|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The sink's name.|
|`--namespace`|The sink's namespace.|
|`--tenant`|The sink's tenant.|
diff --git a/site2/website-next/versioned_docs/version-2.7.1/reference-metrics.md b/site2/website-next/versioned_docs/version-2.7.1/reference-metrics.md
index 8289e11433c..5172653659e 100644
--- a/site2/website-next/versioned_docs/version-2.7.1/reference-metrics.md
+++ b/site2/website-next/versioned_docs/version-2.7.1/reference-metrics.md
@@ -421,7 +421,7 @@ All the Pulsar Functions metrics are labelled with the following labels:
All the proxy metrics are labelled with the following labels:
- *cluster*: `cluster=${pulsar_cluster}`. `${pulsar_cluster}` is the cluster name that you have configured in the `broker.conf` file.
-- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the kubernetes pod name.
+- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the Kubernetes pod name.
| Name | Type | Description |
|---|---|---|
diff --git a/site2/website-next/versioned_docs/version-2.7.2/functions-runtime.md b/site2/website-next/versioned_docs/version-2.7.2/functions-runtime.md
index f5c478baffb..d9eba67ac17 100644
--- a/site2/website-next/versioned_docs/version-2.7.2/functions-runtime.md
+++ b/site2/website-next/versioned_docs/version-2.7.2/functions-runtime.md
@@ -198,7 +198,7 @@ io.kubernetes.client.ApiException: Forbidden
### Integrate Kubernetes secrets
-In order to safely distribute secrets, Pulasr Functions can reference Kubernetes secrets. To enable this, set the `secretsProviderConfiguratorClassName` to `org.apache.pulsar.functions.secretsproviderconfigurator.KubernetesSecretsProviderConfigurator`.
+In order to safely distribute secrets, Pulsar Functions can reference Kubernetes secrets. To enable this, set the `secretsProviderConfiguratorClassName` to `org.apache.pulsar.functions.secretsproviderconfigurator.KubernetesSecretsProviderConfigurator`.
You can create a secret in the namespace where your functions are deployed. For example, you deploy functions to the `pulsar-func` Kubernetes namespace, and you have a secret named `database-creds` with a field name `password`, which you want to mount in the pod as an environment variable called `DATABASE_PASSWORD`. The following functions configuration enables you to reference that secret and mount the value as an environment variable in the pod.
diff --git a/site2/website-next/versioned_docs/version-2.7.2/io-cli.md b/site2/website-next/versioned_docs/version-2.7.2/io-cli.md
index a9d4a8632ee..8c5faf43bd1 100644
--- a/site2/website-next/versioned_docs/version-2.7.2/io-cli.md
+++ b/site2/website-next/versioned_docs/version-2.7.2/io-cli.md
@@ -171,7 +171,7 @@ $ pulsar-admin sources status options
|Flag|Description|
|---|---|
-|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The source's name.|
|`--namespace`|The source's namespace.|
|`--tenant`|The source's tenant.|
@@ -495,7 +495,7 @@ $ pulsar-admin sinks status options
|Flag|Description|
|---|---|
-|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The sink's name.|
|`--namespace`|The sink's namespace.|
|`--tenant`|The sink's tenant.|
diff --git a/site2/website-next/versioned_docs/version-2.7.2/reference-metrics.md b/site2/website-next/versioned_docs/version-2.7.2/reference-metrics.md
index 8289e11433c..5172653659e 100644
--- a/site2/website-next/versioned_docs/version-2.7.2/reference-metrics.md
+++ b/site2/website-next/versioned_docs/version-2.7.2/reference-metrics.md
@@ -421,7 +421,7 @@ All the Pulsar Functions metrics are labelled with the following labels:
All the proxy metrics are labelled with the following labels:
- *cluster*: `cluster=${pulsar_cluster}`. `${pulsar_cluster}` is the cluster name that you have configured in the `broker.conf` file.
-- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the kubernetes pod name.
+- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the Kubernetes pod name.
| Name | Type | Description |
|---|---|---|
diff --git a/site2/website-next/versioned_docs/version-2.7.3/functions-runtime.md b/site2/website-next/versioned_docs/version-2.7.3/functions-runtime.md
index f5c478baffb..d9eba67ac17 100644
--- a/site2/website-next/versioned_docs/version-2.7.3/functions-runtime.md
+++ b/site2/website-next/versioned_docs/version-2.7.3/functions-runtime.md
@@ -198,7 +198,7 @@ io.kubernetes.client.ApiException: Forbidden
### Integrate Kubernetes secrets
-In order to safely distribute secrets, Pulasr Functions can reference Kubernetes secrets. To enable this, set the `secretsProviderConfiguratorClassName` to `org.apache.pulsar.functions.secretsproviderconfigurator.KubernetesSecretsProviderConfigurator`.
+In order to safely distribute secrets, Pulsar Functions can reference Kubernetes secrets. To enable this, set the `secretsProviderConfiguratorClassName` to `org.apache.pulsar.functions.secretsproviderconfigurator.KubernetesSecretsProviderConfigurator`.
You can create a secret in the namespace where your functions are deployed. For example, you deploy functions to the `pulsar-func` Kubernetes namespace, and you have a secret named `database-creds` with a field name `password`, which you want to mount in the pod as an environment variable called `DATABASE_PASSWORD`. The following functions configuration enables you to reference that secret and mount the value as an environment variable in the pod.
diff --git a/site2/website-next/versioned_docs/version-2.7.3/io-cli.md b/site2/website-next/versioned_docs/version-2.7.3/io-cli.md
index 1763839c234..3d54bb61875 100644
--- a/site2/website-next/versioned_docs/version-2.7.3/io-cli.md
+++ b/site2/website-next/versioned_docs/version-2.7.3/io-cli.md
@@ -169,7 +169,7 @@ $ pulsar-admin sources status options
|Flag|Description|
|---|---|
-|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The source's name.|
|`--namespace`|The source's namespace.|
|`--tenant`|The source's tenant.|
@@ -493,7 +493,7 @@ $ pulsar-admin sinks status options
|Flag|Description|
|---|---|
-|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The sink's name.|
|`--namespace`|The sink's namespace.|
|`--tenant`|The sink's tenant.|
diff --git a/site2/website-next/versioned_docs/version-2.7.3/reference-metrics.md b/site2/website-next/versioned_docs/version-2.7.3/reference-metrics.md
index 50fcd3cf24e..a146ce1907b 100644
--- a/site2/website-next/versioned_docs/version-2.7.3/reference-metrics.md
+++ b/site2/website-next/versioned_docs/version-2.7.3/reference-metrics.md
@@ -441,7 +441,7 @@ All the Pulsar Functions metrics are labelled with the following labels:
All the proxy metrics are labelled with the following labels:
- *cluster*: `cluster=${pulsar_cluster}`. `${pulsar_cluster}` is the cluster name that you have configured in the `broker.conf` file.
-- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the kubernetes pod name.
+- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the Kubernetes pod name.
| Name | Type | Description |
|---|---|---|
diff --git a/site2/website-next/versioned_docs/version-2.7.4/functions-runtime.md b/site2/website-next/versioned_docs/version-2.7.4/functions-runtime.md
index f5c478baffb..d9eba67ac17 100644
--- a/site2/website-next/versioned_docs/version-2.7.4/functions-runtime.md
+++ b/site2/website-next/versioned_docs/version-2.7.4/functions-runtime.md
@@ -198,7 +198,7 @@ io.kubernetes.client.ApiException: Forbidden
### Integrate Kubernetes secrets
-In order to safely distribute secrets, Pulasr Functions can reference Kubernetes secrets. To enable this, set the `secretsProviderConfiguratorClassName` to `org.apache.pulsar.functions.secretsproviderconfigurator.KubernetesSecretsProviderConfigurator`.
+In order to safely distribute secrets, Pulsar Functions can reference Kubernetes secrets. To enable this, set the `secretsProviderConfiguratorClassName` to `org.apache.pulsar.functions.secretsproviderconfigurator.KubernetesSecretsProviderConfigurator`.
You can create a secret in the namespace where your functions are deployed. For example, you deploy functions to the `pulsar-func` Kubernetes namespace, and you have a secret named `database-creds` with a field name `password`, which you want to mount in the pod as an environment variable called `DATABASE_PASSWORD`. The following functions configuration enables you to reference that secret and mount the value as an environment variable in the pod.
diff --git a/site2/website-next/versioned_docs/version-2.7.4/io-cli.md b/site2/website-next/versioned_docs/version-2.7.4/io-cli.md
index 1763839c234..3d54bb61875 100644
--- a/site2/website-next/versioned_docs/version-2.7.4/io-cli.md
+++ b/site2/website-next/versioned_docs/version-2.7.4/io-cli.md
@@ -169,7 +169,7 @@ $ pulsar-admin sources status options
|Flag|Description|
|---|---|
-|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The source's name.|
|`--namespace`|The source's namespace.|
|`--tenant`|The source's tenant.|
@@ -493,7 +493,7 @@ $ pulsar-admin sinks status options
|Flag|Description|
|---|---|
-|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The sink's name.|
|`--namespace`|The sink's namespace.|
|`--tenant`|The sink's tenant.|
diff --git a/site2/website-next/versioned_docs/version-2.7.4/reference-metrics.md b/site2/website-next/versioned_docs/version-2.7.4/reference-metrics.md
index 50fcd3cf24e..a146ce1907b 100644
--- a/site2/website-next/versioned_docs/version-2.7.4/reference-metrics.md
+++ b/site2/website-next/versioned_docs/version-2.7.4/reference-metrics.md
@@ -441,7 +441,7 @@ All the Pulsar Functions metrics are labelled with the following labels:
All the proxy metrics are labelled with the following labels:
- *cluster*: `cluster=${pulsar_cluster}`. `${pulsar_cluster}` is the cluster name that you have configured in the `broker.conf` file.
-- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the kubernetes pod name.
+- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the Kubernetes pod name.
| Name | Type | Description |
|---|---|---|
diff --git a/site2/website-next/versioned_docs/version-2.8.0/functions-runtime.md b/site2/website-next/versioned_docs/version-2.8.0/functions-runtime.md
index ad82299b178..ab7d1c05db4 100644
--- a/site2/website-next/versioned_docs/version-2.8.0/functions-runtime.md
+++ b/site2/website-next/versioned_docs/version-2.8.0/functions-runtime.md
@@ -235,7 +235,7 @@ io.kubernetes.client.ApiException: Forbidden
### Integrate Kubernetes secrets
-In order to safely distribute secrets, Pulasr Functions can reference Kubernetes secrets. To enable this, set the `secretsProviderConfiguratorClassName` to `org.apache.pulsar.functions.secretsproviderconfigurator.KubernetesSecretsProviderConfigurator`.
+In order to safely distribute secrets, Pulsar Functions can reference Kubernetes secrets. To enable this, set the `secretsProviderConfiguratorClassName` to `org.apache.pulsar.functions.secretsproviderconfigurator.KubernetesSecretsProviderConfigurator`.
You can create a secret in the namespace where your functions are deployed. For example, you deploy functions to the `pulsar-func` Kubernetes namespace, and you have a secret named `database-creds` with a field name `password`, which you want to mount in the pod as an environment variable called `DATABASE_PASSWORD`. The following functions configuration enables you to reference that secret and mount the value as an environment variable in the pod.
diff --git a/site2/website-next/versioned_docs/version-2.8.0/io-cli.md b/site2/website-next/versioned_docs/version-2.8.0/io-cli.md
index 1763839c234..3d54bb61875 100644
--- a/site2/website-next/versioned_docs/version-2.8.0/io-cli.md
+++ b/site2/website-next/versioned_docs/version-2.8.0/io-cli.md
@@ -169,7 +169,7 @@ $ pulsar-admin sources status options
|Flag|Description|
|---|---|
-|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The source's name.|
|`--namespace`|The source's namespace.|
|`--tenant`|The source's tenant.|
@@ -493,7 +493,7 @@ $ pulsar-admin sinks status options
|Flag|Description|
|---|---|
-|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The sink's name.|
|`--namespace`|The sink's namespace.|
|`--tenant`|The sink's tenant.|
diff --git a/site2/website-next/versioned_docs/version-2.8.0/reference-metrics.md b/site2/website-next/versioned_docs/version-2.8.0/reference-metrics.md
index c0a8d8eac3e..24a67d4b81d 100644
--- a/site2/website-next/versioned_docs/version-2.8.0/reference-metrics.md
+++ b/site2/website-next/versioned_docs/version-2.8.0/reference-metrics.md
@@ -28,7 +28,7 @@ The following types of metrics are available:
The ZooKeeper metrics are exposed under "/metrics" at port `8000`. You can use a different port by configuring the `metricsProvider.httpPort` in conf/zookeeper.conf.
-ZooKeeper provides a New Metrics System since 3.6.0, more detailed metrics can refer [ZooKeeper Monitor Guide](https://zookeeper.apache.org/doc/r3.7.0/zookeeperMonitor.html).
+ZooKeeper provides a New Metrics System since 3.6.0. For more detailed metrics, refer to the [ZooKeeper Monitor Guide](https://zookeeper.apache.org/doc/r3.7.0/zookeeperMonitor.html).
## BookKeeper
@@ -497,7 +497,7 @@ Connector metrics contain **source** metrics and **sink** metrics.
All the proxy metrics are labelled with the following labels:
- *cluster*: `cluster=${pulsar_cluster}`. `${pulsar_cluster}` is the cluster name that you have configured in the `broker.conf` file.
-- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the kubernetes pod name.
+- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the Kubernetes pod name.
| Name | Type | Description |
|---|---|---|
diff --git a/site2/website-next/versioned_docs/version-2.8.1/functions-runtime.md b/site2/website-next/versioned_docs/version-2.8.1/functions-runtime.md
index ad82299b178..ab7d1c05db4 100644
--- a/site2/website-next/versioned_docs/version-2.8.1/functions-runtime.md
+++ b/site2/website-next/versioned_docs/version-2.8.1/functions-runtime.md
@@ -235,7 +235,7 @@ io.kubernetes.client.ApiException: Forbidden
### Integrate Kubernetes secrets
-In order to safely distribute secrets, Pulasr Functions can reference Kubernetes secrets. To enable this, set the `secretsProviderConfiguratorClassName` to `org.apache.pulsar.functions.secretsproviderconfigurator.KubernetesSecretsProviderConfigurator`.
+In order to safely distribute secrets, Pulsar Functions can reference Kubernetes secrets. To enable this, set the `secretsProviderConfiguratorClassName` to `org.apache.pulsar.functions.secretsproviderconfigurator.KubernetesSecretsProviderConfigurator`.
You can create a secret in the namespace where your functions are deployed. For example, you deploy functions to the `pulsar-func` Kubernetes namespace, and you have a secret named `database-creds` with a field name `password`, which you want to mount in the pod as an environment variable called `DATABASE_PASSWORD`. The following functions configuration enables you to reference that secret and mount the value as an environment variable in the pod.
diff --git a/site2/website-next/versioned_docs/version-2.8.1/io-cli.md b/site2/website-next/versioned_docs/version-2.8.1/io-cli.md
index 1763839c234..3d54bb61875 100644
--- a/site2/website-next/versioned_docs/version-2.8.1/io-cli.md
+++ b/site2/website-next/versioned_docs/version-2.8.1/io-cli.md
@@ -169,7 +169,7 @@ $ pulsar-admin sources status options
|Flag|Description|
|---|---|
-|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The source's name.|
|`--namespace`|The source's namespace.|
|`--tenant`|The source's tenant.|
@@ -493,7 +493,7 @@ $ pulsar-admin sinks status options
|Flag|Description|
|---|---|
-|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The sink's name.|
|`--namespace`|The sink's namespace.|
|`--tenant`|The sink's tenant.|
diff --git a/site2/website-next/versioned_docs/version-2.8.1/reference-metrics.md b/site2/website-next/versioned_docs/version-2.8.1/reference-metrics.md
index 1a4a9aaeee8..9ec2cec93be 100644
--- a/site2/website-next/versioned_docs/version-2.8.1/reference-metrics.md
+++ b/site2/website-next/versioned_docs/version-2.8.1/reference-metrics.md
@@ -28,7 +28,7 @@ The following types of metrics are available:
The ZooKeeper metrics are exposed under "/metrics" at port `8000`. You can use a different port by configuring the `metricsProvider.httpPort` in conf/zookeeper.conf.
-ZooKeeper provides a New Metrics System since 3.6.0, more detailed metrics can refer [ZooKeeper Monitor Guide](https://zookeeper.apache.org/doc/r3.7.0/zookeeperMonitor.html).
+ZooKeeper provides a New Metrics System since 3.6.0. For more detailed metrics, refer to the [ZooKeeper Monitor Guide](https://zookeeper.apache.org/doc/r3.7.0/zookeeperMonitor.html).
## BookKeeper
@@ -500,7 +500,7 @@ Connector metrics contain **source** metrics and **sink** metrics.
All the proxy metrics are labelled with the following labels:
- *cluster*: `cluster=${pulsar_cluster}`. `${pulsar_cluster}` is the cluster name that you have configured in the `broker.conf` file.
-- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the kubernetes pod name.
+- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the Kubernetes pod name.
| Name | Type | Description |
|---|---|---|
diff --git a/site2/website-next/versioned_docs/version-2.8.2/functions-runtime.md b/site2/website-next/versioned_docs/version-2.8.2/functions-runtime.md
index ad82299b178..ab7d1c05db4 100644
--- a/site2/website-next/versioned_docs/version-2.8.2/functions-runtime.md
+++ b/site2/website-next/versioned_docs/version-2.8.2/functions-runtime.md
@@ -235,7 +235,7 @@ io.kubernetes.client.ApiException: Forbidden
### Integrate Kubernetes secrets
-In order to safely distribute secrets, Pulasr Functions can reference Kubernetes secrets. To enable this, set the `secretsProviderConfiguratorClassName` to `org.apache.pulsar.functions.secretsproviderconfigurator.KubernetesSecretsProviderConfigurator`.
+In order to safely distribute secrets, Pulsar Functions can reference Kubernetes secrets. To enable this, set the `secretsProviderConfiguratorClassName` to `org.apache.pulsar.functions.secretsproviderconfigurator.KubernetesSecretsProviderConfigurator`.
You can create a secret in the namespace where your functions are deployed. For example, you deploy functions to the `pulsar-func` Kubernetes namespace, and you have a secret named `database-creds` with a field name `password`, which you want to mount in the pod as an environment variable called `DATABASE_PASSWORD`. The following functions configuration enables you to reference that secret and mount the value as an environment variable in the pod.
diff --git a/site2/website-next/versioned_docs/version-2.8.2/io-cli.md b/site2/website-next/versioned_docs/version-2.8.2/io-cli.md
index 1763839c234..3d54bb61875 100644
--- a/site2/website-next/versioned_docs/version-2.8.2/io-cli.md
+++ b/site2/website-next/versioned_docs/version-2.8.2/io-cli.md
@@ -169,7 +169,7 @@ $ pulsar-admin sources status options
|Flag|Description|
|---|---|
-|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The source's name.|
|`--namespace`|The source's namespace.|
|`--tenant`|The source's tenant.|
@@ -493,7 +493,7 @@ $ pulsar-admin sinks status options
|Flag|Description|
|---|---|
-|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The sink's name.|
|`--namespace`|The sink's namespace.|
|`--tenant`|The sink's tenant.|
diff --git a/site2/website-next/versioned_docs/version-2.8.2/reference-metrics.md b/site2/website-next/versioned_docs/version-2.8.2/reference-metrics.md
index 97bf22af85a..4c0f307b7e6 100644
--- a/site2/website-next/versioned_docs/version-2.8.2/reference-metrics.md
+++ b/site2/website-next/versioned_docs/version-2.8.2/reference-metrics.md
@@ -28,7 +28,7 @@ The following types of metrics are available:
The ZooKeeper metrics are exposed under "/metrics" at port `8000`. You can use a different port by configuring the `metricsProvider.httpPort` in conf/zookeeper.conf.
-ZooKeeper provides a New Metrics System since 3.6.0, more detailed metrics can refer [ZooKeeper Monitor Guide](https://zookeeper.apache.org/doc/r3.7.0/zookeeperMonitor.html).
+ZooKeeper provides a New Metrics System since 3.6.0. For more detailed metrics, refer to the [ZooKeeper Monitor Guide](https://zookeeper.apache.org/doc/r3.7.0/zookeeperMonitor.html).
## BookKeeper
@@ -509,7 +509,7 @@ Connector metrics contain **source** metrics and **sink** metrics.
All the proxy metrics are labelled with the following labels:
- *cluster*: `cluster=${pulsar_cluster}`. `${pulsar_cluster}` is the cluster name that you have configured in the `broker.conf` file.
-- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the kubernetes pod name.
+- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the Kubernetes pod name.
| Name | Type | Description |
|---|---|---|
diff --git a/site2/website-next/versioned_docs/version-2.8.3/functions-runtime.md b/site2/website-next/versioned_docs/version-2.8.3/functions-runtime.md
index ad82299b178..ab7d1c05db4 100644
--- a/site2/website-next/versioned_docs/version-2.8.3/functions-runtime.md
+++ b/site2/website-next/versioned_docs/version-2.8.3/functions-runtime.md
@@ -235,7 +235,7 @@ io.kubernetes.client.ApiException: Forbidden
### Integrate Kubernetes secrets
-In order to safely distribute secrets, Pulasr Functions can reference Kubernetes secrets. To enable this, set the `secretsProviderConfiguratorClassName` to `org.apache.pulsar.functions.secretsproviderconfigurator.KubernetesSecretsProviderConfigurator`.
+In order to safely distribute secrets, Pulsar Functions can reference Kubernetes secrets. To enable this, set the `secretsProviderConfiguratorClassName` to `org.apache.pulsar.functions.secretsproviderconfigurator.KubernetesSecretsProviderConfigurator`.
You can create a secret in the namespace where your functions are deployed. For example, you deploy functions to the `pulsar-func` Kubernetes namespace, and you have a secret named `database-creds` with a field name `password`, which you want to mount in the pod as an environment variable called `DATABASE_PASSWORD`. The following functions configuration enables you to reference that secret and mount the value as an environment variable in the pod.
diff --git a/site2/website-next/versioned_docs/version-2.8.3/io-cli.md b/site2/website-next/versioned_docs/version-2.8.3/io-cli.md
index 1763839c234..3d54bb61875 100644
--- a/site2/website-next/versioned_docs/version-2.8.3/io-cli.md
+++ b/site2/website-next/versioned_docs/version-2.8.3/io-cli.md
@@ -169,7 +169,7 @@ $ pulsar-admin sources status options
|Flag|Description|
|---|---|
-|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The source's name.|
|`--namespace`|The source's namespace.|
|`--tenant`|The source's tenant.|
@@ -493,7 +493,7 @@ $ pulsar-admin sinks status options
|Flag|Description|
|---|---|
-|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The sink's name.|
|`--namespace`|The sink's namespace.|
|`--tenant`|The sink's tenant.|
diff --git a/site2/website-next/versioned_docs/version-2.8.3/reference-metrics.md b/site2/website-next/versioned_docs/version-2.8.3/reference-metrics.md
index 97bf22af85a..4c0f307b7e6 100644
--- a/site2/website-next/versioned_docs/version-2.8.3/reference-metrics.md
+++ b/site2/website-next/versioned_docs/version-2.8.3/reference-metrics.md
@@ -28,7 +28,7 @@ The following types of metrics are available:
The ZooKeeper metrics are exposed under "/metrics" at port `8000`. You can use a different port by configuring the `metricsProvider.httpPort` in conf/zookeeper.conf.
-ZooKeeper provides a New Metrics System since 3.6.0, more detailed metrics can refer [ZooKeeper Monitor Guide](https://zookeeper.apache.org/doc/r3.7.0/zookeeperMonitor.html).
+ZooKeeper provides a New Metrics System since 3.6.0. For more detailed metrics, refer to the [ZooKeeper Monitor Guide](https://zookeeper.apache.org/doc/r3.7.0/zookeeperMonitor.html).
## BookKeeper
@@ -509,7 +509,7 @@ Connector metrics contain **source** metrics and **sink** metrics.
All the proxy metrics are labelled with the following labels:
- *cluster*: `cluster=${pulsar_cluster}`. `${pulsar_cluster}` is the cluster name that you have configured in the `broker.conf` file.
-- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the kubernetes pod name.
+- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the Kubernetes pod name.
| Name | Type | Description |
|---|---|---|
diff --git a/site2/website-next/versioned_docs/version-2.9.0/functions-runtime.md b/site2/website-next/versioned_docs/version-2.9.0/functions-runtime.md
index 5ed48badd30..7164bd13668 100644
--- a/site2/website-next/versioned_docs/version-2.9.0/functions-runtime.md
+++ b/site2/website-next/versioned_docs/version-2.9.0/functions-runtime.md
@@ -239,7 +239,7 @@ io.kubernetes.client.ApiException: Forbidden
### Integrate Kubernetes secrets
-In order to safely distribute secrets, Pulasr Functions can reference Kubernetes secrets. To enable this, set the `secretsProviderConfiguratorClassName` to `org.apache.pulsar.functions.secretsproviderconfigurator.KubernetesSecretsProviderConfigurator`.
+In order to safely distribute secrets, Pulsar Functions can reference Kubernetes secrets. To enable this, set the `secretsProviderConfiguratorClassName` to `org.apache.pulsar.functions.secretsproviderconfigurator.KubernetesSecretsProviderConfigurator`.
You can create a secret in the namespace where your functions are deployed. For example, you deploy functions to the `pulsar-func` Kubernetes namespace, and you have a secret named `database-creds` with a field name `password`, which you want to mount in the pod as an environment variable called `DATABASE_PASSWORD`. The following functions configuration enables you to reference that secret and mount the value as an environment variable in the pod.
diff --git a/site2/website-next/versioned_docs/version-2.9.0/io-cli.md b/site2/website-next/versioned_docs/version-2.9.0/io-cli.md
index 1763839c234..3d54bb61875 100644
--- a/site2/website-next/versioned_docs/version-2.9.0/io-cli.md
+++ b/site2/website-next/versioned_docs/version-2.9.0/io-cli.md
@@ -169,7 +169,7 @@ $ pulsar-admin sources status options
|Flag|Description|
|---|---|
-|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The source's name.|
|`--namespace`|The source's namespace.|
|`--tenant`|The source's tenant.|
@@ -493,7 +493,7 @@ $ pulsar-admin sinks status options
|Flag|Description|
|---|---|
-|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The sink's name.|
|`--namespace`|The sink's namespace.|
|`--tenant`|The sink's tenant.|
diff --git a/site2/website-next/versioned_docs/version-2.9.0/reference-metrics.md b/site2/website-next/versioned_docs/version-2.9.0/reference-metrics.md
index 4658cce37c7..96c378c3c5d 100644
--- a/site2/website-next/versioned_docs/version-2.9.0/reference-metrics.md
+++ b/site2/website-next/versioned_docs/version-2.9.0/reference-metrics.md
@@ -501,7 +501,7 @@ Connector metrics contain **source** metrics and **sink** metrics.
All the proxy metrics are labelled with the following labels:
- *cluster*: `cluster=${pulsar_cluster}`. `${pulsar_cluster}` is the cluster name that you have configured in the `broker.conf` file.
-- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the kubernetes pod name.
+- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the Kubernetes pod name.
| Name | Type | Description |
|---|---|---|
diff --git a/site2/website-next/versioned_docs/version-2.9.1/functions-runtime.md b/site2/website-next/versioned_docs/version-2.9.1/functions-runtime.md
index 5ed48badd30..7164bd13668 100644
--- a/site2/website-next/versioned_docs/version-2.9.1/functions-runtime.md
+++ b/site2/website-next/versioned_docs/version-2.9.1/functions-runtime.md
@@ -239,7 +239,7 @@ io.kubernetes.client.ApiException: Forbidden
### Integrate Kubernetes secrets
-In order to safely distribute secrets, Pulasr Functions can reference Kubernetes secrets. To enable this, set the `secretsProviderConfiguratorClassName` to `org.apache.pulsar.functions.secretsproviderconfigurator.KubernetesSecretsProviderConfigurator`.
+In order to safely distribute secrets, Pulsar Functions can reference Kubernetes secrets. To enable this, set the `secretsProviderConfiguratorClassName` to `org.apache.pulsar.functions.secretsproviderconfigurator.KubernetesSecretsProviderConfigurator`.
You can create a secret in the namespace where your functions are deployed. For example, you deploy functions to the `pulsar-func` Kubernetes namespace, and you have a secret named `database-creds` with a field name `password`, which you want to mount in the pod as an environment variable called `DATABASE_PASSWORD`. The following functions configuration enables you to reference that secret and mount the value as an environment variable in the pod.
diff --git a/site2/website-next/versioned_docs/version-2.9.1/io-cli.md b/site2/website-next/versioned_docs/version-2.9.1/io-cli.md
index 1763839c234..3d54bb61875 100644
--- a/site2/website-next/versioned_docs/version-2.9.1/io-cli.md
+++ b/site2/website-next/versioned_docs/version-2.9.1/io-cli.md
@@ -169,7 +169,7 @@ $ pulsar-admin sources status options
|Flag|Description|
|---|---|
-|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The source's name.|
|`--namespace`|The source's namespace.|
|`--tenant`|The source's tenant.|
@@ -493,7 +493,7 @@ $ pulsar-admin sinks status options
|Flag|Description|
|---|---|
-|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The sink's name.|
|`--namespace`|The sink's namespace.|
|`--tenant`|The sink's tenant.|
diff --git a/site2/website-next/versioned_docs/version-2.9.1/reference-metrics.md b/site2/website-next/versioned_docs/version-2.9.1/reference-metrics.md
index 4658cce37c7..96c378c3c5d 100644
--- a/site2/website-next/versioned_docs/version-2.9.1/reference-metrics.md
+++ b/site2/website-next/versioned_docs/version-2.9.1/reference-metrics.md
@@ -501,7 +501,7 @@ Connector metrics contain **source** metrics and **sink** metrics.
All the proxy metrics are labelled with the following labels:
- *cluster*: `cluster=${pulsar_cluster}`. `${pulsar_cluster}` is the cluster name that you have configured in the `broker.conf` file.
-- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the kubernetes pod name.
+- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the Kubernetes pod name.
| Name | Type | Description |
|---|---|---|
diff --git a/site2/website-next/versioned_docs/version-2.9.2/functions-runtime.md b/site2/website-next/versioned_docs/version-2.9.2/functions-runtime.md
index 5ed48badd30..7164bd13668 100644
--- a/site2/website-next/versioned_docs/version-2.9.2/functions-runtime.md
+++ b/site2/website-next/versioned_docs/version-2.9.2/functions-runtime.md
@@ -239,7 +239,7 @@ io.kubernetes.client.ApiException: Forbidden
### Integrate Kubernetes secrets
-In order to safely distribute secrets, Pulasr Functions can reference Kubernetes secrets. To enable this, set the `secretsProviderConfiguratorClassName` to `org.apache.pulsar.functions.secretsproviderconfigurator.KubernetesSecretsProviderConfigurator`.
+In order to safely distribute secrets, Pulsar Functions can reference Kubernetes secrets. To enable this, set the `secretsProviderConfiguratorClassName` to `org.apache.pulsar.functions.secretsproviderconfigurator.KubernetesSecretsProviderConfigurator`.
You can create a secret in the namespace where your functions are deployed. For example, you deploy functions to the `pulsar-func` Kubernetes namespace, and you have a secret named `database-creds` with a field name `password`, which you want to mount in the pod as an environment variable called `DATABASE_PASSWORD`. The following functions configuration enables you to reference that secret and mount the value as an environment variable in the pod.
diff --git a/site2/website-next/versioned_docs/version-2.9.2/io-cli.md b/site2/website-next/versioned_docs/version-2.9.2/io-cli.md
index 1763839c234..3d54bb61875 100644
--- a/site2/website-next/versioned_docs/version-2.9.2/io-cli.md
+++ b/site2/website-next/versioned_docs/version-2.9.2/io-cli.md
@@ -169,7 +169,7 @@ $ pulsar-admin sources status options
|Flag|Description|
|---|---|
-|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The source ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The source's name.|
|`--namespace`|The source's namespace.|
|`--tenant`|The source's tenant.|
@@ -493,7 +493,7 @@ $ pulsar-admin sinks status options
|Flag|Description|
|---|---|
-|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulasr gets status of all instances.|
+|`--instance-id`|The sink ID.<br />If `instance-id` is not provided, Pulsar gets status of all instances.|
|`--name`|The sink's name.|
|`--namespace`|The sink's namespace.|
|`--tenant`|The sink's tenant.|
diff --git a/site2/website-next/versioned_docs/version-2.9.2/reference-metrics.md b/site2/website-next/versioned_docs/version-2.9.2/reference-metrics.md
index 4658cce37c7..96c378c3c5d 100644
--- a/site2/website-next/versioned_docs/version-2.9.2/reference-metrics.md
+++ b/site2/website-next/versioned_docs/version-2.9.2/reference-metrics.md
@@ -501,7 +501,7 @@ Connector metrics contain **source** metrics and **sink** metrics.
All the proxy metrics are labelled with the following labels:
- *cluster*: `cluster=${pulsar_cluster}`. `${pulsar_cluster}` is the cluster name that you have configured in the `broker.conf` file.
-- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the kubernetes pod name.
+- *kubernetes_pod_name*: `kubernetes_pod_name=${kubernetes_pod_name}`. `${kubernetes_pod_name}` is the Kubernetes pod name.
| Name | Type | Description |
|---|---|---|