linkerd2/controller/cmd
Alejandro Pedraza 02efb46e45
Have the proxy-injector emit events upon injection/skipping injection (#3316)
* Have the proxy-injector emit events upon injection/skipping injection

Fixes #3253

Have the proxy-injector emit an event whenever a injection happens, or
when injection is skipped for some reason (also added that reason into
the proxy-injector logs). The level is associated to the parent workload
(it can't be associated to the pod because at this point the pod hasn't
been persisted).

The event recorder was setup at the `webhook/server.go` level and passed
to the proxy-injector's `Inject` function. The sp-validator thus also
has access to the event recorder, but for now it's not using it.

Related changes:

- Refactored `api.GetOwnerKindAndName()` to have it return a more
generic object.
- Refactored `report.Injectable()` to also have it return the reason why
a workload is not injectable.

Signed-off-by: Alejandro Pedraza <alejandro@buoyant.io>
2019-08-26 13:34:36 -05:00
..
destination Add support for stateful sets (#3113) 2019-07-24 14:09:46 -07:00
heartbeat Add container cpu and mem to heartbeat requests (#3238) 2019-08-14 12:04:08 -07:00
identity Introduce `linkerd --as` flag for impersonation (#3173) 2019-07-31 16:05:33 -07:00
proxy-injector Have the proxy-injector emit events upon injection/skipping injection (#3316) 2019-08-26 13:34:36 -05:00
public-api Remove tap from public API and associated test infrastructure (#3240) 2019-08-14 17:27:37 -04:00
sp-validator Have the proxy-injector emit events upon injection/skipping injection (#3316) 2019-08-26 13:34:36 -05:00
tap Remove gRPC tap server listener from controller (#3276) 2019-08-16 16:38:50 -04:00