Martin Ostrowski
Martin Ostrowski
Hi Nick, The work involved in implementing this should not be very much, but the trick is to understand how to integrate it into the exiting code. Unfortunately the complexity...
sgtm, my only suggestion would be to consider IgnorePaths since this may be a more common scenario? i.e. validate all refs _except_ these ones I'm excluding.
@richardwxn please move this pr to istio/istio.
We need to create the namespace to accommodate a single line install. There's just no way around it. The current check in the code is insufficient - what if a...
@howardjohn there are good reasons for keeping the operator and ICP in a separate ns from Istio, namely creating an administrative boundary and making it easy to uninstall operator without...
Rob, what's the motivation for putting the ICP CR in istio-system? It's possible to create rbac that restricts a user from touching anything other than ICP CR in either ns.
Apologies in advance if I'm missing something obvious as security is not my forte. Just trying to understand your proposal better. I have no objection to moving the CR out...
The operator already supports the CR being in any namespace the admin doing the install chooses. I'm still wondering why that should be istio-system today, given that we're trying to...
I completely agree that for multi-tenant and/or managed case it makes sense not have the CR in istio-operator. I do still wonder why the cluster admin would install a managed...
This repo is inactive and out of date - see istio/istio/manifests instead.