Skip to content

test(kubernetes): allow expected custom API server error - #14112

Closed
kayx23 wants to merge 1 commit into
apache:release/3.17from
kayx23:test/backport-kubernetes-expected-error-317
Closed

kayx23 wants to merge 1 commit into
apache:release/3.17from
kayx23:test/backport-kubernetes-expected-error-317

Conversation

@kayx23

@kayx23 kayx23 commented Oct 28, 2026

Copy link
Copy Markdown
Member

Why this PR is needed

Kubernetes discovery TEST 3 intentionally configures sample.com:6443 to verify resolved custom/default configuration values. That host is not the API server forwarded by CI, so the informer is expected to log a connection error. The default Test::Nginx no_error_log: [error] assertion makes the test fail depending on when the asynchronous informer attempt lands.

This backports the exact test-only fix from #13701: keep alert-level protection while allowing the expected connection error. Product code and response assertions are unchanged.

#14083 should rebase after this prerequisite merges.

Validation

@kayx23

kayx23 commented Oct 28, 2026

Copy link
Copy Markdown
Member Author

Closing this PR to keep the Admin API migration scoped to documentation and CI environment maintenance. This test-only backport was opened in response to an unrelated flaky check on a documentation PR; the documentation contract remains version-specific and is validated against its own branch sources.

@kayx23 kayx23 closed this Oct 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant