From 62c97afb5de3cf037b6de6fc2b41bd3877cc249a Mon Sep 17 00:00:00 2001
From: Darlington Kofa <darlington@lidonation.com>
Date: Sun, 29 Dec 2024 09:15:37 +0300
Subject: [PATCH] cleanup

---
 chart/values.postgresql.yaml | 20 +-------------------
 1 file changed, 1 insertion(+), 19 deletions(-)

diff --git a/chart/values.postgresql.yaml b/chart/values.postgresql.yaml
index aa4701b7..d5b2f401 100644
--- a/chart/values.postgresql.yaml
+++ b/chart/values.postgresql.yaml
@@ -1084,25 +1084,7 @@ volumePermissions:
   ## @param volumePermissions.enabled Enable init container that changes the owner and group of the persistent volume
   ##
   enabled: true
-  ## @param volumePermissions.image.registry Init container volume-permissions image registry
-  ## @param volumePermissions.image.repository Init container volume-permissions image repository
-  ## @param volumePermissions.image.tag Init container volume-permissions image tag (immutable tags are recommended)
-  ## @param volumePermissions.image.pullPolicy Init container volume-permissions image pull policy
-  ## @param volumePermissions.image.pullSecrets Init container volume-permissions image pull secrets
-  ##
-  image:
-    registry: docker.io
-    repository: bitnami/bitnami-shell
-    tag: 11-debian-11-r93
-    pullPolicy: IfNotPresent
-    ## Optionally specify an array of imagePullSecrets.
-    ## Secrets must be manually created in the namespace.
-    ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
-    ## Example:
-    ## pullSecrets:
-    ##   - myRegistryKeySecretName
-    ##
-    pullSecrets: []
+
   ## Init container resource requests and limits
   ## ref: https://kubernetes.io/docs/user-guide/compute-resources/
   ## @param volumePermissions.resources.limits Init container volume-permissions resource limits
-- 
GitLab