Conversation
|
Hi @yacut. Thanks for your PR. I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@yacut: The following test failed, say
DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
PR istio#548 for issue istio/istio#18819 by adding excludedWorkloads
|
same change has been made in the PR #556 that moves to the Kiali operator. |
PR istio#548 for issue istio/istio#18819 by adding excludedWorkloads
PR istio#548 for issue istio/istio#18819 by adding excludedWorkloads
|
@yacut I am not really sure what this does. Similar in vein to the comments here #546 (comment) I think we should get out of the third party install business and into the third party integration business (via their operators). Cheers |
|
FWIW: I have included this in the kiali operator integration PR: https://github.com/istio/installer/pull/556/files#diff-d2ae3febaa0204735dffb73c835471ddR88-R91 So the kiali operator integration will have the ability for the user to tell kiali which types of workloads to ignore. We can close this PR once those kiali operator PRs are merged since this PR will not be relevant anymore. |
PR istio#548 for issue istio/istio#18819 by adding excludedWorkloads
related to istio/istio#18819