domains / families / devops / ai-inference-service-mesh

ai-inference-service-mesh

combined

Use service mesh patterns for AI inference traffic management, mTLS, canary releases, policy enforcement, and cross-cluster resilience. Use verified service mesh patterns for AI inference traffic management, mTLS,

When to use

• Design or troubleshoot mTLS identity, model-version routing, inference retry budgets, mesh egress or observable latency on an actual supported cluster.

When not to use

• Infrastructure commands can disrupt services: confirm target host/scope and have backups/snapshots before mutating state.
• Docs-only import: upstream scripts and templates not bundled.

Skill page

Conflict

The sickn33 copy is a mirror of the BagelHole copy (it explicitly cites BagelHole as the source) but it adds material safety constraints and corrections that the original lacks. The original presents the egress policy as a complete firewall and includes a DestinationRule that originates TLS for an external HTTPS host, which the mirror explicitly warns against (double TLS breaks the connection). The mirror also adds a prerequisite to confirm cluster context, mesh version, and CRD schemas, and warns that multiple DestinationRules for the same host must be consolidated. Because the mirror corrects a real operational hazard in the original, crowning the original would hide a safer alternative, so the copies should be combined.