[stable/efs-provisioner] Add support for priorityClasses (#10278)

* [stable/efs-provisioner] Add support for priorityClasses

Signed-off-by: Art3mK <artem@kayalaynen.ru>

* feat(deployment): disable deployment with default efsFileSystemId to prevent CI test failuersi

Signed-off-by: Art3mK <artem@kayalaynen.ru>
This commit is contained in:
Art3mK
2019-01-04 15:31:57 -08:00
committed by Kubernetes Prow Robot
parent 6960e32d98
commit 6dca7f0ed5
3 changed files with 18 additions and 1 deletions
+1 -1
View File
@@ -1,7 +1,7 @@
apiVersion: v1
name: efs-provisioner
description: A Helm chart for the AWS EFS external storage provisioner
version: 0.1.1
version: 0.1.2
appVersion: v0.1.2
home: https://github.com/kubernetes-incubator/external-storage/tree/master/aws/efs
sources:
@@ -1,3 +1,14 @@
{{- if ne .Values.efsProvisioner.efsFileSystemId "fs-12345678" }}
{{/*
The `efsFileSystemId` value must be set.
The above `if` condition also prevents the helm integration tests from failing.
Given that the helm test infrastructure does not have access to valid
AWS EFS resources, a deployment that references the example `fs-12345678`
creates pods that will never enter a clean, running state.
Omitting the deployment hacks around this limitation.
*/}}
kind: Deployment
apiVersion: apps/v1beta2
metadata:
@@ -24,6 +35,9 @@ spec:
release: "{{ .Release.Name }}"
spec:
serviceAccount: {{ template "efs-provisioner.serviceAccountName" . }}
{{- if .Values.priorityClassName }}
priorityClassName: "{{ .Values.priorityClassName }}"
{{- end }}
containers:
- name: {{ template "efs-provisioner.fullname" . }}
image: "{{ .Values.image.repository }}:{{ .Values.image.tag }}"
@@ -54,3 +68,4 @@ spec:
nfs:
server: {{ .Values.efsProvisioner.efsFileSystemId }}.efs.{{ .Values.efsProvisioner.awsRegion }}.amazonaws.com
path: /
{{- end }}
+2
View File
@@ -65,3 +65,5 @@ resources: {}
# requests:
# cpu: 100m
# memory: 128Mi
priorityClassName: ""