Thomas Shafer

I don't think it can reliably be used from the image tag. Similarly how users can change the format of the image digest in the operator using the `KnativeServing` CRD,...

If we support Option 1, does that also mean we support a way to install the operator without it automatically installing knative-serving? Or is the idea that if the operator...

@vincent-pli The current flow (Option 1) supports this flow. The user creates the `KnativeServing` CRD, then creates the `KnativeServing` CR with a custom registry configuration. Then they finally apply the...

If there's a flag called `no-install` or similar, should this actively delete the knative-serving resources, or should it just make the operator noop, not delete or install? One possible issue...

/assign cynocracy

It was inspired from the 0.6 -> 0.9 (I think) upgrade. It was a migration from clusterroute to route IIRF. Users needed to migrate from 0.6 -> 0.7 or 0.8...

0.6->.8 and then .9 is probably fine. or if jumping from 0.6 -> 0.12 then have 0.6 -> 0.8 -> 0.10 -> 0.12.

I believe deleting the `KnativeServing` CR will delete the resources in the serving.yaml, however it will not delete knative-build or istio work. I'll double check on deleting the CR.

Thanks @jcrossley3

Hey @juanmnl , there is not currently an official way. It's stored in `state.visible`. Technically it's available via `this.refs.Typeahead.state.visible`, assuming your component has ref Typeahead. But I wouldn't recommend that....