-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Better application deployments in kubernetes #3069
Comments
Hey there, @yairyairyair! 👋 I'm Dosu, a friendly bot here to lend a hand with bugs, answer your questions, and help you get started with contributing while we wait for a human maintainer to join us. I'm diving into your issue about enhancing application deployments in Kubernetes with Dify and will get back to you with a comprehensive response shortly. Hang tight! |
I think this will also GREATLY improve the cloud experience too if my dify.ai app in the cloud will have higher availability and auto-scaling capabilities (might even be cheaper if can scale to zero 0) |
To enhance Dify's deployment process within Kubernetes and deploy each app as a separate Kubernetes deployment, you can follow a structured approach to improve scalability, resilience, and the cloud experience. This involves creating a Kubernetes deployment for each application, defining services and ingress for external accessibility, implementing auto-scaling, and ensuring the setup remains functional even if Dify is removed.
These steps are a general guide and may require adjustments based on your specific environment and use case. If you have further questions or need assistance, feel free to ask. Sources
|
Please refer this link #2931 about use helm to deploy dify.ai |
Self Checks
1. Is this request related to a challenge you're experiencing?
yes
2. Describe the feature you'd like to see
would like a better app deployment when i am running dify in kubernetes.
i want the app to be deployed separately in a different kubernetes deployment.
this can be done via CRD or via knative or via whatever.
i mean that when i am publishing an app dify.ai will create a new kubernetes deployment with service and ingress and i can access it via the same URL and embed it but it will be a separate entity that even if i remove dify.ai (helm uninstall) the app will still run and can also scale and all of the kubernetes advantages.
3. How will this feature improve your workflow or experience?
it will greatly improve scalability and resiliience of dify.ai apps.
4. Additional context or comments
No response
5. Can you help us with this feature?
The text was updated successfully, but these errors were encountered: