fix(ci): apply cr in nested cluster#2319
Merged
Merged
Conversation
Signed-off-by: Nikita Korolev <nikita.korolev@flant.com>
1235732 to
08bfd52
Compare
diafour
approved these changes
May 5, 2026
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.
Description
Add retry logic around
kubectl applycalls in the nested E2EConfigure Virtualizationstep.The workflow now writes the manifest received from stdin to a temporary file and retries the same
kubectl applycommand several times before failing. This covers transient Kubernetes API or DNS failures while applyingModuleSource,ModuleConfig, andModulePullOverrideresources.Why do we need it, and what problem does it solve?
The nested E2E pipeline can fail during Virtualization configuration when
kubectl applycannot reach the cluster API long enough to download the OpenAPI schema. This is a transient infrastructure/connectivity issue, but it currently fails the whole CI run immediately.Example failure:
Retrying the apply operation gives the nested cluster a chance to recover from short DNS/API hiccups without disabling manifest validation.
What is the expected result?
Configure Virtualizationstep.kubectl applyinstead of failing on the first transient error.Checklist
Changelog entries