- the actual code is in pkg/install - including a readiness probe, monitoring.
    - it also sets up a UDS socket for istio-cni to send logs to this container.
    - based on config, it may run the 'repair' controller that detects pods where istio setup fails and restarts them, or created in corner cases.

This can be a `Service` or a `Workload`.

The address type has the following goals:
* It should support (but not require) on-demand lookups.
  * Specifically, ztunnel should be able to send a request to the control plane to answer "I got a request to send traffic to 1.1.1.1, what is 1.1.1.1?"

  //   is interpreted as "data at least as new as the provided `resourceVersion`"
  //   and the bookmark event is send when the state is synced
  //   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.
  //   If `resourceVersion` is unset, this is interpreted as "consistent read" and the
  //   bookmark event is send when the state is synced at least to the moment
  //   when request started being processed.