Installation

This document describes how to install Function Mesh based on your application in Kubernetes and how to start Function Mesh Worker service in case you want to use the pulsar-admin CLI tool to manage Pulsar Functions and connectors.

Install Function Mesh

This section describes how to install Function Mesh through the install.sh script or through the Helm.

Prerequisites

Before installing Function Mesh, ensure to perform the following operations.

• Kubernetes server v1.17 or higher.
• Create and connect to a Kubernetes cluster.
• Create a Pulsar cluster in the Kubernetes cluster.
• Deploy Pulsar Functions.
• (Optional) enable Role-based Access Control (RBAC).

Install Function Mesh through install.sh script

This example shows how to use the install.sh command to install Function Mesh on your laptop (Linux or Mac OS), including a local kind cluster, all the Custom Resource Definitions (CRDs), required service account configuration, and Function Mesh components.

curl -sSL https://github.com/streamnative/function-mesh/releases/download/v0.2.0/install.sh | bash

After executing the above command, you should be able to see the output indicating that the Function Mesh pod is up and running. For details, see verify installation.

Note

The install.sh command is suitable for trying Function Mesh out. If you want to deploy Function Mesh in production or other mission-critical scenarios, it is recommended to install Function Mesh through Helm.

Install Function Mesh through Helm

This example shows how to install Function Mesh through Helm.

Note

• Before installation, ensure that Helm v3 is installed properly.
• For the use of kubectl commands, see kubectl command reference.

1. Add the StreamNative Function Mesh repository.

   helm repo add function-mesh http://charts.functionmesh.io/
   helm repo update

2. Install the Function Mesh Operator.

   Let's set some variables for convenient use later.

   export FUNCTION_MESH_RELEASE_NAME=function-mesh  # change the release name according to your scenario
   export FUNCTION_MESH_RELEASE_NAMESPACE=function-mesh  # change the namespace to where you want to install Function Mesh

   Install the Function Mesh Operator via following command.

   Note

   • If no Kubernetes namespace is specified, the default namespace is used.

   • If the namespace ${FUNCTION_MESH_RELEASE_NAMESPACE} doesn't exist yet, you can add the parameter --create-namespace to create it automatically.

   helm install ${FUNCTION_MESH_RELEASE_NAME} function-mesh/function-mesh-operator -n ${FUNCTION_MESH_RELEASE_NAMESPACE}

   This table outlines the configurable parameters of the Function Mesh Operator and their default values.

   Parameters	Description	Default
   enable-leader-election	Whether the Function Mesh Controller Manager should enable leader election.	true
   enable-pprof	Whether the Function Mesh Controller Manager should enable pprof.	false
   pprof-addr	The address of the pprof.	:8090
   metrics-addr	The address of the metrics.	:8080
   health-probe-addr	The address of the health probe.	:8000
   config-file	The configuration file of the Function Mesh Controller Manager, which includes runnerImages, resourceLabels, and resourceAnnotations configurations. - runnerImage: the runner image to run the Pulsar Function instances. Currently, it supports Java, Python, and Go runner images. - resourceLabels: set labels for Pulsar Functions, Sources, or Sinks. - resourceAnnotations: set annotations for Pulsar Functions, Sources, or Sinks.	/etc/config/configs.yaml

   For example, if you want to enable pprof for the Function Mesh Operator, set the controllerManager.pprof.enable to true.

   helm install ${FUNCTION_MESH_RELEASE_NAME} function-mesh/function-mesh-operator -n ${FUNCTION_MESH_RELEASE_NAMESPACE} \
     --set controllerManager.pprof.enable=true

3. Check whether Function Mesh is installed successfully.

   kubectl get pods --namespace ${FUNCTION_MESH_RELEASE_NAMESPACE} -l app.kubernetes.io/instance=function-mesh

   Output

   NAME                                               READY   STATUS    RESTARTS   AGE
   function-mesh-controller-manager-5f867557c-d6vf4   1/1     Running   0          8s

Verify installation

• This example shows how to verify whether Function Mesh is installed successfully.

  Note

  ${NAMESPACE} indicates the namespace where Function Mesh Operator is installed.

  kubectl get pods --namespace ${NAMEPSACE} -l app.kubernetes.io/instance=function-mesh

  Output

  NAME                                               READY   STATUS    RESTARTS   AGE
  function-mesh-controller-manager-5f867557c-d6vf4   1/1     Running   0          8s

• This example shows how to verify whether Function Mesh can run properly.

  After installing the Function Mesh Operator and deploying a Pulsar cluster, you can submit a sample CRD to create Pulsar Functions, source, sink, or Function Mesh. In this example, a CRD is submitted to the Pulsar cluster for creating a Pulsar Function. You can also submit other CRDs under the ./config/samples directory.

  1. Submit a sample CRD to the Pulsar cluster.

     kubectl apply -f config/samples/compute_v1alpha1_function.yaml

  2. Verify your submission with the kubectl command, and you can see that the Function pod is running.

     kubectl get all
     NAME                                READY   STATUS      RESTARTS   AGE
     pod/function-sample-0               1/1     Running     0          77s

Uninstall Function Mesh

Use the following command to uninstall Function Mesh through Helm.

Note

${NAMESPACE} indicates the namespace where Function Mesh Operator is installed.

helm delete function-mesh -n ${NAMESPACE}

Work with pulsar-admin CLI tool

Function Mesh supports Function Mesh Worker service, which can forward requests to the Kubernetes cluster. After Function Mesh Worker service is started, users can use the pulsar-admin CLI tool to manage Pulsar Functions and connectors.

Limitations

• Function Mesh Worker service is only available for Pulsar 2.8.0 or higher.
• The Function Mesh Worker service cannot manage the FunctionMesh CRD.
• You need to configure the clusterName, inputTypeClassName, outputTypeClassName parameters through the custom-runtime-options option when creating or updating Pulsar Functions or connectors.
• You need to manually manage the ConfigMap, such as the Pulsar service URL.

To start Function Mesh Worker service, follow these steps.

1. Add the following Function Mesh Worker service configuration to your functions_worker.yml configuration file.

   functionsWorkerServiceNarPackage: /YOUR-NAR-PATH/function-mesh-worker-service-{version}.nar

   Replace the YOUR-NAR-PATH variable with your real local path.

2. Start Pulsar.

   This example shows how to start Pulsar through Helm.

   helm install \
       --values examples/values-minikube.yaml \
       --set initialize=true \
       --namespace pulsar \
       pulsar-mini apache/pulsar

3. Start Function Mesh Operator.

   If the namespace function-mesh doesn't exist yet, you can add the parameter --create-namespace to create it automatically.

   helm install function-mesh function-mesh/function-mesh-operator -n function-mesh

4. Verify whether the Function Mesh Worker service is started successfully.

   ./bin/pulsar-admin --admin-url  WEB_SERVICE_URL functions status --tenant TENANT_NAME --namespace NAMESPACE_NAME --name FUNCTION_NAME

   You should see a similar output as below.

   Output

   {
   "numInstances" : 1,
   "numRunning" : 1,
   "instances" : [ {
       "instanceId" : 0,
       "status" : {
       "running" : true,
       "error" : "",
       "numRestarts" : 0,
       "numReceived" : 0,
       "numSuccessfullyProcessed" : 0,
       "numUserExceptions" : 0,
       "latestUserExceptions" : [ ],
       "numSystemExceptions" : 0,
       "latestSystemExceptions" : [ ],
       "averageLatency" : 0.0,
       "lastInvocationTime" : 0,
       "workerId" : ""
       }
   } ]
   }