[ci] refactor k8s integration tests to pre-render kustomize manifest #8550
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.





What does this PR do?
This PR refactors the Kubernetes integration tests by pre-rendering the Kustomize manifest before test execution. The key changes include:
TestMain: This ensures Kustomize manifests are rendered once before all tests run, avoiding repeated work in every test case.--integration.k8s.skip-kustomize-testsflag: Allows skipping Kustomize-based tests when necessary (e.g., local test runs or CI constraints).k8sRenderKustomizelogic: This logic is now centralized and retried with backoff usingcenkalti/backoff/v5.skip(t *testing.T)function to allow dynamic skipping logic.Why is it important?
Reduces test flakiness: Previously, each test independently rendered the Kustomize YAML, which involved fetching resources such as
kube-state-metricsmanifests from GitHub. This led to transient test failures due to network instability or GitHub rate limiting. By rendering the manifest once during test setup with retry logic, we reduce (but do not eliminate) this source of flakiness.Checklist
./changelog/fragmentsusing the changelog toolDisruptive User Impact
None expected. This change only affects internal integration test infrastructure and does not impact users or production functionality.
How to test this PR locally
Related issues