edgexfoundry / edgexfoundry/edgex-helm

helm deployment: Create EdgeX operator for Kubernetes

Open
#1 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Mustache
Stars
7
Forks
8
PR merge metrics
No merged PRs in 30d

Description

# 🚀 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.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.