back to home

streamnative / function-mesh

The serverless framework purpose-built for event streaming applications.

View on GitHub
228 stars
30 forks
40 issues

AI Architecture Analysis

This repository is indexed by RepoMind. By analyzing streamnative/function-mesh in our AI interface, you can instantly generate complete architecture diagrams, visualize control flows, and perform automated security audits across the entire codebase.

Our Agentic Context Augmented Generation (Agentic CAG) engine loads full source files into context on-demand, avoiding the fragmentation of traditional RAG systems. Ask questions about the architecture, dependencies, or specific features to see it in action.

Source files are only loaded when you start an analysis to optimize performance.

Embed this Badge

Showcase RepoMind's analysis directly in your repository's README.

[![Analyzed by RepoMind](https://img.shields.io/badge/Analyzed%20by-RepoMind-4F46E5?style=for-the-badge)](https://repomind.in/repo/streamnative/function-mesh)
Preview:Analyzed by RepoMind

Repository Overview (README excerpt)

Crawler view

Function-Mesh A Kubernetes-Native way to run pulsar functions, connectors and composed function meshes. Install The above command installs all the CRDs, required service account configuration, and all function-mesh operator components. Before you start running a function-mesh example, verify if Function Mesh is installed correctly. Note: > install.sh is suitable for trying Function Mesh out. If you want to use Function Mesh in production or other serious scenarios, Helm is the recommended deployment method. Prerequisite • Git • operator-sdk • kubernetes cluster • pulsar-cluster • pulsar-functions Compatibility Kubernetes compatibility matrix This table outlines the supported Kubernetes versions. We have tested these versions in their respective branches. But note that other versions might work as well. | Function Mesh operator | Kubernetes 1.19 | Kubernetes 1.20 | Kubernetes 1.21 | Kubernetes 1.22 | Kubernetes 1.23 | Kubernetes 1.24 | Kubernetes 1.25 | |---------------------------------------------------------------------------------|---------------|--------------|---------------|----------------|-----------------| --------------- | --------------- | | | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | | | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | | | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | | | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | | | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | | | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | | | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | | | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | | | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | | | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | | | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | Development • install Git and download the repo • install operator-sdk and use it to add CRD, controller or webhooks > **Note** > > The following command will generate the scaffolding files in the path, in this case , and then you need to move the files contained in it to the directory manually, in this case . Deployment • make sure connected to a kubernetes cluster(gke, mini-kube etc.) • compile the repo to generate related resources in the root dir of the repo. • install the CRD into your k8s cluster. • start the controller locally. Only the controller itself is running in your local terminal, all the resources will be running inside the connected kubernetes cluster • submit a sample CRD to the cluster. You can also submit other CRDs under the directory • verify your submission with , and you will see the function pod is running • in order for function actually work, you need to have a pulsar cluster available for visiting. you can use the helm-chart to deploy one