Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure test-app deployments have unique labels per scenario #74

Merged
merged 1 commit into from
Oct 12, 2023

Conversation

sadlerap
Copy link
Contributor

Previously, since every deployment of the generic test app had the same label, the services we would make as a part of testing would forward requests to any running deployment since they could match the label selector. Make them unique, so that requests get forwarded to the correct pod.

Previously, since every deployment of the generic test app had the same
label, the services we would make as a part of testing would forward
requests to any running deployment since they could match the label
selector.  Make them unique, so that requests get forwarded to the
correct pod.

Signed-off-by: Andy Sadler <[email protected]>
@sadlerap
Copy link
Contributor Author

This should fix #64.

@sadlerap
Copy link
Contributor Author

sadlerap commented Oct 4, 2023

The one test that's failing is an upstream bug which is in the process of being fixed.

@scothis
Copy link
Member

scothis commented Oct 12, 2023

Validated to work with servicebinding/runtime#348

@scothis scothis merged commit e3b7a69 into servicebinding:main Oct 12, 2023
1 of 2 checks passed
@sadlerap sadlerap deleted the fix-deployment-labels branch October 12, 2023 16:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

404 Error loading bound value after successfully loading a different value
2 participants