shukitchan opened a new pull request, #389: URL: https://github.com/apache/trafficserver-ingress-controller/pull/389
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. - 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. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
