Fix kong postgres init container storage permissions

Postgres container runs for kong fails with the permission issue.
This provides elevated permissions for the init container alone to complete the volume permission changes.

Issue-ID: NONRTRIC-1020
Change-Id: If6313e1ed9b98c26874c8fb767b053d2131dc7a1
Signed-off-by: aravind.est <aravindhan.a@est.tech>

diff --git a/nonrtric/helm/kongstorage/kongvalues.yaml b/nonrtric/helm/kongstorage/kongvalues.yaml
index c6fff53..a1ca552 100644 (file)
--- a/nonrtric/helm/kongstorage/kongvalues.yaml
+++ b/nonrtric/helm/kongstorage/kongvalues.yaml
@@ -1,6 +1,6 @@
 
 #  ============LICENSE_START===============================================
-#  Copyright (C) 2024 OpenInfra Foundation Europe. All rights reserved.
+#  Copyright (C) 2024-2025 OpenInfra Foundation Europe. All rights reserved.
 #  ========================================================================
 #  Licensed under the Apache License, Version 2.0 (the "License");
 #  you may not use this file except in compliance with the License.
@@ -118,6 +118,9 @@ postgresql:
       postgresql: "5432"
   volumePermissions:
     enabled: true
+    # This provides permission for the initcontainer to set the correct permissions
+    containerSecurityContext:
+      runAsNonRoot: false
   primary:
     persistence:
       existingClaim: kongpvc