Schedule
Last updated
Last updated
Schedule message event publishing node
Nats cluster needs to enable JetStream
Services and applications should work together the same nats tenant
Each node defines a NODE name that is unique, through which Schedule will be assigned to the node
The principle of the Schedule service is to publish the job message sync up to the worker node cluster. Multi-node can improve the number of tasks and disaster recovery.
The main container image is:
ghcr.io/weplanx/schedule:latest
registry.cn-shenzhen.aliyuncs.com/weplanx/schedule:latest
The case will use Kubernetes deployment orchestration, replicate deployment (modify as needed).
Working mode, default debug
Node name
Nats connection host, use ,
split
Nats NKEY authentication
The client end for managing Schedule configuration, installed in the application: