This is an automated email from the ASF dual-hosted git repository. rxl pushed a commit to branch branch-2.6 in repository https://gitbox.apache.org/repos/asf/pulsar.git
commit 1fd55cf6cbf8b190e995477c4000559c57eaad63 Author: HuanliMeng <[email protected]> AuthorDate: Fri Jul 3 13:54:27 2020 +0800 [Doc]--Add labels to function statefulsets and services (#7428) ### Motivation Pulsar release 2.4.0 supports Adding labels to function statefulsets and services. The code is implemented but the doc is not updated accordingly. Here is the code update PR: https://github.com/apache/pulsar/pull/4038 Therefore, i make this PR to update docs for releases: master/2.5.2/2.5.1/2.5.0/2.4.2/2.4.1/2.4.0 ### Modifications Add a note in the doc "Setup: Configure Functions runtime" under the Pulsar Functions section (cherry picked from commit 4a041698dae58ddc851a7eccdd31e0a350328a24) --- site2/docs/functions-runtime.md | 3 +++ site2/website/versioned_docs/version-2.4.0/functions-runtime.md | 3 +++ site2/website/versioned_docs/version-2.4.1/functions-runtime.md | 3 +++ site2/website/versioned_docs/version-2.4.2/functions-runtime.md | 3 +++ site2/website/versioned_docs/version-2.5.0/functions-runtime.md | 3 +++ site2/website/versioned_docs/version-2.5.1/functions-runtime.md | 3 +++ site2/website/versioned_docs/version-2.5.2/functions-runtime.md | 3 +++ 7 files changed, 21 insertions(+) diff --git a/site2/docs/functions-runtime.md b/site2/docs/functions-runtime.md index 3b4ce79..5134eb7 100644 --- a/site2/docs/functions-runtime.md +++ b/site2/docs/functions-runtime.md @@ -10,6 +10,9 @@ Pulsar Functions support the following methods to run functions. - *Process*: Invoke functions in processes forked by Functions Worker. - *Kubernetes*: Submit functions as Kubernetes StatefulSets by Functions Worker. +#### Note +> Pulsar supports adding labels to the Kubernetes StatefulSets and services while launching functions, which facilitates selecting the target Kubernetes objects. + The differences of the thread and process modes are: - Thread mode: when a function runs in thread mode, it runs on the same Java virtual machine (JVM) with Functions worker. - Process mode: when a function runs in process mode, it runs on the same machine that Functions worker runs. diff --git a/site2/website/versioned_docs/version-2.4.0/functions-runtime.md b/site2/website/versioned_docs/version-2.4.0/functions-runtime.md index 7ce699b..e7934e4 100644 --- a/site2/website/versioned_docs/version-2.4.0/functions-runtime.md +++ b/site2/website/versioned_docs/version-2.4.0/functions-runtime.md @@ -12,6 +12,9 @@ Pulsar Functions support the following methods to run functions. - *Process*: Invoke functions in processes forked by Functions Worker. - *Kubernetes*: Submit functions as Kubernetes StatefulSets by Functions Worker. +#### Note +> Pulsar supports adding labels to the Kubernetes StatefulSets and services while launching functions, which facilitates selecting the target Kubernetes objects. + ## Configure thread runtime It is easy to configure *Thread* runtime. In most cases, you do not need to configure anything. You can customize the thread group name with the following settings: diff --git a/site2/website/versioned_docs/version-2.4.1/functions-runtime.md b/site2/website/versioned_docs/version-2.4.1/functions-runtime.md index ab26cd7..200ade2 100644 --- a/site2/website/versioned_docs/version-2.4.1/functions-runtime.md +++ b/site2/website/versioned_docs/version-2.4.1/functions-runtime.md @@ -11,6 +11,9 @@ Pulsar Functions support the following methods to run functions. - *Process*: Invoke functions in processes forked by Functions Worker. - *Kubernetes*: Submit functions as Kubernetes StatefulSets by Functions Worker. +#### Note +> Pulsar supports adding labels to the Kubernetes StatefulSets and services while launching functions, which facilitates selecting the target Kubernetes objects. + The differences of the thread and process modes are: - Thread mode: when a function runs in thread mode, it runs on the same Java virtual machine (JVM) with Functions worker. - Process mode: when a function runs in process mode, it runs on the same machine that Functions worker runs. diff --git a/site2/website/versioned_docs/version-2.4.2/functions-runtime.md b/site2/website/versioned_docs/version-2.4.2/functions-runtime.md index 4fb98ad..2d2d7a0 100644 --- a/site2/website/versioned_docs/version-2.4.2/functions-runtime.md +++ b/site2/website/versioned_docs/version-2.4.2/functions-runtime.md @@ -11,6 +11,9 @@ Pulsar Functions support the following methods to run functions. - *Process*: Invoke functions in processes forked by Functions Worker. - *Kubernetes*: Submit functions as Kubernetes StatefulSets by Functions Worker. +#### Note +> Pulsar supports adding labels to the Kubernetes StatefulSets and services while launching functions, which facilitates selecting the target Kubernetes objects. + The differences of the thread and process modes are: - Thread mode: when a function runs in thread mode, it runs on the same Java virtual machine (JVM) with Functions worker. - Process mode: when a function runs in process mode, it runs on the same machine that Functions worker runs. diff --git a/site2/website/versioned_docs/version-2.5.0/functions-runtime.md b/site2/website/versioned_docs/version-2.5.0/functions-runtime.md index bf83fef..2a1e6cb 100644 --- a/site2/website/versioned_docs/version-2.5.0/functions-runtime.md +++ b/site2/website/versioned_docs/version-2.5.0/functions-runtime.md @@ -11,6 +11,9 @@ Pulsar Functions support the following methods to run functions. - *Process*: Invoke functions in processes forked by Functions Worker. - *Kubernetes*: Submit functions as Kubernetes StatefulSets by Functions Worker. +#### Note +> Pulsar supports adding labels to the Kubernetes StatefulSets and services while launching functions, which facilitates selecting the target Kubernetes objects. + The differences of the thread and process modes are: - Thread mode: when a function runs in thread mode, it runs on the same Java virtual machine (JVM) with Functions worker. - Process mode: when a function runs in process mode, it runs on the same machine that Functions worker runs. diff --git a/site2/website/versioned_docs/version-2.5.1/functions-runtime.md b/site2/website/versioned_docs/version-2.5.1/functions-runtime.md index 6912fdf..06e18c9 100644 --- a/site2/website/versioned_docs/version-2.5.1/functions-runtime.md +++ b/site2/website/versioned_docs/version-2.5.1/functions-runtime.md @@ -11,6 +11,9 @@ Pulsar Functions support the following methods to run functions. - *Process*: Invoke functions in processes forked by Functions Worker. - *Kubernetes*: Submit functions as Kubernetes StatefulSets by Functions Worker. +#### Note +> Pulsar supports adding labels to the Kubernetes StatefulSets and services while launching functions, which facilitates selecting the target Kubernetes objects. + The differences of the thread and process modes are: - Thread mode: when a function runs in thread mode, it runs on the same Java virtual machine (JVM) with Functions worker. - Process mode: when a function runs in process mode, it runs on the same machine that Functions worker runs. diff --git a/site2/website/versioned_docs/version-2.5.2/functions-runtime.md b/site2/website/versioned_docs/version-2.5.2/functions-runtime.md index 7e28409..edddae6 100644 --- a/site2/website/versioned_docs/version-2.5.2/functions-runtime.md +++ b/site2/website/versioned_docs/version-2.5.2/functions-runtime.md @@ -11,6 +11,9 @@ Pulsar Functions support the following methods to run functions. - *Process*: Invoke functions in processes forked by Functions Worker. - *Kubernetes*: Submit functions as Kubernetes StatefulSets by Functions Worker. +#### Note +> Pulsar supports adding labels to the Kubernetes StatefulSets and services while launching functions, which facilitates selecting the target Kubernetes objects. + The differences of the thread and process modes are: - Thread mode: when a function runs in thread mode, it runs on the same Java virtual machine (JVM) with Functions worker. - Process mode: when a function runs in process mode, it runs on the same machine that Functions worker runs.
