Repository navigation
fix: isolate invalid origin transport and enforce discovery boundaries - #96
Merged
Merged
Conversation
- dns: require namespace label presence - dns: retain explicit namespace union - dns: exclude invalid origin settings - routing: require TCP backend ports - routing: preserve TCP default behavior - routing: resolve inherited transports - routing: keep scoped failure matches - routing: publish sibling revocations - access: preserve denial precedence - access: exclude unusable dependencies - status: report effective parent errors - status: watch tunnel setting changes - client: reject incompatible schemes - client: check connector service aliases - tests: cover writes and wire validation - tests: exercise grant withdrawal
- e2e: retain a healthy sibling origin - e2e: reject inherited conflicts - e2e: reject HTTPS with h2c enabled - e2e: withdraw backend grants in place - e2e: inspect remote forwarding rules - e2e: verify connector error responses - e2e: keep live certificate coverage - docs: explain scoped transport errors - docs: clarify supported backend ports - docs: distinguish stored and applied - docs: require namespace label presence - docs: preserve named namespace union - docs: describe discovery restrictions - docs: record next upgrade behavior - docs: retain existing cleanup policies
- e2e: keep the HTTP/1 TLS origin usable - e2e: disable its inherited HTTP/2 - e2e: isolate sibling transport errors
- connector: normalize HTTP URL spelling - connector: cover WebSocket origins - connector: cover hello-world aliases - tests: retain matching error responses
|
- routing: retain invalid CA matches - routing: isolate annotation failures - routing: separate match validation - access: keep protected denial ordering - tests: reject public fallthrough - tests: cover malformed origin values - docs: identify the alpha.11 upgrade
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
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.
Changes
An empty namespace label selector incorrectly included namespaces without that label. HTTPRoute backend validation also accepted UDP/SCTP Service ports. This change requires label presence while preserving the union with named namespaces, and requires TCP for HTTP origins.
Effective origin validation now resolves tunnel defaults and route overrides before aggregation. Conflicting HTTP/2+h2c and HTTPS+h2c routes retain scoped HTTP 503 responses while valid siblings and backend revocations continue to publish. Matching Access-required denials keep precedence over public routes. Status, DNS discovery, Access dependency inventory, forwarding fallbacks, and final client validation share these constraints; tunnel changes wake route status reconciliation.
No CRD or dependency changes. The pinned connector's origin validation was inspected, including Unix TLS and both hello-world aliases. Documentation describes changed behavior and distinguishes stored configuration from actual connector application.
Validation
7eebd50: 123 passed, 0 failed, 0 skipped, including teardown (24m40s). The live TLS test confirms healthy sibling responses, invalid transport HTTP503, and withdrawn backend HTTP500 through the connector, alongside stored configuration checks. An earlier deliberately interrupted attempt was normally finalized under a temporary manager, then its owned cluster was removed.The user confirmed release order: cfgate alpha.11 after green review and integration checks, then chart 1.10.0. Chart preparation is tracked in cfgate/helm-chart#26.
Initial Greptile finding: CA-pool validation could skip a route before rendering its denial. Fixed by separating match validation from origin validation and preserving scoped denials for invalid origin annotations; regressions cover CA paths, malformed values and overlapping public forwarding. Final focused controller race tests passed.