Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] add initial helm chart #14

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

akihikokuroda
Copy link

Create helm chart to install bee-stack in kubernetes cluster.

The bee-api, bee-ui and bee-observ are in the main chart and the other dependency components are in the sub charts.

Necessary tools are:

  1. kubernetes cluster. (kind, RancherDesctop, etc)
  2. kubectl
  3. helm

Install step:

  1. cd to charts/bee-stack
  2. run helm dependency update
  3. run 'helm install "release name" .`

The stack is install in the default namespace.

uninstall step:

  1. run 'helm uninstall "release name"`
  2. run kubectl delete pvc for an necessary PVC.

@akihikokuroda akihikokuroda marked this pull request as draft October 30, 2024 21:06
@akihikokuroda
Copy link
Author

This is still in progress. It has all components except "the python interpreter". The components are up but not working properly yet.

Any comments and suggestions are welcome.
Thanks!

@akihikokuroda
Copy link
Author

With the latest commit, most of components are working except the "python-interpreter". The bee-ui and the 'mlflow` are accessible via node ports. After install the bee-stack helm chart by
``
cd charts/bee-stack
helm install bee .

The ui can be accessed

kubectl get svc bee-stack-ui bee-mlflow-tracking
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
bee-stack-ui NodePort 10.43.204.200 3000:30995/TCP 17m
bee-mlflow-tracking LoadBalancer 10.43.144.32 192.168.4.181 80:32605/TCP 17m

URL for bee-ui: `http://localhost:30995/`
URL for mlflow: `http://localhost:32605/`


The next steps are:

1. add python-interpreter
2. extract secret information from deployments and put them into secrets.

@jezekra1
Copy link
Collaborator

jezekra1 commented Nov 4, 2024

Thanks for the draft!

We should make the helm chart suitable for production deployment, see the necessary changes in the issue:
#2 (comment)

I'll implement the changes, we'll maintain the current docker-compose stack until then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants