-
Notifications
You must be signed in to change notification settings - Fork 9
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
Add strategy conflict test case #182
Comments
@mikenairn is there still value in keeping the Kuadrant Operator test but ensuring it is simply validating that the status in the DNSPolicy resource is correct given it is the user facing API? |
I think this should be a test we have in the kuadrant operator DNSPolicy tests even if it is tested at the DNSRecord level in the dns operator suite. |
the test was added in Kuadrant/kuadrant-operator#699 PR (issue Kuadrant/kuadrant-operator#606 ). During #187, it won't be changed much. |
Expand on the test cases to cover expected conflicts such as a load balanced and simple strategy having been used.
Wait until #187 is complete.
The text was updated successfully, but these errors were encountered: