Skip to content

docs: fix broken section anchors across versioned docs #745

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Satvik Mishra (SatvikMishra08) wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: fix broken section anchors across versioned docs #745

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ...nt/en/blog/2024-04-05-diy-create-your-own-cloud-with-kubernetes-part-2/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ project and development team.
Virtual machines are the primary means of isolating tenants from each other in a cloud environment.
In virtual machines, users can execute code and programs with administrative privilege, but this
doesn't affect other tenants or the environment itself. In other words, virtual machines allow to
achieve [hard multi-tenancy isolation]({{% ref "/docs/v1.0/guides/concepts#tenant-system" %}}), and run
achieve [hard multi-tenancy isolation]({{% ref "/docs/v1.0/guides/concepts#tenant" %}}), and run
in environments where tenants do not trust each other.

## Virtualization technologies in Kubernetes
Expand Down
2 changes: 1 addition & 1 deletion content/en/docs/next/development.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -217,7 +217,7 @@ Other examples of this pattern: `extra/ingress`, `extra/seaweedfs`, `extra/monit
Similar to `apps` but not shown in the application catalog. They can only be installed as part of a tenant.
They are allowed to use by bottom tenants installed in current tenant namespace.

Read more about [Tenant System](/docs/guides/concepts/#tenant-system) on the Core Concepts page.
Read more about [Tenant System]({{% ref "/docs/next/guides/concepts#tenant" %}}) on the Core Concepts page.

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

Expand Down
2 changes: 1 addition & 1 deletion content/en/docs/next/getting-started/create-tenant.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ Each tenant has its own set of applications and one or more nested Kubernetes cl
Tenant users have full access to their clusters.
Optionally, you can configure quotas for each tenant to limit resource usage and prevent overconsumption.

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


## Create a Tenant
Expand Down
2 changes: 1 addition & 1 deletion content/en/docs/next/install/how-to/single-disk.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ Default Talos setup assumes that each node has a primary and secondary disks, us
However, it's possible to use a single disk, allocating space for user storage.

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

Expand Down
4 changes: 2 additions & 2 deletions content/en/docs/next/introduction/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ Here they're bundled and tested to work together seamlessly.
The virtualization platform is also built-in and does not require additional hardware.
Instead, virtual machines run directly inside Kubernetes.

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

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

Cozystack's [tenant system]({{% ref "/docs/next/guides/concepts#tenant-system" %}}) solves these issues
Cozystack's [tenant system]({{% ref "/docs/next/guides/concepts#tenant" %}}) solves these issues
by allowing users to deploy a Kubernetes-in-Kubernetes environment with a single app.
Users of nested Kubernetes clusters have full access and control.
The quota system ensures optimal hardware utilization while isolating resources to prevent the “noisy neighbor” problem.
Expand Down
14 changes: 7 additions & 7 deletions content/en/docs/next/operations/configuration/variants.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,13 +48,13 @@ or need full manual control over installed packages.
[vm]: {{% ref "/docs/next/virtualization" %}}
[k8s]: {{% ref "/docs/next/kubernetes" %}}
[api]: {{% ref "/docs/next/cozystack-api" %}}
[monitoring subsystem]: {{% ref "/docs/next/guides/platform-stack#victoria-metrics" %}}
[linstor]: {{% ref "/docs/next/guides/platform-stack#drbd" %}}
[kube-ovn]: {{% ref "/docs/next/guides/platform-stack#kube-ovn" %}}
[cilium]: {{% ref "/docs/next/guides/platform-stack#cilium" %}}
[kubevirt]: {{% ref "/docs/next/guides/platform-stack#kubevirt" %}}
[talos linux]: {{% ref "/docs/next/guides/platform-stack#talos-linux" %}}
[kubernetes]: {{% ref "/docs/next/guides/platform-stack#kubernetes" %}}
[monitoring subsystem]: {{% ref "/docs/next/guides/platform-stack#observability" %}}
[linstor]: {{% ref "/docs/next/guides/platform-stack#storage-and-backup" %}}
[kube-ovn]: {{% ref "/docs/next/guides/platform-stack#networking" %}}
[cilium]: {{% ref "/docs/next/guides/platform-stack#networking" %}}
[kubevirt]: {{% ref "/docs/next/guides/platform-stack#cluster-provisioning-and-virtualization" %}}
[talos linux]: {{% ref "/docs/next/guides/platform-stack#operating-system-and-kubernetes-runtime" %}}
[kubernetes]: {{% ref "/docs/next/guides/platform-stack#operating-system-and-kubernetes-runtime" %}}
[kubernetes operators]: https://github.com/cozystack/cozystack/blob/main/packages/core/platform/templates/bundles/paas.yaml

[default]: {{% ref "/docs/next/operations/configuration/variants#default" %}}
Expand Down
2 changes: 1 addition & 1 deletion content/en/docs/next/operations/faq/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@ Most cloud providers don't support MetalLB.
Instead of using it, you can expose the main ingress controller using the external IPs method.

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

</details>
<br>
Expand Down
2 changes: 1 addition & 1 deletion content/en/docs/v0/development.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -95,7 +95,7 @@ They should not contain business logic, because they are managed by operators in
Similar to `apps` but not shown in the application catalog. They can only be installed as part of a tenant.
They are allowed to use by bottom tenants installed in current tenant namespace.

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

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

Expand Down
2 changes: 1 addition & 1 deletion content/en/docs/v0/getting-started/create-tenant.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ Each tenant has its own set of applications and one or more nested Kubernetes cl
Tenant users have full access to their clusters.
Optionally, you can configure quotas for each tenant to limit resource usage and prevent overconsumption.

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


## Create a Tenant
Expand Down
2 changes: 1 addition & 1 deletion content/en/docs/v0/install/how-to/single-disk.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ Default Talos setup assumes that each node has a primary and secondary disks, us
However, it's possible to use a single disk, allocating space for user storage.

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

Expand Down
2 changes: 1 addition & 1 deletion content/en/docs/v0/install/providers/hetzner.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -165,7 +165,7 @@ but has instructions and examples specific to Hetzner.

A bunch of files is now created in the `hetzner-cluster` directory.
To learn more about the role of each file, refer to the
[Talm guide]({{% ref "/docs/v0/install/kubernetes/talm#1-initialize-cluster-configuration" %}}).
[Talm guide]({{% ref "/docs/v0/install/kubernetes/talm#2-initialize-cluster-configuration" %}}).

1. Edit `values.yaml`, modifying the following values:

Expand Down
4 changes: 2 additions & 2 deletions content/en/docs/v0/introduction/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ Here they're bundled and tested to work together seamlessly.
The virtualization platform is also built-in and does not require additional hardware.
Instead, virtual machines run directly inside Kubernetes.

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

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

Cozystack's [tenant system]({{% ref "/docs/v0/guides/concepts#tenant-system" %}}) solves these issues
Cozystack's [tenant system]({{% ref "/docs/v0/guides/concepts#tenant" %}}) solves these issues
by allowing users to deploy a Kubernetes-in-Kubernetes environment with a single app.
Users of nested Kubernetes clusters have full access and control.
The quota system ensures optimal hardware utilization while isolating resources to prevent the “noisy neighbor” problem.
Expand Down
2 changes: 1 addition & 1 deletion content/en/docs/v0/operations/configuration/bundles.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ or just need a minimal Kubernetes cluster.
[k8s]: {{% ref "/docs/v0/kubernetes" %}}
[api]: {{% ref "/docs/v0/cozystack-api" %}}
[monitoring subsystem]: {{% ref "/docs/v0/guides/platform-stack#victoria-metrics" %}}
[linstor]: {{% ref "/docs/v0/guides/platform-stack#drbd" %}}
[linstor]: {{% ref "/docs/v0/guides/platform-stack#drbd-and-linstor" %}}
[kube-ovn]: {{% ref "/docs/v0/guides/platform-stack#kube-ovn" %}}
[cilium]: {{% ref "/docs/v0/guides/platform-stack#cilium" %}}
[kubevirt]: {{% ref "/docs/v0/guides/platform-stack#kubevirt" %}}
Expand Down
2 changes: 1 addition & 1 deletion content/en/docs/v0/operations/faq/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@ Most cloud providers don't support MetalLB.
Instead of using it, you can expose the main ingress controller using the external IPs method.

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

</details>
<br>
Expand Down
2 changes: 1 addition & 1 deletion content/en/docs/v1.0/development.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -217,7 +217,7 @@ Other examples of this pattern: `extra/ingress`, `extra/seaweedfs`, `extra/monit
Similar to `apps` but not shown in the application catalog. They can only be installed as part of a tenant.
They are allowed to use by bottom tenants installed in current tenant namespace.

