mirrors/ceph-csi
1
0
Fork 0
mirror of https://github.com/ceph/ceph-csi.git synced 2024-11-14 10:20:20 +00:00
Code Issues Packages Projects Releases Wiki Activity
6753bbfba3
ceph-csi/deploy/nfs/kubernetes/csi-nfsplugin-provisioner.yaml

156 lines
4.6 KiB
YAML
Raw Normal View History

deploy: add deployment artifacts for NFS support These deployment files are heavily based on the CephFS deployment. Deploying an environment with these files work for me in minikube. This should make it possible to add e2e testing as well. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2022-03-30 08:06:07 +00:00
---
kind: Service
apiVersion: v1
metadata:
name: csi-nfsplugin-provisioner
labels:
app: csi-metrics
spec:
selector:
app: csi-nfsplugin-provisioner
ports:
- name: http-metrics
port: 8080
protocol: TCP
targetPort: 8682
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: csi-nfsplugin-provisioner
spec:
selector:
matchLabels:
app: csi-nfsplugin-provisioner
replicas: 3
template:
metadata:
labels:
app: csi-nfsplugin-provisioner
spec:
affinity:
podAntiAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
- labelSelector:
matchExpressions:
- key: app
operator: In
values:
- csi-nfsplugin-provisioner
topologyKey: "kubernetes.io/hostname"
containers:
deploy: make the csi-*plugin containers the default for kubectl commands When issues or bugs are reported, users often share the logs of the default container in a Pod. These logs do not contain the required information, as that mostly only can be found in the logs of the Ceph-CSI container (named csi-cephfsplugin or csi-rbdplugin). By moving the Ceph-CSI containers in the Pods to the 1st in the list, they become the default container for commands like `kubectl logs`. Signed-off-by: Niels de Vos <ndevos@ibm.com>
2024-02-14 12:23:11 +00:00
- name: csi-nfsplugin
revert: revert to 3.11-canary This commit makes template changes for 3.11 release branch to use 3.11-canary tag. Signed-off-by: Rakshith R <rar@redhat.com>
2024-04-02 15:08:52 +00:00
image: quay.io/cephcsi/cephcsi:v3.11-canary
deploy: make the csi-*plugin containers the default for kubectl commands When issues or bugs are reported, users often share the logs of the default container in a Pod. These logs do not contain the required information, as that mostly only can be found in the logs of the Ceph-CSI container (named csi-cephfsplugin or csi-rbdplugin). By moving the Ceph-CSI containers in the Pods to the 1st in the list, they become the default container for commands like `kubectl logs`. Signed-off-by: Niels de Vos <ndevos@ibm.com>
2024-02-14 12:23:11 +00:00
args:
- "--nodeid=$(NODE_ID)"
- "--type=nfs"
- "--controllerserver=true"
- "--endpoint=$(CSI_ENDPOINT)"
- "--v=5"
- "--drivername=nfs.csi.ceph.com"
- "--pidlimit=-1"
- "--enableprofiling=false"
env:
- name: POD_IP
valueFrom:
fieldRef:
fieldPath: status.podIP
- name: NODE_ID
valueFrom:
fieldRef:
fieldPath: spec.nodeName
- name: CSI_ENDPOINT
value: unix:///csi/csi-provisioner.sock
imagePullPolicy: "IfNotPresent"
volumeMounts:
- name: socket-dir
mountPath: /csi
- name: host-sys
mountPath: /sys
- name: ceph-csi-config
mountPath: /etc/ceph-csi-config/
- name: keys-tmp-dir
mountPath: /tmp/csi/keys
deploy: add deployment artifacts for NFS support These deployment files are heavily based on the CephFS deployment. Deploying an environment with these files work for me in minikube. This should make it possible to add e2e testing as well. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2022-03-30 08:06:07 +00:00
- name: csi-provisioner
deploy: update CSI sidecars to latest versions available Below sidecars are updated with latest available versions csi-node-driver-registrar: v2.10.1 csi-resizer: v1.10.1 csi-provisioner: v4.0.1 csi-attacher: v4.5.1 csi-snapshotter: v7.0.2 Signed-off-by: Praveen M <m.praveen@ibm.com> (cherry picked from commit b095e0441abeb466ebfb278445770b8ba2061b80)
2024-04-22 06:20:46 +00:00
image: registry.k8s.io/sig-storage/csi-provisioner:v4.0.1
deploy: add deployment artifacts for NFS support These deployment files are heavily based on the CephFS deployment. Deploying an environment with these files work for me in minikube. This should make it possible to add e2e testing as well. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2022-03-30 08:06:07 +00:00
args:
- "--csi-address=$(ADDRESS)"
deploy: introduce new log level for sidecar controllers At present we have single log level configuration for all the containers running for our CSI pods, which has been defaulted to log Level 5. However this cause many logs to be spitted in a cluster and cause log spamming to an extent. This commit introduce one more log level control for CSI pods called sidecarLogLevel which defaults to log Level 1. The sidecar controllers like snapshotter, resizer, attacher..etc has been configured with this new log level and driver pods are with old configruation value. This allow us to have different configuration options for sidecar constrollers and driver pods. With this, we will also have a choice of different configuation setting instead of locking onto one variable for the containers deployed via CSI driver. To summarize the CSI containers maintained by Ceph CSI driver has log level 5 and controllers/sidecars not maintained by Ceph CSI driver has log level 1 configuration. Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
2022-07-26 04:52:19 +00:00
- "--v=1"
deploy: add deployment artifacts for NFS support These deployment files are heavily based on the CephFS deployment. Deploying an environment with these files work for me in minikube. This should make it possible to add e2e testing as well. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2022-03-30 08:06:07 +00:00
- "--timeout=150s"
- "--leader-election=true"
- "--retry-interval-start=500ms"
deploy: enable HonorPVReclaimPolicy feature gate This commit enables the HonorPVReclaimPolicy feature gate. fixes: #3230 Signed-off-by: Yati Padia <ypadia@redhat.com>
2022-07-20 06:34:10 +00:00
- "--feature-gates=HonorPVReclaimPolicy=true"
deploy: update csi-provisioner to latest version This commits updates csi-provisioner sidecar to latest version i.e., v3.2.0. fixes: #3184 Signed-off-by: Yati Padia <ypadia@redhat.com>
2022-06-15 07:14:49 +00:00
- "--prevent-volume-mode-conversion=true"
deploy: add deployment artifacts for NFS support These deployment files are heavily based on the CephFS deployment. Deploying an environment with these files work for me in minikube. This should make it possible to add e2e testing as well. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2022-03-30 08:06:07 +00:00
env:
- name: ADDRESS
value: unix:///csi/csi-provisioner.sock
imagePullPolicy: "IfNotPresent"
volumeMounts:
- name: socket-dir
mountPath: /csi
deploy: add resize support to NFS-provisioner deployment Resizing is handled by the csi-resizer container, which needs to run in the provisioner Pod. In addition to the container, the StorageClass also needs to allow volume expansion. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2022-05-02 11:18:20 +00:00
- name: csi-resizer
deploy: update CSI sidecars to latest versions available Below sidecars are updated with latest available versions csi-node-driver-registrar: v2.10.1 csi-resizer: v1.10.1 csi-provisioner: v4.0.1 csi-attacher: v4.5.1 csi-snapshotter: v7.0.2 Signed-off-by: Praveen M <m.praveen@ibm.com> (cherry picked from commit b095e0441abeb466ebfb278445770b8ba2061b80)
2024-04-22 06:20:46 +00:00
image: registry.k8s.io/sig-storage/csi-resizer:v1.10.1
deploy: add resize support to NFS-provisioner deployment Resizing is handled by the csi-resizer container, which needs to run in the provisioner Pod. In addition to the container, the StorageClass also needs to allow volume expansion. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2022-05-02 11:18:20 +00:00
args:
- "--csi-address=$(ADDRESS)"
deploy: introduce new log level for sidecar controllers At present we have single log level configuration for all the containers running for our CSI pods, which has been defaulted to log Level 5. However this cause many logs to be spitted in a cluster and cause log spamming to an extent. This commit introduce one more log level control for CSI pods called sidecarLogLevel which defaults to log Level 1. The sidecar controllers like snapshotter, resizer, attacher..etc has been configured with this new log level and driver pods are with old configruation value. This allow us to have different configuration options for sidecar constrollers and driver pods. With this, we will also have a choice of different configuation setting instead of locking onto one variable for the containers deployed via CSI driver. To summarize the CSI containers maintained by Ceph CSI driver has log level 5 and controllers/sidecars not maintained by Ceph CSI driver has log level 1 configuration. Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
2022-07-26 04:52:19 +00:00
- "--v=1"
deploy: add resize support to NFS-provisioner deployment Resizing is handled by the csi-resizer container, which needs to run in the provisioner Pod. In addition to the container, the StorageClass also needs to allow volume expansion. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2022-05-02 11:18:20 +00:00
- "--timeout=150s"
- "--leader-election"
- "--retry-interval-start=500ms"
- "--handle-volume-inuse-error=false"
nfs: enable featuregate for volume expansion recovery The commit enables the featuregate for volume expansion recovery in NFS. Signed-off-by: Praveen M <m.praveen@ibm.com>
2023-11-23 11:48:47 +00:00
- "--feature-gates=RecoverVolumeExpansionFailure=true"
deploy: add resize support to NFS-provisioner deployment Resizing is handled by the csi-resizer container, which needs to run in the provisioner Pod. In addition to the container, the StorageClass also needs to allow volume expansion. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2022-05-02 11:18:20 +00:00
env:
- name: ADDRESS
value: unix:///csi/csi-provisioner.sock
imagePullPolicy: "IfNotPresent"
volumeMounts:
- name: socket-dir
mountPath: /csi
deploy: add support for nfs snapshot This commit add external-snapshotter container and required rbac to support nfs snaphots. Example volumesnaphotclass, volumesnapshot, pvc-restore and pod-restore yamls are also added. Signed-off-by: Rakshith R <rar@redhat.com>
2022-05-16 07:20:43 +00:00
- name: csi-snapshotter
deploy: update CSI sidecars to latest versions available Below sidecars are updated with latest available versions csi-node-driver-registrar: v2.10.1 csi-resizer: v1.10.1 csi-provisioner: v4.0.1 csi-attacher: v4.5.1 csi-snapshotter: v7.0.2 Signed-off-by: Praveen M <m.praveen@ibm.com> (cherry picked from commit b095e0441abeb466ebfb278445770b8ba2061b80)
2024-04-22 06:20:46 +00:00
image: registry.k8s.io/sig-storage/csi-snapshotter:v7.0.2
deploy: add support for nfs snapshot This commit add external-snapshotter container and required rbac to support nfs snaphots. Example volumesnaphotclass, volumesnapshot, pvc-restore and pod-restore yamls are also added. Signed-off-by: Rakshith R <rar@redhat.com>
2022-05-16 07:20:43 +00:00
args:
- "--csi-address=$(ADDRESS)"
deploy: introduce new log level for sidecar controllers At present we have single log level configuration for all the containers running for our CSI pods, which has been defaulted to log Level 5. However this cause many logs to be spitted in a cluster and cause log spamming to an extent. This commit introduce one more log level control for CSI pods called sidecarLogLevel which defaults to log Level 1. The sidecar controllers like snapshotter, resizer, attacher..etc has been configured with this new log level and driver pods are with old configruation value. This allow us to have different configuration options for sidecar constrollers and driver pods. With this, we will also have a choice of different configuation setting instead of locking onto one variable for the containers deployed via CSI driver. To summarize the CSI containers maintained by Ceph CSI driver has log level 5 and controllers/sidecars not maintained by Ceph CSI driver has log level 1 configuration. Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
2022-07-26 04:52:19 +00:00
- "--v=1"
deploy: add support for nfs snapshot This commit add external-snapshotter container and required rbac to support nfs snaphots. Example volumesnaphotclass, volumesnapshot, pvc-restore and pod-restore yamls are also added. Signed-off-by: Rakshith R <rar@redhat.com>
2022-05-16 07:20:43 +00:00
- "--timeout=150s"
- "--leader-election=true"
env:
- name: ADDRESS
value: unix:///csi/csi-provisioner.sock
imagePullPolicy: "IfNotPresent"
volumeMounts:
- name: socket-dir
mountPath: /csi
deploy: add deployment artifacts for NFS support These deployment files are heavily based on the CephFS deployment. Deploying an environment with these files work for me in minikube. This should make it possible to add e2e testing as well. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2022-03-30 08:06:07 +00:00
- name: liveness-prometheus
revert: revert to 3.11-canary This commit makes template changes for 3.11 release branch to use 3.11-canary tag. Signed-off-by: Rakshith R <rar@redhat.com>
2024-04-02 15:08:52 +00:00
image: quay.io/cephcsi/cephcsi:v3.11-canary
deploy: add deployment artifacts for NFS support These deployment files are heavily based on the CephFS deployment. Deploying an environment with these files work for me in minikube. This should make it possible to add e2e testing as well. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2022-03-30 08:06:07 +00:00
args:
- "--type=liveness"
- "--endpoint=$(CSI_ENDPOINT)"
- "--metricsport=8682"
- "--metricspath=/metrics"
- "--polltime=60s"
- "--timeout=3s"
env:
- name: CSI_ENDPOINT
value: unix:///csi/csi-provisioner.sock
- name: POD_IP
valueFrom:
fieldRef:
fieldPath: status.podIP
volumeMounts:
- name: socket-dir
mountPath: /csi
imagePullPolicy: "IfNotPresent"
serviceAccountName: nfs-csi-provisioner
volumes:
- emptyDir:
medium: Memory
name: socket-dir
- name: host-sys
hostPath:
path: /sys
- name: ceph-csi-config
configMap:
name: ceph-csi-config
- emptyDir:
medium: Memory
name: keys-tmp-dir
Reference in New Issue Copy Permalink