Fix duplicate K8S service ports names #106
Merged
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.
Issue
Jira issues: DPE-1127 and DPE-1378
Solution
Use unique DNS names for each service port (using the same names that are already being used by the primary and replicas k8s services).
Context
The test helpers functions got some new k8s resources added because they were already created before this change, but without the right labels. This PR also fixed it.
Closes #99.
Testing
Tested manually and checked the logs.
Release Notes
Use unique DNS names for each service port.