Skip to content

Commit bca96a0

Browse files
docs: fix architecture links for new docs content structure (#33)
1 parent c6121c2 commit bca96a0

File tree

2 files changed

+4
-2
lines changed

2 files changed

+4
-2
lines changed

README.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,4 +28,6 @@ the machines provisioned by MAAS. The cluster is implemented as a
2828
## Architecture
2929

3030
To visualise the idea of how the different components are architected for deploying a K3s Kubernetes cluster, have a
31-
look at the [architecture diagram](./docs/explanations/architecture.md).
31+
look at the [architecture explanation](./docs/content/explanations/architecture.md).
32+
33+
![Architecture Diagram](http://www.plantuml.com/plantuml/proxy?cache=no&src=https://raw.githubusercontent.com/felix-seifert/gohfert-cluster/refs/heads/main/docs/content/explanations/architecture.puml)

docs/content/explanations/architecture.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
The following architecture diagram gives an idea of how the bare metal machines form a K3s Kubernetes cluster.
44

5-
![Architecture Diagram](http://www.plantuml.com/plantuml/proxy?cache=no&src=https://raw.githubusercontent.com/felix-seifert/gohfert-cluster/refs/heads/main/docs/explanations/architecture.puml)
5+
![Architecture Diagram](http://www.plantuml.com/plantuml/proxy?cache=no&src=https://raw.githubusercontent.com/felix-seifert/gohfert-cluster/refs/heads/main/docs/content/explanations/architecture.puml)
66

77
Even though it might look slightly confusing, we indeed have [several master nodes](./k3s-high-availability-cluster.md)
88
for achieving a high availability architecture.

0 commit comments

Comments
 (0)