Fix podDisruptionBudget default values (#121)

* Update values.yaml

By default, you can only have one or the other. If both are set then we get the following error: 

EXIT STATUS
  1
 
COMBINED OUTPUT:
  Error: UPGRADE FAILED: release opentelemetry-collector failed, and has been rolled back due to atomic being set: failed to create resource: PodDisruptionBudget.policy "opentelemetry-collector" is invalid: spec: Invalid value: policy.PodDisruptionBudgetSpec{MinAvailable:(*intstr.IntOrString)(0xc045b8be40), Selector:(*v1.LabelSelector)(0xc045b8be60), MaxUnavailable:(*intstr.IntOrString)(0xc045b8be20)}: minAvailable and maxUnavailable cannot be both set

charts/opentelemetry-collector/Chart.yaml

@@ -1,6 +1,6 @@
 apiVersion: v2
 name: opentelemetry-collector
-version: 0.9.0
+version: 0.9.1
 description: OpenTelemetry Collector Helm chart for Kubernetes
 type: application
 home: https://opentelemetry.io/

charts/opentelemetry-collector/templates/pdb.yaml

@@ -6,8 +6,12 @@ metadata:
   labels:
     {{- include "opentelemetry-collector.labels" . | nindent 4 }}
 spec:
+  {{- if .Values.podDisruptionBudget.minAvailable }}
   minAvailable: {{ .Values.podDisruptionBudget.minAvailable }}
+  {{- end  }}
+  {{- if .Values.podDisruptionBudget.maxUnavailable }}
   maxUnavailable: {{ .Values.podDisruptionBudget.maxUnavailable }}
+  {{- end  }}
   selector:
     matchLabels:
       {{- include "opentelemetry-collector.selectorLabels" . | nindent 6 }}

charts/opentelemetry-collector/values.yaml

@@ -330,8 +330,8 @@ serviceMonitor:
 # PodDisruptionBudget is used only if standaloneCollector enabled
 podDisruptionBudget:
   enabled: false
-  minAvailable: 2
-  maxUnavailable: 1
+#   minAvailable: 2
+#   maxUnavailable: 1
 
 # autoscaling is used only if standaloneCollector enabled
 autoscaling: