microsoft.genpolicy: drop revert tarindex symlink handling patch #667
Conversation
This file contains 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
Signed-off-by: Paul Meyer <[email protected]>
burgerdev
approved these changes
Jul 3, 2024
|
Successfully created backport PR for |
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.
Using
3.2.0.azl1.genpolicy0version incontrast generateandAKSCBLMariner-V2katagen2-202406.07.0as AKS node image, symlinks with special names would cause a policy mismatch between the deployed tardev-snapshotter service of the image and the policies generated by Contrast, resulting in workload pods not starting, see #624.As consequence, we applied a patch to revert the commit in genpolicy that caused the mismatch.
Given
AKSCBLMariner-V2katagen2-202406.19.0as node image, the tardev-snapshotter is updated to the new behavior so that we need to drop our patch again to get matching policies.