[WIP] [TEST] Testing the behaviour when primary container name is different to the one in basePodSpec #6250
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.
Tracking issue
Why are the changes needed?
Add the test to validate the behaviour of
MergePodSpec
is as expected.What changes were proposed in this pull request?
How was this patch tested?
Labels
Please add one or more of the following labels to categorize your PR:
This is important to improve the readability of release notes.
Setup process
Screenshots
Check all the applicable boxes
Related PRs
Docs link
Summary by Bito
Implementation of test cases for MergePodSpec functionality, focusing on container name mismatch scenarios. Tests verify proper merging of container specifications, including volume mounts, environment variables, and tolerations. Changes include improvements in pod_helper_test.go with better formatting and consistent indentation for test assertions.Unit tests added: True
Estimated effort to review (1-5, lower is better): 1