Ivan

> Interesting find @mariusziemke. Can anyone else confirm upgrading to node 15 works for them as well? We tried Node 16 and it also works...

Completely supporting the major version upgrade. Our team doesn't mind spending some time adjusting code to the new API, as long as we can stop using deprecated or regularly vulnerable...

Hey @a8m is it possible to merge this change in? I also have a good use-case for using concurrent index creation!

@AlexMesser conceptually yes, but it doesn't work - as mentioned here and in #9233 using `enumName` causes TypeORM to generate pointless migrations every time that rename the enum, create the...

Hey @JorritSalverda Are you deploying the snyk-monitor in a non-default namespace? How does your current two-chart deployment process look like? I would imagine you would need to create the namespace...

Hey @phyzical, have you also ensured to set the `fsGroup` and "projected service account token` as described in https://github.com/snyk/kubernetes-monitor/tree/staging/snyk-monitor#using-eks-without-assigning-an-iam-role-to-a-node-group?

Hey @jdomeracki did you need to add any additional steps e.g. add a label or annotation to the ServiceAccount of the snyk-monitor, so that it is provisioned with the correct...

Hey @odidev, if you're building ARM images I assume you would also want to run them in a cluster with ARM worker nodes? Currently the Monitor is not inspecting the...

Hey @odidev is the request for running on Apple M1? Because I know the solution to this and it won't require building separate ARM images. Or do you have a...

Hey @JorritSalverda You can create your own ConfigMap with the custom rules that you need, then when installing with Helm you can point to your ConfigMap with [--set workloadPoliciesMap=my-custom-rules](https://github.com/snyk/kubernetes-monitor/blob/staging/snyk-monitor/values.yaml#L11-L13) `policyOrgs`...