Cannot use RELEASE_2 from tools like ArgoCD because the Chart.lock has not been updated.

I saw in a recent commit the Chart.lock was deleted. Another fix would be to update it.

RELEASE_2 with current Chart.lock

> helm dependency build
Error: the lock file (Chart.lock) is out of sync with the dependencies file (Chart.yaml). Please update the dependencies

RELEASE_2 with updated Chart.lock

> helm dependency update
...
...

> git diff
-digest: sha256:3e52943d17ce8ebe3433685e4a4ba8e63c5c0b7a82ac0d1f7a8bf45e3ced52d4
-generated: "2022-03-28T19:56:16.202347259+03:00"
+digest: sha256:ffaa808dd28e31818ee28fedd36b6ec1868cb039f6e3d9159a83acbc0ff02f78
+generated: "2022-05-31T11:26:08.017351+03:00"

Any chance you can make a new release, either from the current main branch (with deleted Chart.lock) or simply update it?

opswat/metadefendercore-debian:5.2.1
mdcore setup in EKS 1.21, Aurora Postgres 12.11

Everything is setup and working - logs show mdcore successfully init the db, activated, and pulled AV defs.

Trying to login to console with the admin user in the ignition file - logs show a successful attempt but console fails with invalid credentials

[INFO ] 2022.09.20 20:45:39.175: (common.workflow) Successful login, validatedUserName='LOCAL/admin', IP='*.*.*.*' [msgid: 1834]

Is there a setting required to allow console logins?

The activation-manager sidecar does not have default resource requests/limits and configuring them means copying the entire activation-manager sidecar block.

Would be great if this could be configurable or at least come with some defaults, as deploying any containers without limits is a bad idea.

Hi team,

Our worker node groups currently is using ARM chip (we're using EKS, instance type a1.4xlarge). After deploying mdcore, pods couldn't start up (CrashLoopBackOff error). But when using Intel chip instance type (c5.2xlarge), mdcore can run normally.

Please help us to run it on ARM chip, or can you please let us know whenever MDCore supports ARM architecture?

Thank you so much!

the setup works and deploys succesfully - however the activationmanager seems to have an issue with your script