Skip to content

Commit c7e612d

Browse files
readme: Updated example paths
Signed-off-by: Michal Tomczak <michaltomczakse@gmail.com>
1 parent 102ce5a commit c7e612d

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

README.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -34,27 +34,27 @@ An alternative, that will get you started quickly, is to reuse existing
3434
credentials from within the control plane.
3535

3636
First install `provider-helm` with [additional
37-
configuration](./examples/provider-config/provider-incluster.yaml) to bind its
37+
configuration](./examples/cluster/provider-config/provider-incluster.yaml) to bind its
3838
service account to an existing role in the cluster:
3939

4040
```console
41-
kubectl apply -f ./examples/provider-config/provider-incluster.yaml
41+
kubectl apply -f ./examples/cluster/provider-config/provider-incluster.yaml
4242
```
4343

4444
Then simply create a
45-
[`ProviderConfig`](./examples/provider-config/provider-config-incluster.yaml)
45+
[`ProviderConfig`](./examples/cluster/provider-config/provider-config-incluster.yaml)
4646
that uses an `InjectedIdentity` source:
4747

4848
```console
49-
kubectl apply -f ./examples/provider-config/provider-config-incluster.yaml
49+
kubectl apply -f ./examples/cluster/provider-config/provider-config-incluster.yaml
5050
```
5151

5252
`provider-helm` will then be installed and ready to use within the cluster. You
5353
can now create `Release` resources, such as [sample
54-
release.yaml](examples/sample/release.yaml).
54+
release.yaml](examples/cluster/sample/release.yaml).
5555

5656
```console
57-
kubectl create -f examples/sample/release.yaml
57+
kubectl create -f examples/cluster/sample/release.yaml
5858
```
5959

6060
## Design
@@ -86,12 +86,12 @@ using `kind` for local development):
8686
```console
8787
KUBECONFIG=$(kind get kubeconfig | sed -e 's|server:\s*.*$|server: http://localhost:8081|g')
8888
kubectl -n crossplane-system create secret generic cluster-config --from-literal=kubeconfig="${KUBECONFIG}"
89-
kubectl apply -f examples/provider-config/provider-config-with-secret.yaml
89+
kubectl apply -f examples/cluster/provider-config/provider-config-with-secret.yaml
9090
```
9191

9292
Now you can create `Release` resources with this `ProviderConfig`, for example
93-
[sample release.yaml](examples/sample/release.yaml).
93+
[sample release.yaml](examples/cluster/sample/release.yaml).
9494

9595
```console
96-
kubectl create -f examples/sample/release.yaml
96+
kubectl create -f examples/cluster/sample/release.yaml
9797
```

0 commit comments

Comments
 (0)