Nick Fox

This has been partially completed. The perf cluster script includes creation of a variable number of workloads but not all of the demos are being used and the auto-generated workloads...

Going to close this issue as done. Not all of the demo apps have been deployed but many of the parameters are tunable using the hack perf script.

@amantayal5 sure! From here: https://github.com/kiali/kiali/blob/master/business/authentication/session_persistor_test.go#L53-L59, it looks like the test is checking that the cookie doesn't contain "Foo" to ensure that text actually got encrypted however you can randomly get...

> Any plan to work on this? Yes I opened as a draft initially until the CI is passing.

@Xunzhuo I'm not sure this can be worked on until the UI assets are included in the kiali/kiali repo. There's been some discussion on making that change [here](https://github.com/kiali/kiali/discussions/4587).

Now that the frontend is a part of the kiali repo I don't see any blockers for this

Perhaps a first step for support could be simply respecting the discovery selectors if they exist and `accessible_namespaces` hasn't been set. This default behavior could be used to limit Kiali's...

Thanks for opening this issue. I suspect this is more related to how Kiali uses its service account token and less to do with the particular version of kubeclient Kiali...

The fix for this went out with v1.56 of Kiali if folks want to upgrade their version of Kiali.

> Good topic, the original plan on this was to have these annotations as part of the "implementation" side but from Kiali to allow to "drive" some high level actions...