OSM Functionality Updates

[jaiveerk]

Description

This modifies our resource reconciliation when OSM is enabled to avoid a unique edge case encountered during RP e2e testing where client traffic failed to get through to the downstream server due to a failing OSM injector pod.

Fixes # (issue)
Feature # (details)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

RP E2E, with suggestions from the OSM team.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[jaiveerk]

closing after issue was found to be on OSM's side, taking according internal action

[jaiveerk]

/ok-to-test sha=e4552c0

[jaiveerk]

/ok-to-test sha=081ef75

[coveralls]

Pull Request Test Coverage Report for Build 8297498864

Details

• 16 of 16 (100.0%) changed or added relevant lines in 2 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.006%) to 81.258%

---

Totals
Change from base Build 8252883029:	0.006%
Covered Lines:	2558
Relevant Lines:	3148

---

💛 - Coveralls

[jaiveerk]

/ok-to-test sha=452bb8d

[jaiveerk]

/ok-to-test sha=f5d17ca

[jaiveerk]

/ok-to-test sha=9c35174

[jaiveerk]

/ok-to-test sha=65ebf55

[jaiveerk]

/ok-to-test sha=bd3dcd5

[jaiveerk]

/ok-to-test sha=5a986dc

[jaiveerk]

/ok-to-test sha=5b3cd14

[davidgamero]

lgtm