Move docs YAML validation to lightweight docs-lint workflow#1178
Open
Move docs YAML validation to lightweight docs-lint workflow#1178
Conversation
fa042c2 to
6dab5ca
Compare
The docs YAML validation doesn't need a full KIND cluster — it only needs CRDs for server-side dry-run. Move it to the existing docs-lint workflow as a separate job that: - Installs CRDs via kubectl apply (no KIND needed) - Validates standalone and inline YAML examples - Runs in ~30 seconds vs 20+ minutes for full e2e This avoids triggering the slow e2e suite for doc-only changes. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Aarno Aukia <aarno.aukia@vshn.ch>
6dab5ca to
4633f66
Compare
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.
Summary
Move the docs YAML validation out of the e2e suite into the existing
docs-lint.ymlworkflow as a separate lightweight job:docs/**changes--dry-run=servertest-99-docs-examples.batsfrom the e2e suiteWhy
Doc-only PRs don't need the full e2e test infrastructure. The previous approach ran docs validation as part of the 20-minute e2e suite, which was slow and often hit flaky test failures unrelated to docs.
Relates-to: #1101
Test plan
🤖 Generated with Claude Code