Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
…driver into support-openshift
  • Loading branch information
cvvz committed Nov 6, 2023
2 parents bd1e028 + 3f47b3e commit 0c185e7
Show file tree
Hide file tree
Showing 743 changed files with 264,770 additions and 12,002 deletions.
3 changes: 3 additions & 0 deletions .trivyignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
CVE-2023-39325
CVE-2023-44487
GHSA-m425-mq94-257g
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ This option does not depend on cloud provider config file, supports cross subscr
>
> To install specific blobfuse v2 version, run following command directly after driver is running on the agent node:
> ```console
> kubectl patch daemonset csi-blob-node -n kube-system -p '{"spec":{"template":{"spec":{"initContainers":[{"env":[{"name":"INSTALL_BLOBFUSE2","value":"true"},{"name":"BLOBFUSE2_VERSION","value":"2.1.0"}],"name":"install-blobfuse-proxy"}]}}}}'
> kubectl patch daemonset csi-blob-node -n kube-system -p '{"spec":{"template":{"spec":{"initContainers":[{"env":[{"name":"INSTALL_BLOBFUSE2","value":"true"},{"name":"BLOBFUSE2_VERSION","value":"2.1.1"}],"name":"install-blobfuse-proxy"}]}}}}'
> ```
>
- install by [helm charts](./charts)
Expand Down
8 changes: 4 additions & 4 deletions charts/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -66,16 +66,16 @@ The following table lists the configurable parameters of the latest Azure Blob S
| `image.blob.tag` | blob-csi-driver docker image tag | `latest` |
| `image.blob.pullPolicy` | blob-csi-driver image pull policy | `IfNotPresent` |
| `image.csiProvisioner.repository` | csi-provisioner docker image | `mcr.microsoft.com/oss/kubernetes-csi/csi-provisioner` |
| `image.csiProvisioner.tag` | csi-provisioner docker image tag | `v3.5.0` |
| `image.csiProvisioner.tag` | csi-provisioner docker image tag | `v3.6.1` |
| `image.csiProvisioner.pullPolicy` | csi-provisioner image pull policy | `IfNotPresent` |
| `image.livenessProbe.repository` | liveness-probe docker image | `mcr.microsoft.com/oss/kubernetes-csi/livenessprobe` |
| `image.livenessProbe.tag` | liveness-probe docker image tag | `v2.10.0` |
| `image.livenessProbe.tag` | liveness-probe docker image tag | `v2.11.0` |
| `image.livenessProbe.pullPolicy` | liveness-probe image pull policy | `IfNotPresent` |
| `image.nodeDriverRegistrar.repository` | csi-node-driver-registrar docker image | `mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar` |
| `image.nodeDriverRegistrar.tag` | csi-node-driver-registrar docker image tag | `v2.8.0` |
| `image.nodeDriverRegistrar.tag` | csi-node-driver-registrar docker image tag | `v2.9.0` |
| `image.nodeDriverRegistrar.pullPolicy` | csi-node-driver-registrar image pull policy | `IfNotPresent` |
| `image.csiResizer.repository` | csi-resizer docker image | `mcr.microsoft.com/oss/kubernetes-csi/csi-resizer` |
| `image.csiResizer.tag` | csi-resizer docker image tag | `v1.8.0` |
| `image.csiResizer.tag` | csi-resizer docker image tag | `v1.9.1` |
| `image.csiResizer.pullPolicy` | csi-resizer image pull policy | `IfNotPresent` |
| `imagePullSecrets` | Specify docker-registry secret names as an array | [] (does not add image pull secrets to deployed pods) |
| `cloud` | the cloud environment the driver is running on | `AzurePublicCloud` |
Expand Down
Binary file modified charts/latest/blob-csi-driver-v0.0.0.tgz
Binary file not shown.
2 changes: 1 addition & 1 deletion charts/latest/blob-csi-driver/templates/NOTES.txt
Original file line number Diff line number Diff line change
Expand Up @@ -2,4 +2,4 @@ The Azure Blob Storage CSI driver is getting deployed to your cluster.

To check Azure Blob Storage CSI driver pods status, please run:

kubectl --namespace={{ .Release.Namespace }} get pods --selector="release={{ .Release.Name }}" --watch
kubectl --namespace={{ .Release.Namespace }} get pods --selector="app.kubernetes.io/name={{ .Release.Name }}" --watch
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@ spec:
- "--csi-address=$(ADDRESS)"
- "--leader-election"
- "--leader-election-namespace={{ .Release.Namespace }}"
- "--timeout=120s"
- "--timeout=1200s"
- "--extra-create-metadata=true"
- "--kube-api-qps=50"
- "--kube-api-burst=100"
Expand Down
10 changes: 5 additions & 5 deletions charts/latest/blob-csi-driver/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -6,19 +6,19 @@ image:
pullPolicy: IfNotPresent
csiProvisioner:
repository: /oss/kubernetes-csi/csi-provisioner
tag: v3.5.0
tag: v3.6.1
pullPolicy: IfNotPresent
livenessProbe:
repository: /oss/kubernetes-csi/livenessprobe
tag: v2.10.0
tag: v2.11.0
pullPolicy: IfNotPresent
nodeDriverRegistrar:
repository: /oss/kubernetes-csi/csi-node-driver-registrar
tag: v2.8.0
tag: v2.9.0
pullPolicy: IfNotPresent
csiResizer:
repository: /oss/kubernetes-csi/csi-resizer
tag: v1.8.0
tag: v1.9.1
pullPolicy: IfNotPresent

