Fix cluster path in examples

Signed-off-by: Philip Laine <philip.laine@gmail.com>
pull/668/head
Philip Laine 4 years ago
parent 67643e7487
commit 505701e1c6

@ -159,7 +159,7 @@ comes from but rather the kustomization source ref. This mean that commit status
if the manifests comes from a repository which the API token is not allowed to write to. if the manifests comes from a repository which the API token is not allowed to write to.
Copy the manifest content in the "[kustomize](https://github.com/stefanprodan/podinfo/tree/master/kustomize)" directory Copy the manifest content in the "[kustomize](https://github.com/stefanprodan/podinfo/tree/master/kustomize)" directory
into the directory "staging-cluster/flux-system/podinfo" in your fleet-infra repository. Make sure that you also add the into the directory "./clusters/my-cluster/podinfo" in your fleet-infra repository. Make sure that you also add the
namespace podinfo. namespace podinfo.
```yaml ```yaml
apiVersion: v1 apiVersion: v1
@ -178,7 +178,7 @@ metadata:
spec: spec:
interval: 5m interval: 5m
targetNamespace: podinfo targetNamespace: podinfo
path: ./staging-cluster/podinfo path: ./clusters/my-cluster/podinfo
prune: true prune: true
sourceRef: sourceRef:
kind: GitRepository kind: GitRepository
@ -224,7 +224,8 @@ spec:
By now the fleet-infra repository should have a similar directory structure. By now the fleet-infra repository should have a similar directory structure.
``` ```
fleet-infra fleet-infra
└── staging-cluster/ └── clusters/
└── my-cluster/
├── flux-system/ ├── flux-system/
│ ├── gotk-components.yaml │ ├── gotk-components.yaml
│ ├── gotk-sync.yaml │ ├── gotk-sync.yaml

Loading…
Cancel
Save