-
Notifications
You must be signed in to change notification settings - Fork 12
/
powermax_v260_ops_411.yaml
235 lines (233 loc) · 9.81 KB
/
powermax_v260_ops_411.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
apiVersion: storage.dell.com/v1
kind: CSIPowerMax
metadata:
name: test-powermax
namespace: test-powermax
spec:
driver:
# Config version for CSI PowerMax v2.6.0 driver
configVersion: v2.6.0
# replica: Define the number of PowerMax controller nodes
# to deploy to the Kubernetes release
# Allowed values: n, where n > 0
# Default value: None
replicas: 2
dnsPolicy: ClusterFirstWithHostNet
forceUpdate: false
fsGroupPolicy: ReadWriteOnceWithFSType
common:
# Image for CSI PowerMax driver v2.6.0
image: dellemc/csi-powermax:v2.6.0
# imagePullPolicy: Policy to determine if the image should be pulled prior to starting the container.
# Allowed values:
# Always: Always pull the image.
# IfNotPresent: Only pull the image if it does not already exist on the node.
# Never: Never pull the image.
# Default value: None
imagePullPolicy: IfNotPresent
envs:
# X_CSI_MANAGED_ARRAYS: Serial ID of the arrays that will be used for provisioning
# Default value: None
# Examples: "000000000001", "000000000002"
- name: X_CSI_MANAGED_ARRAYS
value: "000000000000,000000000001"
# X_CSI_POWERMAX_ENDPOINT: Address of the Unisphere server that is managing the PowerMax arrays
# Default value: None
# Example: https://0.0.0.1:8443
- name: X_CSI_POWERMAX_ENDPOINT
value: "https://0.0.0.0:8443/"
# X_CSI_K8S_CLUSTER_PREFIX: Define a prefix that is appended onto
# all resources created in the Array
# This should be unique per K8s/CSI deployment
# maximum length of this value is 3 characters
# Default value: None
# Examples: "XYZ", "EMC"
- name: X_CSI_K8S_CLUSTER_PREFIX
value: "XYZ"
# X_CSI_POWERMAX_PORTGROUPS: Define the set of existing port groups that the driver will use.
# It is a comma separated list of portgroup names.
# Required only in case of iSCSI port groups
# Allowed values: iSCSI Port Group names
# Default value: None
# Examples: "pg1", "pg1, pg2"
- name: "X_CSI_POWERMAX_PORTGROUPS"
value: ""
# "X_CSI_TRANSPORT_PROTOCOL" can be "FC" or "FIBRE" for fibrechannel,
# "ISCSI" for iSCSI, or "" for autoselection.
# Allowed values:
# "FC" - Fiber Channel protocol
# "FIBER" - Fiber Channel protocol
# "ISCSI" - iSCSI protocol
# "" - Automatic selection of transport protocol
# Default value: "" <empty>
- name: "X_CSI_TRANSPORT_PROTOCOL"
value: ""
# X_CSI_POWERMAX_PROXY_SERVICE_NAME: Refers to the name of the proxy service in kubernetes
# Allowed values: "powermax-reverseproxy"
# default values: "powermax-reverseproxy"
- name: "X_CSI_POWERMAX_PROXY_SERVICE_NAME"
value: "powermax-reverseproxy"
# X_CSI_GRPC_MAX_THREADS: Defines the maximum number of concurrent grpc requests.
# Set this value to a higher number (max 50) if you are using the proxy
# Allowed values: n, where n > 4
# default values: None
- name: "X_CSI_GRPC_MAX_THREADS"
value: "4"
# VMware/vSphere virtualization support
# set X_CSI_VSPHERE_ENABLED to true, if you to enable VMware virtualized environment support via RDM
# Allowed values:
# "true" - vSphere volumes are enabled
# "false" - vSphere volumes are disabled
# Default value: "false"
- name: "X_CSI_VSPHERE_ENABLED"
value: "false"
# X_CSI_VSPHERE_PORTGROUP: An existing portGroup that driver will use for vSphere
# recommended format: csi-x-VC-PG, x can be anything of user choice
# Allowed value: valid existing port group on the array
# Default value: "" <empty>
- name: "X_CSI_VSPHERE_PORTGROUP"
value: ""
# X_CSI_VSPHERE_HOSTNAME: An existing host (initiator group) that driver will use for vSphere
# this host should contain initiators from all the ESXs/ESXi host where the cluster is deployed
# recommended format: csi-x-VC-HN, x can be anything of user choice
# Allowed value: valid existing port group on the array
# Default value: "" <empty>
- name: "X_CSI_VSPHERE_HOSTNAME"
value: ""
# X_CSI_VCENTER_HOST: URL/endpoint of the vCenter where all the ESX are present
# Allowed value: valid vCenter host endpoint
# Default value: "" <empty>
- name: "X_CSI_VCENTER_HOST"
value: ""
controller:
# nodeSelector: Define node selection constraints for controller pods.
# For the pod to be eligible to run on a node, the node must have each
# of the indicated key-value pairs as labels.
# Leave as blank to consider all nodes
# Allowed values: map of key-value pairs
# Default value: None
nodeSelector:
# Uncomment if nodes you wish to use have the node-role.kubernetes.io/control-plane taint
# node-role.kubernetes.io/control-plane: ""
# tolerations: Define tolerations that would be applied to controller deployment
# Leave as blank to install controller on worker nodes
# Allowed values: map of key-value pairs
# Default value: None
tolerations:
# Uncomment if nodes you wish to use have the node-role.kubernetes.io/control-plane taint
# - key: "node-role.kubernetes.io/control-plane"
# operator: "Exists"
# effect: "NoSchedule"
node:
envs:
# X_CSI_POWERMAX_ISCSI_ENABLE_CHAP: Determine if the driver is going to configure
# ISCSI node databases on the nodes with the CHAP credentials
# If enabled, the CHAP secret must be provided in the credentials secret
# and set to the key "chapsecret"
# Allowed values:
# "true" - CHAP is enabled
# "false" - CHAP is disabled
# Default value: "false"
- name: "X_CSI_POWERMAX_ISCSI_ENABLE_CHAP"
value: "false"
# X_CSI_TOPOLOGY_CONTROL_ENABLED provides a way to filter topology keys on a node based on array and transport protocol
# if enabled, user can create custom topology keys by editing node-topology-config configmap.
# Allowed values:
# true: enable the filtration based on config map
# false: disable the filtration based on config map
# Default value: false
- name: X_CSI_TOPOLOGY_CONTROL_ENABLED
value: "false"
# nodeSelector: Define node selection constraints for node pods.
# For the pod to be eligible to run on a node, the node must have each
# of the indicated key-value pairs as labels.
# Leave as blank to consider all nodes
# Allowed values: map of key-value pairs
# Default value: None
nodeSelector:
# Uncomment if nodes you wish to use have the node-role.kubernetes.io/control-plane taint
# node-role.kubernetes.io/control-plane: ""
# tolerations: Define tolerations that would be applied to node daemonset
# Add/Remove tolerations as per requirement
# Leave as blank if you wish to not apply any tolerations
# Allowed values: map of key-value pairs
# Default value: None
tolerations:
- key: "node.kubernetes.io/memory-pressure"
operator: "Exists"
effect: "NoExecute"
- key: "node.kubernetes.io/disk-pressure"
operator: "Exists"
effect: "NoExecute"
- key: "node.kubernetes.io/network-unavailable"
operator: "Exists"
effect: "NoExecute"
---
apiVersion: v1
kind: ConfigMap
metadata:
name: powermax-config-params
namespace: test-powermax
data:
driver-config-params.yaml: |
CSI_LOG_LEVEL: "debug"
CSI_LOG_FORMAT: "JSON"
---
apiVersion: v1
kind: ConfigMap
metadata:
name: node-topology-config
namespace: test-powermax
data:
topologyConfig.yaml: |
# allowedConnections contains a list of (node, array and protocol) info for user allowed configuration
# For any given storage array ID and protocol on a Node, topology keys will be created for just those pair and
# every other configuration is ignored
# Please refer to the doc website about a detailed explanation of each configuration parameter
# and the various possible inputs
allowedConnections:
# nodeName: Name of the node on which user wants to apply given rules
# Allowed values:
# nodeName - name of a specific node
# * - all the nodes
# Examples: "node1", "*"
- nodeName: "node1"
# rules is a list of 'StorageArrayID:TransportProtocol' pair. ':' is required between both value
# Allowed values:
# StorageArrayID:
# - SymmetrixID : for specific storage array
# - "*" :- for all the arrays connected to the node
# TransportProtocol:
# - FC : Fibre Channel protocol
# - ISCSI : iSCSI protocol
# - "*" - for all the possible Transport Protocol
# Examples: "000000000001:FC", "000000000002:*", "*:FC", "*:*"
rules:
- "000000000001:FC"
- "000000000002:FC"
- nodeName: "*"
rules:
- "000000000002:FC"
# deniedConnections contains a list of (node, array and protocol) info for denied configurations by user
# For any given storage array ID and protocol on a Node, topology keys will be created for every other configuration but
# not these input pairs
deniedConnections:
- nodeName: "node2"
rules:
- "000000000002:*"
- nodeName: "node3"
rules:
- "*:*"
---
apiVersion: v1
kind: Secret
metadata:
name: vcenter-creds
# Set driver namespace
namespace: test-powermax
type: Opaque
data:
# set username to the base64 encoded username
username: YWRtaW4=
# set password to the base64 encoded password
password: YWRtaW4=