expose-zymtrace-backend

What problem does it solve?

This Skill helps you expose an already-installed zymtrace backend to users and agents by configuring Kubernetes network exposure (NodePort, LoadBalancer, or Ingress) with correct TLS and controller-specific settings, so the gateway becomes reachable and functional.

Core Features & Use Cases

• Helm-based exposure changes: Edits the customer’s canonical Helm values file in place and applies it via helm upgrade --install.
• Multiple exposure modes with safe defaults: Supports NodePort, NGINX Ingress + cert-manager TLS, and AWS ALB + ACM TLS (with hostname and scheme handling).
• Controller-correct protocol configuration: Ensures gRPC behavior works by using backend-protocol: "GRPC" for NGINX and the required ALB HTTP/HTTP2 pairing to avoid the HTTP 464 failure mode.
• Verification and rollout confidence: Runs a verification script to confirm ingress/service address, TLS reachability, and gateway health/gRPC behavior.

Quick Start

Tell the Skill: which exposure mode you want (NodePort, NGINX Ingress, or AWS ALB), the target namespace and release name, the gateway hostname, and the TLS source (ACM ARN for ALB or cert-manager issuer/secret for NGINX).