Fix resource name mismatch in application update test - #1496
Merged
devdattakulkarni merged 1 commit intoAug 20, 2026
Merged
Conversation
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.
Problem
test_application_updategenerated different resource names for the initial and replica update manifestsAs a result,
kubectl replaceattempts to update a HelloWorldService that was never created and fails with aNotFounderror.Fix
Allow
_process_template()to accept an optional resource name and reuse the originalhs1_namewhen generating the replicas update manifest.This ensures both manifests refer to the same HelloWorldService resource.