Skip to content

Commit f78a611

Browse files
committed
Streamline getting started with managed resources guide by removing fine grained details
Signed-off-by: Jared Watts <[email protected]>
1 parent 0fd8146 commit f78a611

File tree

1 file changed

+1
-35
lines changed

1 file changed

+1
-35
lines changed

content/v2.0-preview/get-started/get-started-with-managed-resources.md

Lines changed: 1 addition & 35 deletions
Original file line numberDiff line numberDiff line change
@@ -134,26 +134,6 @@ generic aws-secret \
134134
--from-file=creds=./aws-credentials.txt
135135
```
136136

137-
View the secret with `kubectl describe secret`
138-
139-
{{< hint type="note" >}}
140-
The size may be larger if there are extra blank spaces in your text file.
141-
{{< /hint >}}
142-
143-
```shell {copy-lines="1"}
144-
kubectl describe secret aws-secret -n crossplane-system
145-
Name: aws-secret
146-
Namespace: crossplane-system
147-
Labels: <none>
148-
Annotations: <none>
149-
150-
Type: Opaque
151-
152-
Data
153-
====
154-
creds: 114 bytes
155-
```
156-
157137
## Create a ProviderConfig
158138
A {{< hover label="providerconfig" line="3">}}ProviderConfig{{</ hover >}}
159139
customizes the settings of the AWS Provider.
@@ -180,11 +160,6 @@ EOF
180160
This attaches the AWS credentials, saved as a Kubernetes secret, as a
181161
{{< hover label="providerconfig" line="9">}}secretRef{{</ hover>}}.
182162

183-
The
184-
{{< hover label="providerconfig" line="11">}}spec.credentials.secretRef.name{{< /hover >}}
185-
value is the name of the Kubernetes secret containing the AWS credentials in the
186-
{{< hover label="providerconfig" line="10">}}spec.credentials.secretRef.namespace{{< /hover >}}.
187-
188163
## Create a namespace
189164
Before we can create our namespaced S3 bucket managed resource, we must create a
190165
namespace for it.
@@ -214,19 +189,10 @@ spec:
214189
EOF
215190
```
216191

217-
The {{< hover label="xr" line="2">}}apiVersion{{< /hover >}} and
218-
{{< hover label="xr" line="3">}}kind{{</hover >}} are from the provider's CRDs.
219-
220192
The {{< hover label="xr" line="6">}}metadata.generateName{{< /hover >}} gives a
221193
pattern that the provider will use to create a unique name for the bucket in S3.
222194
The generated name will look like `crossplane-bucket-<hash>`.
223195

224-
The {{< hover label="xr" line="9">}}spec.forProvider.region{{< /hover >}} tells
225-
AWS which AWS region to use when deploying resources.
226-
227-
The region can be any
228-
[AWS Regional endpoint](https://docs.aws.amazon.com/general/latest/gr/rande.html#regional-endpoints) code.
229-
230196
Use `kubectl -n crossplane-aws-app get buckets.s3.aws.m.upbound.io` to verify Crossplane created the bucket.
231197

232198
{{< hint type="tip" >}}
@@ -241,7 +207,7 @@ crossplane-bucket-7tfcj True True crossplane-bucket-7tfcj 3m4s
241207
```
242208

243209
## Delete the managed resource
244-
Before shutting down your Kubernetes cluster, delete the S3 bucket just created.
210+
Before shutting down your Kubernetes cluster, delete the S3 bucket that was just created.
245211

246212
Use `kubectl -n crossplane-aws-app delete buckets.s3.aws.m.upbound.io <bucketname>` to remove the bucket.
247213

0 commit comments

Comments
 (0)