Repository navigation
Make integration fixtures respect per-namespace hostname ownership - #389
Merged
Merged
Conversation
Since apache#382 a hostname is owned by the first namespace whose Ingress claims it, and routes for that hostname from other namespaces are skipped. The integration fixtures shared test.edge.com between trafficserver-test-2 and trafficserver-test-3, and test.media.com between trafficserver-test-2 and cache-test-ns, so the controller dropped test.edge.com/app1 and test.media.com/cache-test and ATS answered ERR_INVALID_URL/404. test_basic_routing_edge_app1, test_cache_app1 and test_cache_app1_beyond_ttl failed as a result. - Give test.edge.com entirely to trafficserver-test-3: add the /app1 route to its Ingress (and to the snippet variant) and remove the test.edge.com rules from every trafficserver-test-2 Ingress. - Give the caching app its own hostname, test.cache.com. The caching policy matches on URL path only, so it still applies. - Dump the controller container logs during setup so rejected host claims are visible in CI output. - Document the hostname ownership rule in the tutorial. Co-Authored-By: Claude Fable 5.1 <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.
Since #382 a hostname is owned by the first namespace whose Ingress claims it, and routes for that hostname from other namespaces are skipped. The integration fixtures shared test.edge.com between trafficserver-test-2 and trafficserver-test-3, and test.media.com between trafficserver-test-2 and cache-test-ns, so the controller dropped test.edge.com/app1 and test.media.com/cache-test and ATS answered ERR_INVALID_URL/404. test_basic_routing_edge_app1, test_cache_app1 and test_cache_app1_beyond_ttl failed as a result.