cloud: AzurePublicCloud
Expand Down Expand Up @@ -120,7 +120,7 @@ node:
installBlobfuse: true
blobfuseVersion: "1.4.5"
installBlobfuse2: true
blobfuse2Version: "2.1.0"
blobfuse2Version: "2.1.1"
setMaxOpenFileNum: true
maxOpenFileNum: "9000000"
disableUpdateDB: true
Expand Down
8 changes: 4 additions & 4 deletions deploy/csi-blob-controller.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -34,13 +34,13 @@ spec:
effect: "NoSchedule"
containers:
- name: csi-provisioner
image: mcr.microsoft.com/oss/kubernetes-csi/csi-provisioner:v3.5.0
image: mcr.microsoft.com/oss/kubernetes-csi/csi-provisioner:v3.6.1
args:
- "-v=2"
- "--csi-address=$(ADDRESS)"
- "--leader-election"
- "--leader-election-namespace=kube-system"
- "--timeout=120s"
- "--timeout=1200s"
- "--extra-create-metadata=true"
- "--kube-api-qps=50"
- "--kube-api-burst=100"
Expand All @@ -58,7 +58,7 @@ spec:
cpu: 10m
memory: 20Mi
- name: liveness-probe
image: mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.10.0
image: mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.11.0
args:
- --csi-address=/csi/csi.sock
- --probe-timeout=3s
Expand Down Expand Up @@ -116,7 +116,7 @@ spec:
cpu: 10m
memory: 20Mi
- name: csi-resizer
image: mcr.microsoft.com/oss/kubernetes-csi/csi-resizer:v1.8.0
image: mcr.microsoft.com/oss/kubernetes-csi/csi-resizer:v1.9.1
args:
- "-csi-address=$(ADDRESS)"
- "-v=2"
Expand Down
6 changes: 3 additions & 3 deletions deploy/csi-blob-node.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ spec:
- name: INSTALL_BLOBFUSE2
value: "true"
- name: BLOBFUSE2_VERSION
value: "2.1.0"
value: "2.1.1"
- name: SET_MAX_OPEN_FILE_NUM
value: "true"
- name: MAX_FILE_NUM
Expand All @@ -77,7 +77,7 @@ spec:
volumeMounts:
- mountPath: /csi
name: socket-dir
image: mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.10.0
image: mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.11.0
args:
- --csi-address=/csi/csi.sock
- --probe-timeout=3s
Expand All @@ -90,7 +90,7 @@ spec:
cpu: 10m
memory: 20Mi
- name: node-driver-registrar
image: mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.8.0
image: mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.9.0
args:
- --csi-address=$(ADDRESS)
- --kubelet-registration-path=$(DRIVER_REG_SOCK_PATH)
Expand Down
16 changes: 16 additions & 0 deletions deploy/example/pvc-blob-csi-clone.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: pvc-blob-clone
namespace: default
spec:
accessModes:
- ReadWriteMany
resources:
requests:
storage: 100Gi
storageClassName: blob-fuse
dataSource:
kind: PersistentVolumeClaim
name: pvc-blob
2 changes: 1 addition & 1 deletion deploy/example/storageclass-blobfuse.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ metadata:
name: blob-fuse
provisioner: blob.csi.azure.com
parameters:
skuName: Premium_LRS # available values: Standard_LRS, Premium_LRS, Standard_GRS, Standard_RAGRS
skuName: Premium_LRS # available values: Standard_LRS, Premium_LRS, Standard_GRS, Standard_RAGRS, Standard_ZRS, Premium_ZRS
reclaimPolicy: Delete
volumeBindingMode: Immediate
allowVolumeExpansion: true
Expand Down
2 changes: 1 addition & 1 deletion deploy/example/storageclass-blobfuse2.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ metadata:
name: blob-fuse
provisioner: blob.csi.azure.com
parameters:
skuName: Premium_LRS # available values: Standard_LRS, Premium_LRS, Standard_GRS, Standard_RAGRS
skuName: Premium_LRS # available values: Standard_LRS, Premium_LRS, Standard_GRS, Standard_RAGRS, Standard_ZRS, Premium_ZRS
protocol: fuse2
reclaimPolicy: Delete
volumeBindingMode: Immediate
Expand Down
2 changes: 1 addition & 1 deletion docs/csi-debug.md
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,7 @@ change below deployment config, e.g.
blobfuse2 -v
```
<pre>
blobfuse2 version 2.1.0
blobfuse2 version 2.1.1
</pre>

### check blobfuse mount on the agent node
Expand Down
2 changes: 1 addition & 1 deletion docs/driver-parameters.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@
Name | Meaning | Example | Mandatory | Default value
--- | --- | --- | --- | ---
skuName | Azure storage account type (alias: `storageAccountType`) | `Standard_LRS`, `Premium_LRS`, `Standard_GRS`, `Standard_RAGRS` | No | `Standard_LRS`
skuName | Azure storage account type (alias: `storageAccountType`) | `Standard_LRS`, `Premium_LRS`, `Standard_GRS`, `Standard_RAGRS`, `Standard_ZRS`, `Premium_ZRS` | No | `Standard_LRS`
location | Azure location | `eastus`, `westus`, etc. | No | if empty, driver will use the same location name as current k8s cluster
resourceGroup | Azure resource group name | existing resource group name | No | if empty, driver will use the same resource group name as current k8s cluster
storageAccount | specify Azure storage account name| STORAGE_ACCOUNT_NAME | No | If the driver is not provided with a specific storage account name, it will search for a suitable storage account that matches the account settings within the same resource group. If it cannot find a matching storage account, it will create a new one. However, if a storage account name is specified, the storage account must already exist.
Expand Down
Loading

0 comments on commit 0c185e7

Please sign in to comment.