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: docs/Usage.md
+9-20Lines changed: 9 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,7 +77,6 @@ In the **Scality COSI Driver**, both **Greenfield** and **Brownfield** provision
77
77
78
78
> Note:
79
79
> For **fully working** examples, see the YAMLs in the [cosi-examples/brownfield](../cosi-examples/brownfield/) and [cosi-examples/greenfield](../cosi-examples/greenfield/) directories.
80
-
> For brownfield scenario it is madatory to create COSI CRs in the same namespace as COSI driver and controller.
81
80
82
81
### 1.1 Greenfield: Creating a New Bucket
83
82
@@ -92,7 +91,6 @@ Greenfield provisioning will create a brand-new S3 bucket in your object store,
92
91
kind: BucketClass
93
92
metadata:
94
93
name: greenfield-bucketclass
95
-
namespace: container-object-storage-system
96
94
driverName: cosi.scality.com
97
95
deletionPolicy: Delete
98
96
parameters:
@@ -115,7 +113,6 @@ Greenfield provisioning will create a brand-new S3 bucket in your object store,
115
113
kind: BucketClaim
116
114
metadata:
117
115
name: my-greenfield-bucketclaim
118
-
namespace: container-object-storage-system
119
116
spec:
120
117
bucketClassName: greenfield-bucketclass
121
118
protocols:
@@ -131,8 +128,6 @@ Greenfield provisioning will create a brand-new S3 bucket in your object store,
131
128
132
129
Brownfield provisioning allows you to manage an **already-existing** S3 bucket in Kubernetes.
133
130
134
-
> Note: For brownfield scenario, COSI CRs forBucket and Access provisioning should be createdin the same namespace as COSI driver and controller.
135
-
136
131
1. **Verify Existing Bucket**
137
132
138
133
Ensure the bucket already exists in S3 either through Storage Administrator or by running the following AWS CLI command:
@@ -151,7 +146,6 @@ Brownfield provisioning allows you to manage an **already-existing** S3 bucket i
151
146
kind: BucketClass
152
147
metadata:
153
148
name: brownfield-bucketclass
154
-
namespace: container-object-storage-system
155
149
driverName: cosi.scality.com
156
150
deletionPolicy: Delete
157
151
parameters:
@@ -172,7 +166,6 @@ Brownfield provisioning allows you to manage an **already-existing** S3 bucket i
172
166
kind: Bucket
173
167
metadata:
174
168
name: "<EXISTING_BUCKET_NAME>"
175
-
namespace: container-object-storage-system
176
169
spec:
177
170
bucketClaim: {}
178
171
driverName: cosi.scality.com
@@ -199,9 +192,8 @@ Brownfield provisioning allows you to manage an **already-existing** S3 bucket i
199
192
kind: BucketClaim
200
193
metadata:
201
194
name: my-brownfield-bucketclaim
202
-
namespace: container-object-storage-system
203
195
spec:
204
-
bucketClassName: brownfield-bucket-class
196
+
bucketClassName: brownfield-bucketclass
205
197
existingBucketName: "<EXISTING_BUCKET_NAME>"
206
198
protocols:
207
199
- S3
@@ -244,17 +236,15 @@ A `BucketAccessClass` defines how access (IAM policy or S3 keys) is granted:
0 commit comments