cleanup(mesh): remove unecessary conditional rendering

With #8197 there are no longer versions of the mesh docs <2.2 so we can remove a list of conditional rendering and make the docs simpler. Part of kumahq/kuma-website#2072 Signed-off-by: Charly Molter <[email protected]>
Kong · Nov 29, 2024 · e3ac1bb · e3ac1bb
1 parent 6ba3469
commit e3ac1bb
Show file tree

Hide file tree

Showing 18 changed files with 16 additions and 736 deletions.
diff --git a/app/_src/.repos/kuma b/app/_src/.repos/kuma
diff --git a/app/_src/mesh/features/acmpca.md b/app/_src/mesh/features/acmpca.md
@@ -20,10 +20,8 @@ using a CA root certificate and key stored in a HashiCorp Vault
 server.
 * `acmpca`: {{site.mesh_product_name}} generates data plane certificates
 using Amazon Certificate Manager Private CA.
-{% if_version gte:1.8.x -%}
 * [`certmanager`](/mesh/{{page.release}}/features/cert-manager/): {{site.mesh_product_name}} generates data plane certificates
 using Kubernetes [cert-manager](https://cert-manager.io) certificate controller.
-{% endif_version %}
 
 ## ACM Private CA mode
 
@@ -147,19 +145,5 @@ You must also make sure the global control plane can communicate with ACM Privat
 {% endif_version %}
 
 <!-- links -->
-{% if_version gte:2.0.x %}
-[mtls-policy]: /mesh/{{page.release}}/policies/mutual-tls/
-{% if_version lte:2.1.x %}
-[secrets]: /mesh/{{page.release}}/security/secrets/
-{% endif_version %}
-{% if_version gte:2.2.x %}
 [secrets]: /mesh/{{page.release}}//production/secure-deployment/secrets/
-{% endif_version %}
 [http-api]: /mesh/{{page.release}}/reference/http-api/
-{% endif_version %}
-
-{% if_version lte:1.9.x %}
-[mtls-policy]: https://kuma.io/docs/1.8.x/policies/mutual-tls/
-[secrets]: https://kuma.io/docs/1.8.x/security/secrets/
-[http-api]: https://kuma.io/docs/1.8.x/reference/http-api
-{% endif_version %}
diff --git a/app/_src/mesh/features/cert-manager.md b/app/_src/mesh/features/cert-manager.md
@@ -122,10 +122,4 @@ In a multi-zone environment, validation is performed on the global control plane
 {% endif_version %}
 
 <!-- links -->
-{% if_version gte:2.0.x %}
 [mtls-policy]: /mesh/{{page.release}}/policies/mutual-tls/
-{% endif_version %}
-
-{% if_version lte:1.9.x %}
-[mtls-policy]: https://kuma.io/docs/1.8.x/policies/mutual-tls/
-{% endif_version %}
diff --git a/app/_src/mesh/features/kds-auth.md b/app/_src/mesh/features/kds-auth.md
@@ -158,25 +158,7 @@ By default, a connection from the zone control plane to the global control plane
 
 You can still authenticate a control plane using the separate [Control Plane Token](/mesh/{{page.release}}/features/kds-auth/), but it is deprecated and will be removed in the future.
 
-<!-- vale off -->
 <!-- links -->
-{% if_version gte:2.0.x %}
-{% if_version lte:2.1.x %}
-[zone-proxy]: /mesh/{{page.release}}/security/zoneproxy-auth/
-[auth]: /mesh/{{page.release}}/security/certificates/#user-to-control-plane-communication
-[certs]: /mesh/{{page.release}}/security/certificates/#control-plane-to-control-plane-multizone
-{% endif_version %}
-{% if_version gte:2.2.x %}
 [zone-proxy]: /mesh/{{page.release}}/production/cp-deployment/zoneproxy-auth
 [auth]: /mesh/{{page.release}}/production/secure-deployment/certificates/#data-plane-proxy-to-control-plane-communication
 [certs]: /mesh/{{page.release}}/production/secure-deployment/certificates/#control-plane-to-control-plane-multizone
-{% endif_version %}
-{% endif_version %}
-
-{% if_version lte:1.9.x %}
-[zone-proxy]: https://kuma.io/docs/1.8.x/security/zone-ingress-auth/
-[auth]: https://kuma.io/docs/1.8.x/security/certificates/#user-to-control-plane-communication
-[certs]: https://kuma.io/docs/1.8.x/security/certificates/#control-plane-to-control-plane-multizone
-{% endif_version %}
-
-<!-- vale on -->