You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: content/docs/applicationmobility/_index.md
+1-9
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ Description: >
8
8
9
9
>> NOTE: This tech-preview release is not intended for use in production environment.
10
10
11
-
>> NOTE: Application Mobility requires a time-based license. See [Deployment](./deployment) for instructions.
11
+
>> NOTE: Application Mobility requires a time-based license. See [Deployment](../deployment/helm/modules/installation/applicationmobility/) for instructions.
12
12
13
13
Container Storage Modules for Application Mobility provide Kubernetes administrators the ability to clone their stateful application workloads and application data to other clusters, either on-premise or in the cloud.
14
14
@@ -28,11 +28,3 @@ After a backup has been created, it can be restored on the same Kubernetes clust
28
28
|-|-|
29
29
| Restic | Persistent Volume data will be stored in the provided object store bucket |
Application Mobility requires a license in order to function. See the [Deployment](../deployment) instructions for steps to request a license.
43
+
Application Mobility requires a license in order to function. See the [Deployment](../../deployment/helm/modules/installation/applicationmobility/) instructions for steps to request a license.
44
44
45
45
There will be errors in the logs about the license for these cases:
Redis is used to store application data regarding [tenants, quota, and volume ownership](../../design#quota--volume-ownership) with the Storage Class specified in the `redis.storageClass` parameter in the values file, or with the default Storage Class if that parameter was not specified.
78
+
Redis is used to store application data regarding [tenants, quota, and volume ownership](../../design#quota--volume-ownership) with the Storage Class `csm-authorization-local-storage` or the one specified in the `redis.storageClass` parameter in the values file.
79
79
80
-
The Persistent Volume for Redis is dynamically provisioned by this Storage Class with the `redis-primary-pv-claim` Persistent Volume Claim. See the example.
80
+
The Persistent Volume for Redis is provisioned by the above Storage Class with the `redis-primary-pv-claim` Persistent Volume Claim. See the example.
Copy file name to clipboardexpand all lines: content/docs/authorization/_index.md
+2-28
Original file line number
Diff line number
Diff line change
@@ -29,38 +29,12 @@ The following diagram shows a high-level overview of CSM for Authorization with
29
29
30
30
**NOTE:** PowerScale OneFS implements its own form of Role-Based Access Control (RBAC). CSM for Authorization does not enforce any role-based restrictions for PowerScale. To configure RBAC for PowerScale, refer to the PowerScale OneFS [documentation](https://www.dell.com/support/home/en-us/product-support/product/isilon-onefs/docs).
| CSI Driver for Dell PowerFlex |[csi-powerflex](https://github.com/dell/csi-powerflex)| v2.0 + |
54
-
| CSI Driver for Dell PowerMax |[csi-powermax](https://github.com/dell/csi-powermax)| v2.0 + |
55
-
| CSI Driver for Dell PowerScale |[csi-powerscale](https://github.com/dell/csi-powerscale)| v2.0 + |
56
-
{{</table>}}
32
+
## Authorization Components Support Matrix
33
+
CSM for Authorization consists of 2 components - The authorization sidecar, bundled with the driver, communicates with the Authorization proxy server to validate access to Storage platforms. The authorization sidecar is backward compatible with older Authorization proxy server versions. However, it is highly recommended to have the Authorization proxy server and sidecar installed from the same release of CSM.
57
34
58
35
**NOTE:** If the deployed CSI driver has a number of controller pods equal to the number of schedulable nodes in your cluster, CSM for Authorization may not be able to inject properly into the driver's controller pod.
59
36
To resolve this, please refer to our [troubleshooting guide](./troubleshooting) on the topic.
60
37
61
-
## Authorization Components Support Matrix
62
-
CSM for Authorization consists of 2 components - The authorization sidecar, bundled with the driver, communicates with the Authorization proxy server to validate access to Storage platforms. The authorization sidecar is backward compatible with older Authorization proxy server versions. However, it is highly recommended to have the Authorization proxy server and sidecar installed from the same release of CSM.
63
-
64
38
## Roles and Responsibilities
65
39
66
40
The CSM for Authorization CLI can be executed in the context of the following roles:
Copy file name to clipboardexpand all lines: content/docs/authorization/configuration/powerflex/_index.md
+9-9
Original file line number
Diff line number
Diff line change
@@ -55,7 +55,7 @@ Given a setup where Kubernetes, a storage system, and the CSM for Authorization
55
55
56
56
**Helm**
57
57
58
-
Refer to the [Install the Driver](../../../csidriver/installation/helm/powerflex/#install-the-driver) section to edit the parameters in `samples/config.yaml` to configure the driver to communicate with the CSM Authorization sidecar.
58
+
Refer to the [Install the Driver](../../../deployment/helm/drivers/installation/powerflex/#install-the-driver) section to edit the parameters in `samples/config.yaml` to configure the driver to communicate with the CSM Authorization sidecar.
59
59
60
60
- Update `endpoint` to match the localhost endpoint in`samples/secret/karavi-authorization-config.json`.
61
61
@@ -78,7 +78,7 @@ Given a setup where Kubernetes, a storage system, and the CSM for Authorization
78
78
79
79
**Operator**
80
80
81
-
Refer to the [Create Secret](../../../deployment/csmoperator/drivers/powerflex/#create-secret) section to prepare `config.yaml` to configure the driver to communicate with the CSM Authorization sidecar.
81
+
Refer to the [Create Secret](../../../deployment/csmoperator/drivers/powerflex/#create-secret) section to prepare `secret.yaml` to configure the driver to communicate with the CSM Authorization sidecar.
82
82
83
83
- Update `endpoint` to match the localhost endpoint in`samples/secret/karavi-authorization-config.json`.
84
84
@@ -102,13 +102,13 @@ Given a setup where Kubernetes, a storage system, and the CSM for Authorization
102
102
103
103
**Helm**
104
104
105
-
Refer to the [Install the Driver](../../../csidriver/installation/helm/powerflex/#install-the-driver) section to edit the parameters in `myvalues.yaml` to enable CSM Authorization.
105
+
Refer to the [Install the Driver](../../../deployment/helm/drivers/installation/powerflex/#install-the-driver) section to edit the parameters in `myvalues.yaml` to enable CSM Authorization.
106
106
107
107
- Update `authorization.enabled` to `true`.
108
108
109
109
- Update `images.authorization` to the image of the CSM Authorization sidecar. In most cases, you can leave the default value.
110
110
111
-
- Update `authorization.proxyHost` to the hostname of the CSM Authorization Proxy Server.
111
+
- Update `authorization.proxyHost` to the hostname of the CSM Authorization Proxy Server.`csm-authorization.com` is a placeholder for the proxyHost. See the administrator of CSM for Authorization for the correct value.
112
112
113
113
- Update `authorization.skipCertificateValidation` to `true` or `false` depending on if you want to disable or enable certificate validation of the CSM Authorization Proxy Server.
114
114
@@ -119,8 +119,8 @@ Given a setup where Kubernetes, a storage system, and the CSM for Authorization
119
119
enabled: true
120
120
121
121
# sidecarProxyImage: the container image used for the csm-authorization-sidecar.
# proxyHost: hostname of the csm-authorization server
126
126
# Default value: None
@@ -144,7 +144,7 @@ Given a setup where Kubernetes, a storage system, and the CSM for Authorization
144
144
145
145
- Update the `image` to the image of the CSM Authorization sidecar. In most cases, you can leave the default value.
146
146
147
-
- Update the `PROXY_HOST` environment value to the hostname of the CSM Authorization Proxy Server.
147
+
- Update the `PROXY_HOST` environment value to the hostname of the CSM Authorization Proxy Server.`csm-authorization.com` is a placeholder for the proxyHost. See the administrator of CSM for Authorization for the correct value.
148
148
149
149
- Update the `SKIP_CERTIFICATE_VALIDATION` environment value to `true` or `false` depending on if you want to disable or enable certificate validation of the CSM Authorization Proxy Server.
150
150
@@ -156,10 +156,10 @@ Given a setup where Kubernetes, a storage system, and the CSM for Authorization
156
156
- name: authorization
157
157
# enable: Enable/Disable csm-authorization
158
158
enabled: true
159
-
configVersion: v1.9.0
159
+
configVersion: v1.10.0
160
160
components:
161
161
- name: karavi-authorization-proxy
162
-
image: dellemc/csm-authorization-sidecar:v1.9.0
162
+
image: dellemc/csm-authorization-sidecar:v1.10.0
163
163
envs:
164
164
# proxyHost: hostname of the csm-authorization server
4. Enable CSM Authorization inthe driver installation applicable to your installation method.
54
+
4. Prepare the driver configuration secret, applicable to your driver installation method, to communicate with the CSM Authorization sidecar.
55
55
56
56
**Helm**
57
57
58
-
In [Install the Driver](../../../csidriver/installation/helm/powermax/#install-the-driver) where you edit `samples/secret/secret.yaml` with the credentials of the PowerMax, you can leave these with the default values as they will be ignored.
58
+
Refer to the [Install the Driver](../../../deployment/helm/drivers/installation/powermax/#install-the-driver) section where you edit `samples/secret/secret.yaml` with the credentials of the PowerMax. Leave `username` and `password` with the default values as they will be ignored.
59
59
60
-
Refer to the [Install the Driver](../../../csidriver/installation/helm/powermax/#install-the-driver) section to edit the parameters in `my-powermax-settings.yaml` file to configure the driver to communicate with the CSM Authorization sidecar.
60
+
**Operator**
61
+
62
+
Refer to the [Install the Driver](../../../deployment/csmoperator/drivers/powermax/#install-driver) section to prepare `powermax-creds.yaml`. Leave `username` and `password` with the default values as they will be ignored.
63
+
64
+
5. Enable CSM Authorization in the driver installation applicable to your installation method.
65
+
66
+
**Helm**
67
+
68
+
Refer to the [Install the Driver](../../../deployment/helm/drivers/installation/powermax/#install-the-driver) section to edit the parameters in `my-powermax-settings.yaml` file to configure the driver to communicate with the CSM Authorization sidecar.
61
69
62
70
- Update `global.storageArrays.endpoint` to match the localhost endpoint in`samples/secret/karavi-authorization-config.json`.
63
71
@@ -67,7 +75,7 @@ Create the karavi-authorization-config secret using this command:
67
75
68
76
- Update `images.authorization` to the image of the CSM Authorization sidecar. In most cases, you can leave the default value.
69
77
70
-
- Update `authorization.proxyHost` to the hostname of the CSM Authorization Proxy Server.
78
+
- Update `authorization.proxyHost` to the hostname of the CSM Authorization Proxy Server.`csm-authorization.com` is a placeholder for the proxyHost. See the administrator of CSM for Authorization for the correct value.
71
79
72
80
- Update `authorization.skipCertificateValidation` to `true` or `false` depending on if you want to disable or enable certificate validation of the CSM Authorization Proxy Server.
73
81
@@ -85,8 +93,8 @@ Create the karavi-authorization-config secret using this command:
85
93
enabled: true
86
94
87
95
# sidecarProxyImage: the container image used for the csm-authorization-sidecar.
# proxyHost: hostname of the csm-authorization server
92
100
# Default value: None
@@ -110,7 +118,7 @@ Create the karavi-authorization-config secret using this command:
110
118
111
119
- Update the `image` to the image of the CSM Authorization sidecar. In most cases, you can leave the default value.
112
120
113
-
- Update the `PROXY_HOST` environment value to the hostname of the CSM Authorization Proxy Server.
121
+
- Update the `PROXY_HOST` environment value to the hostname of the CSM Authorization Proxy Server.`csm-authorization.com` is a placeholder for the proxyHost. See the administrator of CSM for Authorization for the correct value.
114
122
115
123
- Update the `SKIP_CERTIFICATE_VALIDATION` environment value to `true` or `false` depending on if you want to disable or enable certificate validation of the CSM Authorization Proxy Server.
116
124
@@ -122,10 +130,10 @@ Create the karavi-authorization-config secret using this command:
122
130
- name: authorization
123
131
# enable: Enable/Disable csm-authorization
124
132
enabled: true
125
-
configVersion: v1.9.0
133
+
configVersion: v1.10.0
126
134
components:
127
135
- name: karavi-authorization-proxy
128
-
image: dellemc/csm-authorization-sidecar:v1.9.0
136
+
image: dellemc/csm-authorization-sidecar:v1.10.0
129
137
envs:
130
138
# proxyHost: hostname of the csm-authorization server
Refer to the [Install the Driver](../../../csidriver/installation/helm/isilon/#install-the-driver) section to edit the parameters in `samples/secret/secret.yaml` file to configure the driver to communicate with the CSM Authorization sidecar.
59
+
Refer to the [Install the Driver](../../../deployment/helm/drivers/installation/isilon/#install-the-driver) section to edit the parameters to prepare the `samples/secret/secret.yaml` file to configure the driver to communicate with the CSM Authorization sidecar.
60
60
61
61
- Update `endpoint` to match the localhost endpoint in`samples/secret/karavi-authorization-config.json`.
Refer to the [Install the Driver](../../../csidriver/installation/helm/isilon/#install-the-driver) section to edit the parameters in `my-isilon-settings.yaml` file to enable CSM Authorization.
113
+
Refer to the [Install the Driver](../../../deployment/helm/drivers/installation/isilon/#install-the-driver) section to edit the parameters in `my-isilon-settings.yaml` file to enable CSM Authorization.
114
114
115
115
- Update `authorization.enabled` to `true`.
116
116
117
117
- Update `images.authorization` to the image of the CSM Authorization sidecar. In most cases, you can leave the default value.
118
118
119
-
- Update `authorization.proxyHost` to the hostname of the CSM Authorization Proxy Server.
119
+
- Update `authorization.proxyHost` to the hostname of the CSM Authorization Proxy Server.`csm-authorization.com` is a placeholder for the proxyHost. See the administrator of CSM for Authorization for the correct value.
120
120
121
121
- Update `authorization.skipCertificateValidation` to `true` or `false` depending on if you want to disable or enable certificate validation of the CSM Authorization Proxy Server.
- Update the `image` to the image of the CSM Authorization sidecar. In most cases, you can leave the default value.
154
154
155
-
- Update the `PROXY_HOST` environment value to the hostname of the CSM Authorization Proxy Server.
155
+
- Update the `PROXY_HOST` environment value to the hostname of the CSM Authorization Proxy Server.`csm-authorization.com` is a placeholder for the proxyHost. See the administrator of CSM for Authorization for the correct value.
156
156
157
157
- Update the `SKIP_CERTIFICATE_VALIDATION` environment value to `true` or `false` depending on if you want to disable or enable certificate validation of the CSM Authorization Proxy Server.
0 commit comments