-
Notifications
You must be signed in to change notification settings - Fork 8
/
Copy pathcsi-wekafs-api-secret.yaml
37 lines (36 loc) · 2.25 KB
/
csi-wekafs-api-secret.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
apiVersion: v1
kind: Secret
metadata:
name: csi-wekafs-api-secret
namespace: csi-wekafs
type: Opaque
data:
# username to connect to the cluster API (base64-encoded)
username: YWRtaW4=
# password to connect to the cluster API (base64-encoded)
password: YWRtaW4=
# organization to connect to (default Root, base64-encoded)
organization: Um9vdA==
# comma-separated list of cluster management endpoints in form of <IP:port> (base64-encoded)
# It is recommended to configure at least 2 management endpoints (cluster backend nodes), or a load-balancer if used
# e.g. 172.31.15.113:14000,172.31.12.91:14000
endpoints: MTcyLjMxLjQxLjU0OjE0MDAwLDE3Mi4zMS40Ny4xNTI6MTQwMDAsMTcyLjMxLjM4LjI1MDoxNDAwMCwxNzIuMzEuNDcuMTU1OjE0MDAwLDE3Mi4zMS4zMy45MToxNDAwMCwxNzIuMzEuMzguMTU1OjE0MDAwCg==
# protocol to use for API connection (either http or https, base64-encoded. NOTE: since Weka 4.3.0, HTTPS is mandatory)
scheme: aHR0cA==
# for multiple clusters setup, set specific container name rather than attempt to identify it automatically
localContainerName: ""
# for cloud deployments with automatic healing and auto-scaling, set to "true" to enable automatic updates of the endpoints.
# The API endpoints will be updated automatically on first connection to the cluster API, as well as on each re-login
# maybe either (true/false), base64-encoded
# NOTE: if a load balancer is used to access the cluster API, leave this setting as "false"
autoUpdateEndpoints: ZmFsc2U=
# It is recommended to configure all NFS server IP addresses to better share the load/balance the traffic.
# NOTE: this setting is optional and should be used only when the NFS Group IP addresses are not set in the cluster
# WARNING: providing a load balancer IP address that uses NFS connection redirects (also known as `referrals`) to other servers is not supported.
# e.g. 10.100.100.1,10.100.100.2
nfsTargetIps: ""
# When using HTTPS connection and self-signed or untrusted certificates, provide a CA certificate in PEM format, base64-encoded
# for cloud deployments or other scenarios where setting an NFS Group IP addresses is not possible,
# provide a comma-separated list of NFS target IP addresses in form of <IP> (base64-encoded)
# caCertificate: <base64-encoded-PEM>
caCertificate: ""