Bump Twistlock for defenders NP template & values

Package Owner Merge Request

Package Changes

• New networkPolicies.nodeCidr value in package to set CIDR notation for kubernetes nodes (so defenders hostNetwork traffic can talk to twistlock-console k8s service).

• New Network Policy resource to allow communication of Twistlock Defenders pods to twistlock-console k8s service.

https://repo1.dso.mil/platform-one/big-bang/apps/security-tools/twistlock/-/merge_requests/33

https://repo1.dso.mil/platform-one/big-bang/apps/security-tools/twistlock/-/tags/0.0.9-bb.0

Additional Details

Probably need discussion around including a new BigBang level value concerning the above package value networkPolicies.nodeCidr. The following private Networks are allowed by default "10.0.0.0/8" "172.16.0.0/12" "192.168.0.0/16" "100.64.0.0/10" so there is very small chance that someone would need to set value.

Closes #721 (closed)

chart/values.yaml

@@ -101,6 +101,10 @@ networkPolicies:
   # Must be an IP CIDR range (x.x.x.x/x - ideally with /32 for the specific IP of a single endpoint, broader range for multiple masters/endpoints)
   # Used by package NetworkPolicies to allow Kube API access
   controlPlaneCidr: 0.0.0.0/0
+  # -- Node CIDR, defaults to allowing "10.0.0.0/8" "172.16.0.0/12" "192.168.0.0/16" "100.64.0.0/10" networks.
+  # use `kubectl get nodes -owide` and review the `INTERNAL-IP` column to derive CIDR range.
+  # Must be an IP CIDR range (x.x.x.x/x - ideally a /16 or /24 to include multiple IPs)
+  nodeCidr: ""
 
 # ----------------------------------------------------------------------------------------------------------------------
 # Istio