policy

Saw this rule in the clj-kondo linter, and I think it would be a good addition to our strict mode. Having duplicate elements in sets is probably always a mistake in a production policy, and while it's "harmless", the intent is likely to provide another element rather than the duplicate, leading to an unexpected

Is your feature request related to a problem? Please describe.
the file pkg/defaultRules/defaultRules.yaml is used by our backend as well as the cli itself. Moving it can result in a failure in getting the file for creating new policies in the dashboard

Describe the solution you'd like
Add a step in the ci the verifies that the file pkg/defaultRules/defaultRules.yaml exists (in th

See https://github.blog/2022-05-09-supercharging-github-actions-with-job-summaries/

Instead of (or in addition to) posting a comment on the PR, we could generate a nice looking summary by emitting the Markdown content.

Describe the bug
No easy way of setting .env
OPAL uses decouple to parse configuration from .env and .ini files (As part of Confi)
BY default it looks for them in the folder of the importing module - we should add support for a configurable folder or at least the current-directory

Feature Request

Short Description

Currently, the GRPC server port [is a configuration](https://github.com/kubearmor/KubeArmor/blob/bf39613c0c01e986d3e77d2f46a59c526cbf5907/KubeArmor/config/config.go#L79) and the default value is 32767.
This works fine on kubearmor in

The repository for the helmfile project is changed from https://github.com/roboll/helmfile to https://github.com/helmfile/helmfile.
This PR changes the URL in e2e/README.md to reflect this change.

There is still a reference to the old repository in .github/workflows/e2e.yaml:36. This reference must be updated after there is a release present in