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

Add strategy conflict test case #182

Closed
mikenairn opened this issue Jul 8, 2024 · 3 comments
Closed

Add strategy conflict test case #182

mikenairn opened this issue Jul 8, 2024 · 3 comments

Comments

@mikenairn
Copy link
Member

mikenairn commented Jul 8, 2024

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.

@maleck13 maleck13 added this to Kuadrant Jul 8, 2024
@philbrookes philbrookes changed the title Add strategy confllict test case Add strategy conflict test case Jul 11, 2024
@philbrookes philbrookes moved this to Todo in Kuadrant Jul 11, 2024
@maleck13
Copy link
Collaborator

@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?

@mikenairn
Copy link
Member Author

@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.

@maleck13 maleck13 removed the status in Kuadrant Jul 30, 2024
@maksymvavilov
Copy link
Contributor

maksymvavilov commented Sep 6, 2024

the test was added in Kuadrant/kuadrant-operator#699 PR (issue Kuadrant/kuadrant-operator#606 ). During #187, it won't be changed much.
The test creates conflicting policies and makes sure we display errors in statuses of Policies and Records. I'll close this issue as there is not work to be done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

4 participants