☂ Implement Security Hardened Kubernetes Cluster ruleset

[AleksandarSavchev]

What would you like to be added:
DISA Kubernetes Security Technical Implementation Guide should be extended with a new ruleset Security Hardened Kubernetes Cluster which aims to additionally increase the security posture of a Kubernetes cluster. Thos ruleset should be added to the managedk8s provider.

• Add Security Hardened Kubernetes Cluster ruleset guide Add Security Hardened Kubernetes Cluster ruleset version v0.1.0 #342
• Add Security Hardened Kubernetes Cluster ruleset to managedk8s provider Add Security Hardened Kubernetes Cluster ruleset to managedk8s provider #359
• Implement Rules
  • 2000 Ingress and egress traffic must be restricted by default. [Security Hardened Kubernetes Cluster] Rule 2000 implementation #383
  • 2001 Containers must be forbidden to escalate privileges. [Security Hardened Kubernetes Cluster] Rule 2001 implementation #375
  • 2002 Storage Classes should have a "Delete" reclaim policy. [Security Hardened Kubernetes Cluster] Rule 2002 implementation  #387
  • 2003 Pods should use only allowed volume types.
  • 2004 Limit the Services of type NodePort. [Security Hardened Kubernetes Cluster] Rule 2004 implementation #376
  • 2005 Container images must come from trusted repositories. [Security Hardened Kubernetes Cluster] Rule 2005 implementation #380
  • 2006 Limit the use of wildcards in RBAC resources. [Security Hardened Kubernetes Cluster] Rule 2006 implementation #382
  • 2007 Limit the use of wildcards in RBAC verbs. [Security Hardened Kubernetes Cluster] Rule 2007 implementation #389
  • 2008 Pods must not be allowed to mount host directories. [Security Hardened Kubernetes Cluster] Rule 2008 implementation #371
• Add new usage documentation for running the Security Hardened Kubernetes Cluster ruleset