edgexfoundry / edgexfoundry/edgex-helm

helm deployment: Upgrade helm chart to use standard conventions for settings

Open
#14 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

Helm charts are not following standard helm chart conventions. For example:

## imagePullSecets

(from cert-manager)

```
{{- with .Values.global.imagePullSecrets }}
imagePullSecrets:
{{- toYaml . | nindent 2 }}
{{- end }}
```

## storageClassName

Specify storage class for PVC's

## nodeSelector (map)

Inject into pods to control placement based on key-value pairs.
e.g. https://artifacthub.io/packages/helm/rook/rook-ceph?modal=values

## tolerations

Ability to schedule against a taint

Contributor guide

Open the contributing guide

Research direction

Start by inspecting the Helm chart templates and values for imagePullSecrets, PVC storageClassName, nodeSelector, and tolerations. Compare the existing conventions with the cert-manager and Rook examples linked in the issue. Done means the chart supports these settings using standard Helm conventions and applies them to the relevant workloads.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm
Domain
devops, infrastructure
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.