2020-04-28 13:49:03 +00:00
|
|
|
apiVersion: v1
|
|
|
|
kind: Service
|
|
|
|
metadata:
|
|
|
|
name: {{ include "rawfile-csi.fullname" . }}-controller
|
|
|
|
labels:
|
|
|
|
{{- include "rawfile-csi.labels" . | nindent 4 }}
|
2020-05-03 14:58:55 +00:00
|
|
|
component: controller
|
2020-04-28 13:49:03 +00:00
|
|
|
spec:
|
|
|
|
type: ClusterIP
|
|
|
|
selector:
|
|
|
|
{{- include "rawfile-csi.selectorLabels" . | nindent 4 }}
|
2020-05-03 14:58:55 +00:00
|
|
|
component: controller
|
2020-04-28 13:49:03 +00:00
|
|
|
clusterIP: None
|
|
|
|
---
|
2020-04-23 13:52:01 +00:00
|
|
|
apiVersion: apps/v1
|
2020-04-28 13:49:03 +00:00
|
|
|
kind: StatefulSet
|
2020-04-23 13:52:01 +00:00
|
|
|
metadata:
|
2020-04-28 13:22:20 +00:00
|
|
|
name: {{ include "rawfile-csi.fullname" . }}-controller
|
2020-04-23 13:52:01 +00:00
|
|
|
spec:
|
|
|
|
replicas: 1
|
2020-04-28 13:49:03 +00:00
|
|
|
serviceName: {{ include "rawfile-csi.fullname" . }}
|
2020-04-23 13:52:01 +00:00
|
|
|
selector:
|
2020-04-28 13:22:20 +00:00
|
|
|
matchLabels: &selectorLabels
|
|
|
|
{{- include "rawfile-csi.selectorLabels" . | nindent 6 }}
|
|
|
|
component: controller
|
2020-04-23 13:52:01 +00:00
|
|
|
template:
|
|
|
|
metadata:
|
2020-04-28 13:22:20 +00:00
|
|
|
labels: *selectorLabels
|
2020-04-23 13:52:01 +00:00
|
|
|
spec:
|
2020-04-28 13:22:20 +00:00
|
|
|
serviceAccount: {{ include "rawfile-csi.fullname" . }}-driver
|
2020-04-23 13:52:01 +00:00
|
|
|
priorityClassName: system-cluster-critical
|
|
|
|
tolerations:
|
|
|
|
- key: "node-role.kubernetes.io/master"
|
|
|
|
operator: Equal
|
|
|
|
value: "true"
|
|
|
|
effect: NoSchedule
|
|
|
|
volumes:
|
|
|
|
- name: socket-dir
|
|
|
|
emptyDir: {}
|
|
|
|
containers:
|
|
|
|
- name: csi-driver
|
2020-04-28 13:22:20 +00:00
|
|
|
image: "{{ .Values.controller.image.repository }}:{{ .Values.controller.image.tag }}"
|
|
|
|
imagePullPolicy: {{ .Values.controller.image.pullPolicy }}
|
2021-07-02 16:00:48 +00:00
|
|
|
args:
|
|
|
|
- csi-driver
|
|
|
|
- --disable-metrics
|
2020-04-23 13:52:01 +00:00
|
|
|
env:
|
2020-08-14 20:54:55 +00:00
|
|
|
- name: PROVISIONER_NAME
|
|
|
|
value: "{{ .Values.provisionerName }}"
|
2020-04-23 13:52:01 +00:00
|
|
|
- name: CSI_ENDPOINT
|
|
|
|
value: unix:///csi/csi.sock
|
2020-05-29 14:50:03 +00:00
|
|
|
- name: IMAGE_REPOSITORY
|
|
|
|
value: "{{ .Values.controller.image.repository }}"
|
2020-06-19 17:38:55 +00:00
|
|
|
{{- if regexMatch "^.*-ci$" .Values.controller.image.tag }}
|
|
|
|
- name: IMAGE_TAG
|
|
|
|
value: "{{ .Values.controller.image.tag }}"
|
|
|
|
{{- end }}
|
2020-04-23 13:52:01 +00:00
|
|
|
volumeMounts:
|
|
|
|
- name: socket-dir
|
|
|
|
mountPath: /csi
|
2020-09-11 16:14:29 +00:00
|
|
|
ports:
|
|
|
|
- name: csi-probe
|
|
|
|
containerPort: 9808
|
2020-04-28 13:22:20 +00:00
|
|
|
resources:
|
|
|
|
{{- toYaml .Values.controller.resources | nindent 12 }}
|
2020-09-11 16:14:29 +00:00
|
|
|
- name: external-provisioner
|
2021-06-29 12:21:28 +00:00
|
|
|
image: k8s.gcr.io/sig-storage/csi-provisioner:v2.2.2
|
2020-04-23 13:52:01 +00:00
|
|
|
imagePullPolicy: IfNotPresent
|
|
|
|
args:
|
|
|
|
- "--csi-address=$(ADDRESS)"
|
|
|
|
- "--feature-gates=Topology=true"
|
|
|
|
- "--strict-topology"
|
2021-08-02 20:32:50 +00:00
|
|
|
- "--timeout=120s"
|
2020-04-23 13:52:01 +00:00
|
|
|
env:
|
|
|
|
- name: ADDRESS
|
|
|
|
value: /csi/csi.sock
|
|
|
|
volumeMounts:
|
|
|
|
- name: socket-dir
|
|
|
|
mountPath: /csi
|
2020-09-11 16:14:29 +00:00
|
|
|
- name: external-resizer
|
2021-06-29 12:21:28 +00:00
|
|
|
image: k8s.gcr.io/sig-storage/csi-resizer:v1.2.0
|
Support online volume expansion
Summary:
Online volume expansion is a 2 phase process:
1. The backing storage, in this case the raw file, needs to be resized. (i.e. `truncate -s`)
2. The node should be notified, so that it can both refresh its device capacity (i.e. `losetup -c`) and resize the filesystem (`resize2fs`) accordingly.
Although in our case both steps could be performed on the node itself, for the sake of following the semantics of how volume expansion works, we perform step 1 from the controller, and step 2 from the node.
Also, the `external-resizer` component is added which watches for PVC size updates, and notifies the CSI controller about it.
Test Plan:
Setup:
- Deploy
- Create a rawfile-backed pvc, and attach a Deployment to it
- Keep an eye on `rawfile` pod logs in `kube-system` namespace to see if any errors pop out during all scenarios
Scenario 1:
- Increase the size of the pvc
- Exec into the pod and verify that the volume is resized indeed (using `df`)
Scenario 2:
- Decrease deployment's replica to 0
- Increase the size of the pvc. Wait for a couple of minutes.
- Increase deployment's replica to 1
- Exec into the pod and verify that the volume is resized indeed.
Reviewers: bghadiri, mhyousefi, h.marvi, sina_rad
Reviewed By: bghadiri, mhyousefi, sina_rad
Differential Revision: https://phab.hamravesh.ir/D817
2020-06-12 12:12:49 +00:00
|
|
|
imagePullPolicy: IfNotPresent
|
|
|
|
args:
|
|
|
|
- "--csi-address=$(ADDRESS)"
|
2020-09-11 16:14:29 +00:00
|
|
|
- "--handle-volume-inuse-error=false"
|
Support online volume expansion
Summary:
Online volume expansion is a 2 phase process:
1. The backing storage, in this case the raw file, needs to be resized. (i.e. `truncate -s`)
2. The node should be notified, so that it can both refresh its device capacity (i.e. `losetup -c`) and resize the filesystem (`resize2fs`) accordingly.
Although in our case both steps could be performed on the node itself, for the sake of following the semantics of how volume expansion works, we perform step 1 from the controller, and step 2 from the node.
Also, the `external-resizer` component is added which watches for PVC size updates, and notifies the CSI controller about it.
Test Plan:
Setup:
- Deploy
- Create a rawfile-backed pvc, and attach a Deployment to it
- Keep an eye on `rawfile` pod logs in `kube-system` namespace to see if any errors pop out during all scenarios
Scenario 1:
- Increase the size of the pvc
- Exec into the pod and verify that the volume is resized indeed (using `df`)
Scenario 2:
- Decrease deployment's replica to 0
- Increase the size of the pvc. Wait for a couple of minutes.
- Increase deployment's replica to 1
- Exec into the pod and verify that the volume is resized indeed.
Reviewers: bghadiri, mhyousefi, h.marvi, sina_rad
Reviewed By: bghadiri, mhyousefi, sina_rad
Differential Revision: https://phab.hamravesh.ir/D817
2020-06-12 12:12:49 +00:00
|
|
|
env:
|
|
|
|
- name: ADDRESS
|
|
|
|
value: /csi/csi.sock
|
|
|
|
volumeMounts:
|
|
|
|
- name: socket-dir
|
|
|
|
mountPath: /csi
|