Repository navigation
AITRAX-2881: collab README - adopt the hand-applied HTTPRoute too - #231
Merged
Merged
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 metadataon the HTTPRoute (it fails without changing anything).listenersetandhttproute.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.parentRefsmode: Accepted, HTTP 200.--reset-then-reuse-values), after adopting both:--reuse-valuesfrom 1.2.9 withoutgateway: no new objects.helm rollbackto 1.2.9: deletes the ListenerSet and the HTTPRoute.🤖 Generated with Claude Code