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

Feat/multi node support #96

Merged
merged 26 commits into from
May 26, 2024
Merged

Feat/multi node support #96

merged 26 commits into from
May 26, 2024

Conversation

Siumauricio
Copy link
Contributor

@Siumauricio Siumauricio commented May 19, 2024

Close #1

To try out this feature you can use curl -sSL https://dokploy.com/feature.sh | sh

Features:

Server

  • Prevent to automatically download the newest version this to prevent unexpected behaviors

Registry:

  • Add self hosted registry
  • Add external registry (Dockerhub, DO Containers, etc.)

Cluster:

  • Add Nodes (Workers, Managers)
  • Remove Nodes

Users:

  • The users now are displayed in a table to have more control and easy usage

Application:

  • Add replicas customization
  • Select registry to upload the image
  • Swarm Settings (Update Multiples Docker properties trought JSON (HealthCheck, RestartPolicy, Placement, UpdateConfig, ServiceMode, Network,Labels) we validate each JSON to prevent to insert invalid data

How to test this?

  1. Create 2 servers ( The leader which is where dokploy is running, the second is the worker)
  2. Run the command on a fresh server
  3. Enable a self hosted registry
  4. Add a node and follow the instructions
  5. Fork this repository in your github account https://github.com/Dokploy/swarm-test
  6. Create an application then select the repository (Don't forget to add a domain to test this)
  7. Go to advanced tab and then in replicas set 2 and select the registry you've created
  8. Click on Deploy and automatically the load will be balanced by traefik

Screenshot 2024-05-18 at 6 19 40 PM

Screenshot 2024-05-18 at 6 20 35 PM

Screenshot 2024-05-18 at 6 20 48 PM

See how the ID changes, that means the load balanced is selecting the manager instance or the worker instance

Screen.Recording.2024-05-18.at.6.22.57.PM.mov

@Siumauricio Siumauricio linked an issue May 19, 2024 that may be closed by this pull request
@Siumauricio Siumauricio requested a review from hehehai May 19, 2024 04:40
@Siumauricio Siumauricio marked this pull request as ready for review May 19, 2024 17:01
@hehehai
Copy link
Contributor

hehehai commented May 20, 2024

@Siumauricio That's amazing! Great job! 👍

@Siumauricio Siumauricio requested a review from hehehai May 26, 2024 09:10
@Siumauricio Siumauricio merged commit ed6e4e8 into canary May 26, 2024
2 checks passed
@Siumauricio Siumauricio deleted the feat/multi-node-support branch May 26, 2024 09:13
This was referenced May 30, 2024
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.

Feature request: multi node support
2 participants