Skip to content

Commit 27ade0f

Browse files
docs: fix broken section anchors across versioned docs (#745)
I ran a link check over cozystack.io/docs and found section anchors that don't exist on the pages they link to. This PR fixes them in every version directory where they show up (`next/`, `v0`–`v1.6`): - `guides/concepts#tenant-system` → `#tenant`. The heading is "Tenant". The `development.md` link also pointed at the unversioned `/docs/guides/concepts/`, which is an alias that redirects to v0 and drops the fragment. It now uses a versioned `ref`. - `install/kubernetes/talm#1-initialize-cluster-configuration` → `#2-initialize-cluster-configuration` (Hetzner guide). - `install/kubernetes/talm#3-apply-node-configuration` → `#41-apply-configuration-files` (single-disk how-to, "`talm apply`"). - FAQ "Public IP Setup": `install/cozystack#4b-public-ip-setup` → `install/cozystack/platform#4b-node-public-ip-setup` (v1.x). In v0 the page didn't move, so only the anchor changes: `#4b-node-public-ip-setup`. - `guides/platform-stack#drbd` → `#drbd-and-linstor` (v0–v1.2). - v1.3+ (and `next/`): the platform-stack page is now organized by area, so the per-component anchors in `operations/configuration/variants.md` (`#victoria-metrics`, `#drbd`, `#kube-ovn`, `#cilium`, `#kubevirt`, `#talos-linux`, `#kubernetes`) now point at the matching sections (`#observability`, `#storage-and-backup`, `#networking`, `#cluster-provisioning-and-virtualization`, `#operating-system-and-kubernetes-runtime`). I checked every new target against the live page ids on cozystack.io. Only links changed, no prose.
2 parents 5899a50 + 7a0e89e commit 27ade0f

58 files changed

Lines changed: 97 additions & 97 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎content/en/blog/2024-04-05-diy-create-your-own-cloud-with-kubernetes-part-2/index.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ project and development team.
3636
Virtual machines are the primary means of isolating tenants from each other in a cloud environment.
3737
In virtual machines, users can execute code and programs with administrative privilege, but this
3838
doesn't affect other tenants or the environment itself. In other words, virtual machines allow to
39-
achieve [hard multi-tenancy isolation]({{% ref "/docs/v1.0/guides/concepts#tenant-system" %}}), and run
39+
achieve [hard multi-tenancy isolation]({{% ref "/docs/v1.0/guides/concepts#tenant" %}}), and run
4040
in environments where tenants do not trust each other.
4141

4242
## Virtualization technologies in Kubernetes

‎content/en/docs/next/development.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -217,7 +217,7 @@ Other examples of this pattern: `extra/ingress`, `extra/seaweedfs`, `extra/monit
217217
Similar to `apps` but not shown in the application catalog. They can only be installed as part of a tenant.
218218
They are allowed to use by bottom tenants installed in current tenant namespace.
219219
220-
Read more about [Tenant System](/docs/guides/concepts/#tenant-system) on the Core Concepts page.
220+
Read more about [Tenant System]({{% ref "/docs/next/guides/concepts#tenant" %}}) on the Core Concepts page.
221221
222222
It is possible to use only one application type within a single tenant namespace.
223223

‎content/en/docs/next/getting-started/create-tenant.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ Each tenant has its own set of applications and one or more nested Kubernetes cl
3939
Tenant users have full access to their clusters.
4040
Optionally, you can configure quotas for each tenant to limit resource usage and prevent overconsumption.
4141

42-
To learn more about tenants, read the [Core Concepts]({{% ref "/docs/next/guides/concepts#tenant-system" %}}) guide.
42+
To learn more about tenants, read the [Core Concepts]({{% ref "/docs/next/guides/concepts#tenant" %}}) guide.
4343

4444

4545
## Create a Tenant

‎content/en/docs/next/install/how-to/single-disk.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ Default Talos setup assumes that each node has a primary and secondary disks, us
1111
However, it's possible to use a single disk, allocating space for user storage.
1212

1313
This configuration must be applied with the first [`talosctl apply`]({{% ref "/docs/next/install/kubernetes/talosctl#3-apply-node-configuration" %}})
14-
or [`talm apply`]({{% ref "/docs/next/install/kubernetes/talm#3-apply-node-configuration" %}})
14+
or [`talm apply`]({{% ref "/docs/next/install/kubernetes/talm#41-apply-configuration-files" %}})
1515
— the one with the `-i` (`--insecure`) flag.
1616
Applying changes after initialization will not have any effect.
1717

‎content/en/docs/next/introduction/_index.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ Here they're bundled and tested to work together seamlessly.
2424
The virtualization platform is also built-in and does not require additional hardware.
2525
Instead, virtual machines run directly inside Kubernetes.
2626

27-
Another powerful feature is the [tenant system]({{% ref "/docs/next/guides/concepts#tenant-system" %}}).
27+
Another powerful feature is the [tenant system]({{% ref "/docs/next/guides/concepts#tenant" %}}).
2828
It allows you to isolate individual developers, teams, or even entire companies in their own fully functional spaces—all on the same hardware.
2929

3030
## Key features
@@ -36,7 +36,7 @@ The traditional approach of assigning each team a dedicated namespace can be too
3636
Teams may need multiple environments with identical namespace names,
3737
or they may lack the root permissions required to manage their own access models.
3838

39-
Cozystack's [tenant system]({{% ref "/docs/next/guides/concepts#tenant-system" %}}) solves these issues
39+
Cozystack's [tenant system]({{% ref "/docs/next/guides/concepts#tenant" %}}) solves these issues
4040
by allowing users to deploy a Kubernetes-in-Kubernetes environment with a single app.
4141
Users of nested Kubernetes clusters have full access and control.
4242
The quota system ensures optimal hardware utilization while isolating resources to prevent the “noisy neighbor” problem.

‎content/en/docs/next/operations/configuration/variants.md‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -48,13 +48,13 @@ or need full manual control over installed packages.
4848
[vm]: {{% ref "/docs/next/virtualization" %}}
4949
[k8s]: {{% ref "/docs/next/kubernetes" %}}
5050
[api]: {{% ref "/docs/next/cozystack-api" %}}
51-
[monitoring subsystem]: {{% ref "/docs/next/guides/platform-stack#victoria-metrics" %}}
52-
[linstor]: {{% ref "/docs/next/guides/platform-stack#drbd" %}}
53-
[kube-ovn]: {{% ref "/docs/next/guides/platform-stack#kube-ovn" %}}
54-
[cilium]: {{% ref "/docs/next/guides/platform-stack#cilium" %}}
55-
[kubevirt]: {{% ref "/docs/next/guides/platform-stack#kubevirt" %}}
56-
[talos linux]: {{% ref "/docs/next/guides/platform-stack#talos-linux" %}}
57-
[kubernetes]: {{% ref "/docs/next/guides/platform-stack#kubernetes" %}}
51+
[monitoring subsystem]: {{% ref "/docs/next/guides/platform-stack#observability" %}}
52+
[linstor]: {{% ref "/docs/next/guides/platform-stack#storage-and-backup" %}}
53+
[kube-ovn]: {{% ref "/docs/next/guides/platform-stack#networking" %}}
54+
[cilium]: {{% ref "/docs/next/guides/platform-stack#networking" %}}
55+
[kubevirt]: {{% ref "/docs/next/guides/platform-stack#cluster-provisioning-and-virtualization" %}}
56+
[talos linux]: {{% ref "/docs/next/guides/platform-stack#operating-system-and-kubernetes-runtime" %}}
57+
[kubernetes]: {{% ref "/docs/next/guides/platform-stack#operating-system-and-kubernetes-runtime" %}}
5858
[kubernetes operators]: https://github.com/cozystack/cozystack/blob/main/packages/core/platform/templates/bundles/paas.yaml
5959

6060
[default]: {{% ref "/docs/next/operations/configuration/variants#default" %}}

‎content/en/docs/next/operations/faq/_index.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ Most cloud providers don't support MetalLB.
4646
Instead of using it, you can expose the main ingress controller using the external IPs method.
4747

4848
For deploying on Hetzner, follow the specialized [Hetzner installation guide]({{% ref "/docs/next/install/providers/hetzner" %}}).
49-
For other providers, follow the [Cozystack installation guide, Public IP Setup]({{% ref "/docs/next/install/cozystack#4b-public-ip-setup" %}}).
49+
For other providers, follow the [Cozystack installation guide, Public IP Setup]({{% ref "/docs/next/install/cozystack/platform#4b-node-public-ip-setup" %}}).
5050

5151
</details>
5252
<br>

‎content/en/docs/v0/development.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -95,7 +95,7 @@ They should not contain business logic, because they are managed by operators in
9595
Similar to `apps` but not shown in the application catalog. They can only be installed as part of a tenant.
9696
They are allowed to use by bottom tenants installed in current tenant namespace.
9797

98-
Read more about [Tenant System](/docs/v0/guides/concepts/#tenant-system) on the Core Concepts page.
98+
Read more about [Tenant System](/docs/v0/guides/concepts/#tenant) on the Core Concepts page.
9999

100100
It is possible to use only one application type within a single tenant namespace.
101101

‎content/en/docs/v0/getting-started/create-tenant.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ Each tenant has its own set of applications and one or more nested Kubernetes cl
4141
Tenant users have full access to their clusters.
4242
Optionally, you can configure quotas for each tenant to limit resource usage and prevent overconsumption.
4343

44-
To learn more about tenants, read the [Core Concepts]({{% ref "/docs/v0/guides/concepts#tenant-system" %}}) guide.
44+
To learn more about tenants, read the [Core Concepts]({{% ref "/docs/v0/guides/concepts#tenant" %}}) guide.
4545

4646

4747
## Create a Tenant

‎content/en/docs/v0/install/how-to/single-disk.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ Default Talos setup assumes that each node has a primary and secondary disks, us
1313
However, it's possible to use a single disk, allocating space for user storage.
1414

1515
This configuration must be applied with the first [`talosctl apply`]({{% ref "/docs/v0/install/kubernetes/talosctl#3-apply-node-configuration" %}})
16-
or [`talm apply`]({{% ref "/docs/v0/install/kubernetes/talm#3-apply-node-configuration" %}})
16+
or [`talm apply`]({{% ref "/docs/v0/install/kubernetes/talm#41-apply-configuration-files" %}})
1717
— the one with the `-i` (`--insecure`) flag.
1818
Applying changes after initialization will not have any effect.
1919

0 commit comments

Comments
 (0)