Comments (5)
Are you on Linux?
@nicoloboschi can you please take a look?
from langstream.
Yup, linux, running Ubuntu 22.04.3 LTS
(newly setup Azure VM today)
from langstream.
In case it helps, the versions of everything I'm running are:
*Docker:* Docker version 24.0.5, build 24.0.5-0ubuntu1~22.04.1
*Minikube:* minikube version: v1.31.2
*Helm:* version.BuildInfo{Version:"v3.13.1", GitCommit:"3547a4b5bf5edb5478ce352e18858d8a552a4110", GitTreeState:"clean", GoVersion:"go1.20.8"}
*KubeCtl:* Client Version: v1.28.3, Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
*Ubuntu:* Ubuntu 22.04.3 LTS
*LangStream:* LangStream CLI 0.4.2
*Mini LangStream:* 0.4.2
Running the wrapped minikube we see no node ports setup for the langstream services, but ingress is enabled in general
KUBECONFIG=.mini-langstream/data/kube-config minikube --profile mini-langstream service list
|---------------|------------------------------------|--------------|---------------------------|
| NAMESPACE | NAME | TARGET PORT | URL |
|---------------|------------------------------------|--------------|---------------------------|
| default | kubernetes | No node port | |
| ingress-nginx | ingress-nginx-controller | http/80 | http://192.168.49.2:30413 |
| | | https/443 | http://192.168.49.2:32229 |
| ingress-nginx | ingress-nginx-controller-admission | No node port | |
| kube-system | kube-dns | No node port | |
| langstream | langstream-api-gateway | No node port | |
| langstream | langstream-control-plane | No node port | |
|---------------|------------------------------------|--------------|---------------------------|
from langstream.
From my investigations so far, it does seem like helm isn't setting up the external node port that the script is expecting
I'm still not sure if there's an issue with the latest helm script, the minikube env needs extra services adding that full k8s doesn't, there should be a fallback via the ingress (which is setup fine), or something else!
I have at least got a proposed patch that will detect when this has happened and error out, rather than hanging, which is a start...
from langstream.
Since the Helm charts are shared between the Mini-Langstream case and more "production" deployments, I'm not sure if it's a good idea to define a target port on the k8s service definition in the helm chart as standard. Doing that would make it harder for people using other approaches (eg ingress or gateway) to override things for their own use
I've seen a few other projects setup their helm charts to support a few different modes for allowing access, which can be toggled between, but that might be an overkill.
I'm tempted to have mini-langstream check to see if external access has already been enabled (as now), and if not send in a short bit of yaml to k8s to setup a NodePort. That way, the helm charts don't have to change, anyone doing their own custom config continues as now, but the mini-langstream case gets a sensible clean setup (without the complexity of a full ingress setup, or the brittleness of kubectl port forwards).
Thoughts?
from langstream.
Related Issues (20)
- mini-langstream getting started (deploy sample app) fails with: Missing required option: '--instance=<instanceFilePath>'
- mini-langstream start suggestion fails to deploy due to incorrect path
- [Feature request] Add more automatic configuration for LangChain LLMs for Python processors HOT 2
- [Feature request] Toggle for showing credentials in log
- langstream apps deploy should provide more beginner friendly help if it can't connect to annot connect to http://localhost:8090/api/applications/ HOT 1
- java.lang.RuntimeException: Missing some input keys: {'query'} for source record KafkaRecord.KafkaConsumerRecord HOT 8
- LangStream pipeline UI has disconnect when LangChain is used
- LangStream has no Windows support HOT 1
- PGVector as vector db HOT 2
- ProduceConsumeHandlerTest.testSendEvents is flaky
- write-to-astra sink to support JSON API HOT 2
- Langstream does not work on windows. HOT 1
- redirection to a forbidden domain happened without slash suffix character in the web crawler HOT 1
- Provisioned disks for custom agent permission denied HOT 3
- RESOURCE_EXHAUSTED in python-source agent HOT 8
- Allow runtime upgrade of existing applications HOT 1
- Copy artifacts into the container before compiling
- langstream python run-tests should quote all arguments
- Support GPU in Kubernetes cluster
- SimpleHeader values not decoding properly in log-event agent
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from langstream.