Updated Chart for IoT Agents

[SBlechmann]

Hey @c0c0n3 and @chicco785 ,

I was just wondering if you could maybe help us out here? We are moving towards k8s and are struggeling with the IoTA-Json and MongoDB.
We have described the problem here as well.

I appreciate your time :)

Cheers,
Sebastian

[chicco785]

Hey @c0c0n3 and @chicco785 ,

I was just wondering if you could maybe help us out here? We are moving towards k8s and are struggeling with the IoTA-Json and MongoDB. We have described the problem here as well.

I appreciate your time :)

Cheers, Sebastian

Hi @SBlechmann I am no more working at Martel, hopefully @c0c0n3 can help out! (How are you Andrea? Hope all good!)

[c0c0n3]

How are you Andrea? Hope all good!

Hi! swamped w/ work but all good otherwise :-)

It looks like the config path has changed:

• Helm charts for IoT Agent JSON with more recent versions (e.g. >= 1.19) FIWARE/helm-charts#220 (comment)

So the mount point in our chart should change accordingly I think:

• https://github.com/orchestracities/charts/blob/master/charts/iot-agent/templates/deployment.yaml#L67

We don't have dev cycles to maintain these charts at the moment, but we welcome contribs :-)

Keep in mind if what I mentioned above is the cause of your problem (I didn't have the time to actually test!), then an easy way around that which doesn't require changing the chart would be to apply a Kustomize patch after the chart is inflated in your deployment process---e.g. as part of an Argo CD deployment. We have some examples of how to do that here:

• https://github.com/c0c0n3/anubis.deployment#yaml-pipeline-concept
• https://github.com/c0c0n3/anubis.deployment/blob/main/k8s/apps/orion.oc/kustomization.yaml

[SBlechmann]

I'll have a look, thanks, Andrea!

[c0c0n3]

pleasure!

[SBlechmann]

Hey Andrea,

we have changed the mount path in our test setup (iota-json versions 1.19.0 and 2.4.2). With both versions, the iota seems to connect to mongodb successfully. We have deployed a simple sensor and a simple actuator to validate the correct data flows (via MQTT).
Thanks for your suggestion!
We suggest to update to a newer iota version --> which one do you prefer? We can come up with a PR afterwards.

Cheers,
Sebastian

[c0c0n3]

the iota seems to connect to mongodb successfully

glad you managed to make it work!

We suggest to update to a newer iota version --> which one do you prefer?

The one version you tested with would be best I think?

We can come up with a PR afterwards.

That'd be fan-tas-tic!

[jorgesanmartin]

Hi,
we came up with the same issue and we created some workarounds. However it would be great if this issue is solved. As far as I checked there is no PR to solve it yet. Can we provide a PR from our side? Adding new value and apply in the deployment (volumeMounts section) should be enough, right?

[c0c0n3]

hi @jorgesanmartin :-)

Can we provide a PR from our side?

Sure, thanks sooo much!!

Adding new value and apply in the deployment (volumeMounts section) should be enough, right?

Yep, you should change the mount paths as I mentioned earlier. Also if you could please change the default agent versions, e.g.

• https://github.com/orchestracities/charts/blob/master/charts/iot-agent/values.yaml#L7

to something more recent and add a notice in the chart docs to say we don't support anymore versions older than 1.19.

Thanks again!