Feat(Mesh): Mutual TLS

.claude/skills/kuma-to-mesh/SKILL.md

@@ -50,9 +50,9 @@ Check whether the target file already exists. If it does, show the user the exis
 
 Do NOT add anything to the `/mesh/policies/` folder. For example, `/mesh/policies/mutual-tls.md` should be migrated to `/mesh/mutual-tls.md`.
 
-If the URL changes as a result, add a redirect in `app/_redirects` under "Mesh redirects", for example:
-```
-/mesh/policies/mutual-tls/ /mesh/mutual-tls/
+If the URL changes as a result, set a permalink. For example:
+```yaml
+permalink: /mesh/policies/mutual-tls/
 ```
 
 ---
@@ -125,6 +125,8 @@ Apply these verbatim substitutions anywhere they appear in link targets:
 - `/policies/` → `/mesh/policies/`
 - `/features/` → `/mesh/enterprise/`
 
+When replacing relative links, check against https://developer.konghq.com/ that the URL doesn't return a 404 and that the anchor exists.
+
 ### 5d. Prose "Kuma" replacement
 In body text (not inside code blocks, YAML examples, or annotations):
 - Replace standalone `Kuma` (the product name) with `{{site.mesh_product_name}}`

app/_data/kuma_to_mesh/config.yaml

@@ -31,16 +31,6 @@ pages:
         url: /mesh/service-mesh/
     min_version:
       mesh: '2.7'
-  -
-    path: app/_src/policies/mutual-tls.md
-    title: 'Configuring Mutual TLS'
-    description: 'Configuring Mutual TLS for your workloads'
-    url: '/mesh/policies/mutual-tls/'
-    related_resources:
-      - text: MeshTLS Policy
-        url: /mesh/policies/meshtls/
-    min_version:
-      mesh: '2.9'
   -
     path: app/_src/introduction/concepts.md
     title: 'Concepts'

app/mesh/manage-secrets.md

@@ -101,7 +101,7 @@ echo "value" | base64
 ### Mesh-scoped secrets
 
 Mesh-scoped secrets are bound to a given mesh.
-This is the only type of secret that can be used in mesh policies like the [Provided CA](/mesh/policies/mutual-tls/#usage-of-provided-ca) or TLS setting in [External Service](/mesh/policies/external-services/).
+This is the only type of secret that can be used in mesh policies like the [Provided CA](/mesh/policies/mutual-tls/#using-a-provided-ca) or TLS setting in [External Service](/mesh/policies/external-services/).
 
 {% navtabs "Environments" %}
 {% navtab "Kubernetes" %}
@@ -175,7 +175,7 @@ Secrets are synced from the global control plane to the zones CPs, but not the o
 
 ## Using secrets
 
-Here is an example of how to use a {{site.mesh_product_name}} `Secret` with a `provided` [Mutual TLS](/mesh/policies/mutual-tls/#usage-of-provided-ca) backend.
+Here is an example of how to use a {{site.mesh_product_name}} `Secret` with a `provided` [Mutual TLS](/mesh/policies/mutual-tls/#using-a-provided-ca) backend.
 
 The examples below assume that the `Secret` object has already been created: