Skip to content

AITRAX-2881: collab README - adopt the hand-applied HTTPRoute too - #231

Merged
danc094codetogether merged 1 commit into
devfrom
aitrax-2881-collab-adopt-route
Nov 9, 2026
Merged

danc094codetogether merged 1 commit into
devfrom
aitrax-2881-collab-adopt-route

Conversation

@CodeTogetherBot

@CodeTogetherBot CodeTogetherBot commented Nov 9, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Follow-up to #229 (AITRAX-2881), README only.

Chart 1.2.9 renders no Gateway API objects, so a Gateway setup on it (Claritev's case) has a hand-applied HTTPRoute as well as the ListenerSet. The README only said to adopt the ListenerSet. Following it, the upgrade to 1.3.0 fails with invalid ownership metadata on the HTTPRoute (it fails without changing anything).

  • The adoption step now covers both listenerset and httproute.
  • It notes that the upgrade keeps serving traffic and keeps the certificate.
  • The rollback warning now names both objects.

Testing

Tested 1.3.0 on k3s 1.34 with Gateway API v1.5.1, NGINX Gateway Fabric 2.8.0 and cert-manager v1.21.3 with ListenerSet support. The Gateway gateway-ngf (kube-system) and ClusterIssuer use the same names as Claritev's cluster.

  • Fresh install with a ListenerSet:
    • ListenerSet Accepted/Programmed and HTTPRoute Accepted/ResolvedRefs.
    • Certificate issued with the right SAN.
    • HTTPS 200 and WebSocket 101 through the Gateway.
  • parentRefs mode: Accepted, HTTP 200.
  • 1.2.9 with a hand-applied ListenerSet and HTTPRoute → 1.3.0 (--reset-then-reuse-values), after adopting both:
    • 251 of 251 requests returned 200, 143 of them during the upgrade.
    • The certificate serial is unchanged.
  • --reuse-values from 1.2.9 without gateway: no new objects.
  • helm rollback to 1.2.9: deletes the ListenerSet and the HTTPRoute.
  • Backend: a WebSocket echo server in the chart's Deployment, because Collab needs an Intel server for its license. The Gateway objects and the Service are the chart's own.
  • Note: NGF closes WebSockets idle for 60s. That is the same default as ingress-nginx, which the charts never changed.

🤖 Generated with Claude Code

Chart 1.2.9 renders no Gateway API objects, so a Gateway setup on it has a
hand-applied HTTPRoute as well as the ListenerSet. Adopting only the
ListenerSet makes the upgrade to 1.3.0 fail with "invalid ownership metadata"
on the HTTPRoute. Found while testing the upgrade on k3s with NGINX Gateway
Fabric 2.8 and cert-manager 1.21: after adopting both, the upgrade served
traffic without errors and kept the certificate.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@danc094codetogether
danc094codetogether merged commit 23a71c2 into dev Nov 9, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants