Making the RemoveEnv method work across all containers in a deployment #1003
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.
Making the RemoveEnv method work across all containers in a deployment, instead asserting there is exactly one container.
What type of PR is this?
/kind failing-test
What does this PR do / why we need it:
When installing gitops-operator-bundle directly through operator sdk, there seems to be more than one container in the deployment. Making the utility function work across all containers makes the code more robust.