Krzysztof Słonka

WIP ### Checklist prior to review - [ ] [Link to relevant issue][1] as well as docs and UI issues -- - [ ] This will not break child repos:...

After applying `MeshTcpRoute` health checks disappear and traffic starts to be routed to unhealthy service

2

### What happened? Coming from slack: https://kuma-mesh.slack.com/archives/CN2GN4HE1/p1724414616702329 1. Yep, my policies. ``` type: MeshHealthCheck name: web-to-redis-check mesh: default spec: targetRef: kind: Mesh to: - targetRef: kind: MeshService name: redis_kuma-demo_svc_6379 default:...

### Description I don't think we ever tested it.

Combating flakes in our codebase

8

### Description While being on-duty and trying to reproduce flakes I thought of a couple of things that we could do to improve fighting flakes in our codebase (CI /...

Check if retry on DeleteMeshResources improved `build-test-ditribute` stability and figure out the root cause

1

### Description https://github.com/kumahq/kuma/pull/10189 - need to understand if it helped and then why it helped.

### Description We should have the possibility to configure MeshCircuitBreaker.

### What happened? continuation from https://github.com/kumahq/kuma/issues/4622 details TBD.

Deprecate `UnixDomainPath` in MeshExternalService

1

### What happened? Does it still make sense to have `UnixDomainPath` when we route only through egress?

Rewrite meshhttproute/meshexternalservice tests to output egress configuration

1

### Description Continuation from https://github.com/kumahq/kuma/pull/11080#discussion_r1721598871 - we cut scope there to focus on MeshTLS.

feat(meshtls): initial guide

5

closes https://github.com/kumahq/kuma-website/issues/1897 rendered: https://deploy-preview-1906--kuma.netlify.app/docs/dev/guides/progressively-rolling-in-strict-mtls/ Did you sign your commit? [Instructions](https://github.com/kumahq/.github/blob/main/CONTRIBUTING.md#sign-your-commits) yes Have you read [Contributing guidelines](https://github.com/kumahq/.github/blob/main/CONTRIBUTING.md)? yes