Helm deployment of EdgeX takes a very very long time to finish, especially with lots of services to start. Helm chart tends to start them in the wrong order, causing lots of retries.
Describe the solution you'd like
Consider creating an EdgeX operator that programmatically instantiates EdgeX components in the proper order, so that less CPU is spent spinning up containers that will ultimately fail and have to be restarted.
Describe alternatives you've considered
Kubernetes has a cluster priority option, but must be a cluster admin to use it, and it is global to the cluster rather than being namespaced. Don't think its a good idea.
🚀 Feature Request
Relevant Package [REQUIRED]
helm deployment scripts
Description [REQUIRED]
Helm deployment of EdgeX takes a very very long time to finish, especially with lots of services to start. Helm chart tends to start them in the wrong order, causing lots of retries.
Describe the solution you'd like
Consider creating an EdgeX operator that programmatically instantiates EdgeX components in the proper order, so that less CPU is spent spinning up containers that will ultimately fail and have to be restarted.
Describe alternatives you've considered
Kubernetes has a cluster priority option, but must be a cluster admin to use it, and it is global to the cluster rather than being namespaced. Don't think its a good idea.