linkerd2/proxy-init
Andrew Seigner ec5a0ca8d9
Authorization-aware control-plane components (#2349)
The control-plane components relied on a `--single-namespace` param,
passed from `linkerd install` into each individual component, to
determine which namespaces they were authorized to access, and whether
to support ServiceProfiles. This command-line flag was redundant given
the authorization rules encoded in the parent `linkerd install` output,
via [Cluster]Role[Binding]s.

Modify the control-plane components to query Kubernetes at startup to
determine which namespaces they are authorized to access, and whether
ServiceProfile support is available. This allows removal of the
`--single-namespace` flag on the components.

Also update `bin/test-cleanup` to cleanup the ServiceProfile CRD.

TODO:
- Remove `--single-namespace` flag on `linkerd install`, part of #2164

Signed-off-by: Andrew Seigner <siggy@buoyant.io>
2019-02-26 11:54:52 -08:00
..
cmd WIP: CNI Plugin (#2071) 2019-01-30 11:51:34 -08:00
integration_test Bump base Docker images (#2241) 2019-02-22 15:59:18 -08:00
iptables WIP: CNI Plugin (#2071) 2019-01-30 11:51:34 -08:00
Dockerfile Authorization-aware control-plane components (#2349) 2019-02-26 11:54:52 -08:00
main.go Send non-zero status code when proxy-init command fails (#2064) 2019-01-10 15:48:42 -08:00