device-agent: helm chart for deployment in kubernetes

[andreikop]

Description

Despite device agents were designed for hardware devices, there are useful real life scenarios to run flow instances on Kubernetes. i.e.

• for flowforge development purposes
• to scale running flow
• to achieve high availability with multiple running flow instances
• to have more flexibility in running flow instance configuration, than FlowForge UI supports (custom Ingress settings, service accounts, scaling, secrets and configuration maps, ...)

The Helm was tested on Azure and AWS K8S, therefore providing custom values.yaml for this vendors which can be used with slight edits.

Related Issue(s)

Checklist

• I have read the contribution guidelines
• Suitable unit/system level tests have been added and they pass
• Documentation has been updated
  • Upgrade instructions
  • Configuration details
  • Concepts
• Changes flowforge.yml?
  • Issue/PR raised on flowforge/helm to update ConfigMap Template
  • Issue/PR raised on flowforge/CloudProject to update values for Staging/Production

Labels

• Backport needed? -> add the backport label
• Includes a DB migration? -> add the area:migration label

[hardillb]

This PR will need some thought.

We are working on adding scaling to the "Cloud" instances already so this might not be the right approach.

We will review in the 1.7.0 release period.

[hardillb]

@MarianRaphael FYI