feat: Connect with discovery-engine to recommend Kyverno policies

[Vyom-Yadav]

Signed-off-by: Vyom-Yadav jackhammervyom@gmail.com

---

Kyverno policy recommendation is spread across 3 PRs including this one:

• Modify policy template schema for Kyverno policies policy-templates#1037
• feat: Add logic for Kyverno policy recommendation accuknox/discovery-engine#701

---

Explanation:

Unlike other recommended policies, admission controller policies are fetched from Discovery-Engine. The client does not generate any admission controller policies.

Admission controller policies recommendation does not require downloading the images, they can be directly fetched from Discovery Engine.

CLI is extended with another flag for recommend: (-p, --policy)

$ ./karmor recommend --help          
Recommend policies based on container image, k8s manifest or the actual runtime env

Usage:
  karmor recommend [flags]
  karmor recommend [command]

Available Commands:
  update      Updates policy-template cache

Flags:
  -c, --config string      absolute path to image registry configuration file (default "/home/vyom/.docker/config.json")
  -h, --help               help for recommend
  -i, --image strings      Container image list (comma separated)
  -l, --labels strings     User defined labels for policy (comma separated)
  -n, --namespace string   User defined namespace value for policies
  -o, --outdir string      output folder to write policies (default "out")
  -p, --policy strings     Types of policy that can be recommended: KubeArmorPolicy|KyvernoPolicy (comma separated) (default [KyvernoPolicy,KubeArmorPolicy])
  -r, --report string      report file (default "report.txt")
  -t, --tag strings        tags (comma-separated) to apply. Eg. PCI-DSS, MITRE

Global Flags:
      --context string      Name of the kubeconfig context to use
      --kubeconfig string   Path to the kubeconfig file to use

Use "karmor recommend [command] --help" for more information about a command.

Policies are being currently fetched from my fork of policy-templates, change would be required after merging kubearmor/policy-templates#1037.

---

Recommendation Logs: https://gist.github.com/Vyom-Yadav/17d2baf7164c7204a4237b2b3efb88b6

[Vyom-Yadav]

CI failure is due to dependency on updated worker protobuf.

[PrimalPimmy]

LGTM 👍 tested locally

[Vyom-Yadav]

@nyrahul Can you please LGTM if the changes look good?

[nyrahul]

Lgtm