Read more about [Tenant System](/docs/guides/concepts/#tenant-system) on the Core Concepts page.
Read more about [Tenant System]({{% ref "/docs/v1.0/guides/concepts#tenant" %}}) on the Core Concepts page.

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

Expand Down
2 changes: 1 addition & 1 deletion content/en/docs/v1.0/getting-started/create-tenant.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ Each tenant has its own set of applications and one or more nested Kubernetes cl
Tenant users have full access to their clusters.
Optionally, you can configure quotas for each tenant to limit resource usage and prevent overconsumption.

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


## Create a Tenant
Expand Down
2 changes: 1 addition & 1 deletion content/en/docs/v1.0/install/how-to/single-disk.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ Default Talos setup assumes that each node has a primary and secondary disks, us
However, it's possible to use a single disk, allocating space for user storage.

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

Expand Down
2 changes: 1 addition & 1 deletion content/en/docs/v1.0/install/providers/hetzner.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -161,7 +161,7 @@ but has instructions and examples specific to Hetzner.

A bunch of files is now created in the `hetzner-cluster` directory.
To learn more about the role of each file, refer to the
[Talm guide]({{% ref "/docs/v1.0/install/kubernetes/talm#1-initialize-cluster-configuration" %}}).
[Talm guide]({{% ref "/docs/v1.0/install/kubernetes/talm#2-initialize-cluster-configuration" %}}).

1. Edit `values.yaml`, modifying the following values:

Expand Down
4 changes: 2 additions & 2 deletions content/en/docs/v1.0/introduction/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ Here they're bundled and tested to work together seamlessly.
The virtualization platform is also built-in and does not require additional hardware.
Instead, virtual machines run directly inside Kubernetes.

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

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

Cozystack's [tenant system]({{% ref "/docs/v1.0/guides/concepts#tenant-system" %}}) solves these issues
Cozystack's [tenant system]({{% ref "/docs/v1.0/guides/concepts#tenant" %}}) solves these issues
by allowing users to deploy a Kubernetes-in-Kubernetes environment with a single app.
Users of nested Kubernetes clusters have full access and control.
The quota system ensures optimal hardware utilization while isolating resources to prevent the “noisy neighbor” problem.
Expand Down
2 changes: 1 addition & 1 deletion content/en/docs/v1.0/operations/configuration/variants.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ or need full manual control over installed packages.
[k8s]: {{% ref "/docs/v1.0/kubernetes" %}}
[api]: {{% ref "/docs/v1.0/cozystack-api" %}}
[monitoring subsystem]: {{% ref "/docs/v1.0/guides/platform-stack#victoria-metrics" %}}
[linstor]: {{% ref "/docs/v1.0/guides/platform-stack#drbd" %}}
[linstor]: {{% ref "/docs/v1.0/guides/platform-stack#drbd-and-linstor" %}}
[kube-ovn]: {{% ref "/docs/v1.0/guides/platform-stack#kube-ovn" %}}
[cilium]: {{% ref "/docs/v1.0/guides/platform-stack#cilium" %}}
[kubevirt]: {{% ref "/docs/v1.0/guides/platform-stack#kubevirt" %}}
Expand Down
2 changes: 1 addition & 1 deletion content/en/docs/v1.0/operations/faq/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@ Most cloud providers don't support MetalLB.
Instead of using it, you can expose the main ingress controller using the external IPs method.

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

</details>
<br>
Expand Down
2 changes: 1 addition & 1 deletion content/en/docs/v1.1/development.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -217,7 +217,7 @@ Other examples of this pattern: `extra/ingress`, `extra/seaweedfs`, `extra/monit
Similar to `apps` but not shown in the application catalog. They can only be installed as part of a tenant.
They are allowed to use by bottom tenants installed in current tenant namespace.

Read more about [Tenant System](/docs/guides/concepts/#tenant-system) on the Core Concepts page.
Read more about [Tenant System]({{% ref "/docs/v1.1/guides/concepts#tenant" %}}) on the Core Concepts page.

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

Expand Down
2 changes: 1 addition & 1 deletion content/en/docs/v1.1/getting-started/create-tenant.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ Each tenant has its own set of applications and one or more nested Kubernetes cl
Tenant users have full access to their clusters.
Optionally, you can configure quotas for each tenant to limit resource usage and prevent overconsumption.

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


## Create a Tenant
Expand Down
2 changes: 1 addition & 1 deletion content/en/docs/v1.1/install/how-to/single-disk.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ Default Talos setup assumes that each node has a primary and secondary disks, us
However, it's possible to use a single disk, allocating space for user storage.

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

Expand Down
2 changes: 1 addition & 1 deletion content/en/docs/v1.1/install/providers/hetzner.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -161,7 +161,7 @@ but has instructions and examples specific to Hetzner.

A bunch of files is now created in the `hetzner-cluster` directory.
To learn more about the role of each file, refer to the
[Talm guide]({{% ref "/docs/v1.1/install/kubernetes/talm#1-initialize-cluster-configuration" %}}).
[Talm guide]({{% ref "/docs/v1.1/install/kubernetes/talm#2-initialize-cluster-configuration" %}}).

1. Edit `values.yaml`, modifying the following values:

Expand Down
4 changes: 2 additions & 2 deletions content/en/docs/v1.1/introduction/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ Here they're bundled and tested to work together seamlessly.
The virtualization platform is also built-in and does not require additional hardware.
Instead, virtual machines run directly inside Kubernetes.

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

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

Cozystack's [tenant system]({{% ref "/docs/v1.1/guides/concepts#tenant-system" %}}) solves these issues
Cozystack's [tenant system]({{% ref "/docs/v1.1/guides/concepts#tenant" %}}) solves these issues
by allowing users to deploy a Kubernetes-in-Kubernetes environment with a single app.
Users of nested Kubernetes clusters have full access and control.
The quota system ensures optimal hardware utilization while isolating resources to prevent the “noisy neighbor” problem.
Expand Down
2 changes: 1 addition & 1 deletion content/en/docs/v1.1/operations/configuration/variants.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ or need full manual control over installed packages.
[k8s]: {{% ref "/docs/v1.1/kubernetes" %}}
[api]: {{% ref "/docs/v1.1/cozystack-api" %}}
[monitoring subsystem]: {{% ref "/docs/v1.1/guides/platform-stack#victoria-metrics" %}}
[linstor]: {{% ref "/docs/v1.1/guides/platform-stack#drbd" %}}
[linstor]: {{% ref "/docs/v1.1/guides/platform-stack#drbd-and-linstor" %}}
[kube-ovn]: {{% ref "/docs/v1.1/guides/platform-stack#kube-ovn" %}}
[cilium]: {{% ref "/docs/v1.1/guides/platform-stack#cilium" %}}
[kubevirt]: {{% ref "/docs/v1.1/guides/platform-stack#kubevirt" %}}
Expand Down
2 changes: 1 addition & 1 deletion content/en/docs/v1.1/operations/faq/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@ Most cloud providers don't support MetalLB.
Instead of using it, you can expose the main ingress controller using the external IPs method.

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

</details>
<br>
Expand Down
Loading