test(8.10): add CI integration test scenarios for gateway namespace feature#6243
Draft
hisImminence wants to merge 9 commits into
Draft
test(8.10): add CI integration test scenarios for gateway namespace feature#6243hisImminence wants to merge 9 commits into
hisImminence wants to merge 9 commits into
Conversation
…ateway parentRefs HTTPRoutes and GRPCRoutes created by the chart never included a namespace field in their parentRefs. When omitted, Kubernetes assumes the Gateway is in the same namespace as the Route, which breaks setups where a shared Gateway lives in a different namespace (for example, a shared-infra namespace). Adds global.gateway.namespace to values.yaml and values.schema.json, plumbs it into parentRefs in all seven Route templates, and adds four test cases per template covering: namespace set, namespace unset, namespace + TLS, and external mode with namespace set. Closes #6167 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…tRefs Without a configurable Gateway name, parentRefs in every Route was hardcoded to the Helm release fullname. In cross-namespace setups the shared Gateway almost certainly has a different name, making global.gateway.namespace insufficient on its own. Adds global.gateway.name (defaults to release fullname for backward compat), plumbs it into parentRefs across all seven Route templates and the Gateway resource itself, and adds a test case per template verifying a custom name is rendered. Also drops the erroneous require.NoError from the external=true not-rendered test cases, which was wrong: chart constraint validation fires even when external=true, producing expected non-feature errors. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…parentRef name in tests Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Gate namespace+createGatewayResource constraint on gateway.enabled so inert value combinations don't fail helm template - Add Keycloak+namespace identity HTTPRoute test to cover Keycloak parentRef path - Add TestGatewayCustomName test (createGatewayResource=true + gateway.name) - Fix TLS sectionName docs: https (HTTPRoutes) vs grpcs (GRPCRoute) in values.yaml, values.schema.json, and README.md Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…isting CI scenarios Adds three new integration test scenarios to ci-test-config.yaml covering the gateway feature modes introduced by the gateway.namespace PR: - gateway-keycloak (gatkc): baseline gateway scenario with Keycloak auth; uses a post-deploy fixture to apply the NGINX ProxySettingsPolicy. - gateway-cross-namespace (gatxn): exercises global.gateway.namespace by deploying Routes that reference a shared Gateway in camunda-gateway-shared, pre-created by pre-install-gateway-cross-namespace.sh. - gateway-existing (gatex): exercises createGatewayResource=false with a pre-created Gateway fixture (gateway-prereq.yaml), proving that the chart can attach Routes to an externally-managed Gateway. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
… scenarios
Moves gateway-cross-namespace and gateway-existing out of the main
ci-test-config.yaml into a new ci-reference-scenarios.yaml alongside all
three Gateway API scenarios (including gateway-keycloak already in main).
Reference scenarios never run in PR or merge-queue CI — they exist for
incident reproduction and feature-specific validation.
Adds --ci-config flag to deploy-camunda matrix list/run to point at any
ci-test-config-compatible file in the chart's test/ directory:
deploy-camunda matrix run \
--ci-config ci-reference-scenarios.yaml \
--shortname-filter gatxn \
--repo-root <path>
LoadCITestConfig now accepts an optional filename override (variadic);
all existing callers are unaffected. The orphan-check test is extended to
also scan ci-reference-scenarios.yaml so reference scenario assets are not
reported as orphans.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Ian-wang-liyang
force-pushed
the
gatewayapi-namespace
branch
4 times, most recently
from
a5a307f to
2cd2df4
Compare
41 tasks
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
1 participant
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
Stacks on top of #6174. Introduces a
ci-reference-scenarios.yamlpattern for Gateway API scenarios that are too specific to run in regular PR or merge-queue CI, but are valuable to keep as validated, runnable configurations for incident reproduction and feature-specific testing.Reference scenarios (never run automatically):
Infrastructure changes:
Run a reference scenario on demand:
```
deploy-camunda matrix run
--ci-config ci-reference-scenarios.yaml
--scenario-filter gateway-cross-namespace
--repo-root
```
Test plan
Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com