Feature: Support for SealOS Deployment with K8S Helm Charts in OpenIM v3.5 (Post MySQL Removal)

[cubxxw]

Checklist

• I've searched for similar issues and couldn't find anything matching
• I've discussed this feature request in the OpenIMSDK Slack and got positive feedback

Is this feature request related to a problem?

✅ Yes

Problem Description

I am following the development of OpenIM and am excited about the upcoming v3.5 release. With the planned changes, especially the removal of the MySQL database, I believe this presents an opportunity to enhance the deployment process. I would like to suggest the integration of SealOS for a more streamlined deployment experience.

Solution Description

• Provide K8S Helm charts for OpenIM v3.5 that are compatible with SealOS, specifically tailored for instances where the MySQL database is removed.
• Ensure that these Helm charts set default values appropriately to facilitate ease of use.
• Optimize the pods to support multiple replicas, enhancing the scalability and robustness of the system.

Benefits

• This integration will simplify the deployment process for users opting for SealOS, making OpenIM more accessible.
• It aligns with the ongoing efforts to optimize OpenIM components, contributing to the system's overall robustness and maintainability.

Potential Drawbacks

• None identified at this stage, but open for discussion and feedback.

Additional Information

• The deployment repository for reference is openimsdk/openim-charts.
• This request is in line with the ongoing developments and the community's needs for more efficient deployment methods.

Looking forward to seeing these enhancements in the upcoming version. Thank you for considering this request.

[cubxxw]

Link #1511

[kubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

Link #1511

[caesar168]

Very good, waiting for good news.

[kubbot]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[kubbot]

This issue was closed because it has been stalled for 7 days with no activity.

[kubbot]

This issue is available for anyone to work on. Make sure to reference this issue in your pull request. ✨ Thank you for your contribution! ✨
Join slack 🤖 to connect and communicate with our developers.
If you wish to accept this assignment, please leave a comment in the comments section: /accept.🎯

[kubbot]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.