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
Adding MultiMatch and NoWorkloadFound validations to PeerAuthentication #2808
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
return s.HasWorkloadSelectorLabels() | ||
} | ||
|
||
func getLabels(first, second string, s kubernetes.IstioObject) map[string]string { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor one.
I have started to add more comments in the helpers methods in my PRs as well.
Basically for me, but also it helps others to get more clarity and reduce ambiguity what this helper was necessary.
If you can get a couple of comments about that "first, second" means, perhaps it helps reviewer to not enter in the implementation detail to get it.
@lucasponce comments approached. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM comments approached, QE tested in detailed.
Adding MultiMatch and NoWorkloadFound validations to PeerAuthentication. Both validations has been moved to a common place just to better reuse the code. The validations are quite standard since the "workloadSelector" field is quite standard within Istio CRDs.
Related to #2086
Needs documentation PR: kiali/kiali.io#240
Yamls to reproduce errors: