Browse Source

Remove podDisruptionBudget configuration

Waqar Ahmed 5 years ago
parent
commit
36f7e7a497
2 changed files with 0 additions and 20 deletions
  1. 0 13
      test/minio/8.0.5/templates/poddisruptionbudget.yaml
  2. 0 7
      test/minio/8.0.5/values.yaml

+ 0 - 13
test/minio/8.0.5/templates/poddisruptionbudget.yaml

@@ -1,13 +0,0 @@
-{{- if .Values.podDisruptionBudget.enabled }}
-apiVersion: policy/v1beta1
-kind: PodDisruptionBudget
-metadata:
-  name: minio
-  labels:
-    app: {{ template "minio.name" . }}
-spec:
-  maxUnavailable: {{ .Values.podDisruptionBudget.maxUnavailable }}
-  selector:
-    matchLabels:
-      app: {{ template "minio.name" . }}
-{{- end }}

+ 0 - 7
test/minio/8.0.5/values.yaml

@@ -191,13 +191,6 @@ networkPolicy:
   enabled: false
   allowExternal: true
 
-## PodDisruptionBudget settings
-## ref: https://kubernetes.io/docs/concepts/workloads/pods/disruptions/
-##
-podDisruptionBudget:
-  enabled: false
-  maxUnavailable: 1
-
 ## Specify the service account to use for the Minio pods. If 'create' is set to 'false'
 ## and 'name' is left unspecified, the account 'default' will be used.
 serviceAccount: