Skip to content

Commit 90ed49c

Browse files
Merge pull request #1322 from adolfo-ab/fix-readme-broken-link
CLID-504: fix broken links in docs
2 parents c5027f3 + 5cbfd5d commit 90ed49c

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,7 @@ Three workflows are available with this command: `m2d`, `d2m` and `m2m`.
8686
### Creating the Image Set Configuration
8787
The Image Set Configuration is the input file for the oc-mirror command (using the flag `-c` or `--config`).
8888

89-
Here is an example of the Image Set Configuration for reference. More examples can be found [here](v2/docs/image-set-examples/).
89+
Here is an example of the Image Set Configuration for reference. More examples can be found [here](docs/image-set-examples/).
9090

9191
```
9292
kind: ImageSetConfiguration
@@ -180,7 +180,7 @@ There is also a `delete` sub command to delete images specified in the Delete Im
180180
- Phase 1: using a delete image set configuration as an input, oc-mirror discovers all images that needed to be deleted. These images are included in a delete-images file to be consumed as input in the second phase.
181181
- Phase 2: using the file generated in first phase, oc-mirror will delete all container image manifests specified on this file on the destination specified in the command line. It is up to the container registry to run the garbage collector to clean up all the blobs which are not referenced by a manifest. Deleting only manifests is safer since blobs shared between more than one image are not going to be deleted.
182182

183-
For more details about the delete feature can be found [here](v2/docs/features/delete-functionality.md).
183+
For more details about the delete feature can be found [here](docs/features/delete-functionality.md).
184184

185185
### Creating the Delete Image Set Configuration
186186

@@ -260,7 +260,7 @@ make v2cover
260260
This section will give an overview about oc-mirror v2 architecture and how to generate docs from oc-mirror source code.
261261

262262
### Architecture
263-
![Alt text](v2/assets/architecture.png)
263+
![Alt text](assets/architecture.png)
264264

265265
### Code Source Documentation Only for oc-mirror v2 developers
266266

docs/features/enclave_support.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -31,15 +31,15 @@ The Enclave Support feature (`--v2`) mirrors OCP releases, Operator catalogs, ad
3131

3232

3333
## Reference Architecture Diagram for Enclave Support
34-
![Architecture](../assets/architecture.png)
34+
![Architecture](../../assets/architecture.png)
3535

3636
## How to mirror to an enclave?
3737

3838
The following diagram will be used to illustrate the workflow for mirroring to enclaves, with an intermediate disconnected network stage, called airgap env in the diagram.
3939

4040

4141
### Overall diagram
42-
![enclave support flow](../assets/enclave_support_flow.jpg)
42+
![enclave support flow](../../assets/enclave_support_flow.jpg)
4343

4444

4545
### Phase 1 - Mirroring to the airgap env(on-premise registry)

0 commit comments

Comments
 (0)