Duplicate istio.hardened keys in chart/values.yaml

Bug

Description

When tested with Istio hardened, we noticed that the outbound traffic policy mode REGISTRY_ONLY was not getting applied in the gitlab-runner namespace. This was due to the duplicate istio.hardened keys in chart/values.yaml.

Here is a patch to fix the issue:

diff --git a/chart/values.yaml b/chart/values.yaml
index aef09b1..01d516f 100644
--- a/chart/values.yaml
+++ b/chart/values.yaml
@@ -810,30 +810,28 @@ extraObjects: []
 istio:
   # Toggle istio integration
   enabled: false
-  hardened:
-    enabled: false
-    outboundTrafficPolicyMode: "REGISTRY_ONLY"
-    customServiceEntries: []
-      # - name: "allow-google"
-      #   enabled: true
-      #   spec:
-      #     exportTo:
-      #       - "."
-      #     hosts:
-      #       - google.com
-      #     location: MESH_EXTERNAL
-      #     ports:
-      #       - number: 443
-      #         protocol: TLS
-      #         name: https
-      #     resolution: DNS
   injection: disabled
   hardened:
     enabled: false
+    outboundTrafficPolicyMode: "REGISTRY_ONLY"
     customAuthorizationPolicies: []
     # - name: "allow-nothing"
     #   enabled: true
     #   spec: {}
+    customServiceEntries: []
+    # - name: "allow-google"
+    #   enabled: true
+    #   spec:
+    #     exportTo:
+    #       - "."
+    #     hosts:
+    #       - google.com
+    #     location: MESH_EXTERNAL
+    #     ports:
+    #       - number: 443
+    #         protocol: TLS
+    #         name: https
+    #     resolution: DNS
     gitlab:
       enabled: true
       namespaces:

BigBang Version

What version of BigBang were you running?

2.28.1