linkerd2/controller
Andrew Seigner e5d2460792
Remove single namespace functionality (#2474)
linkerd/linkerd2#1721 introduced a `--single-namespace` install flag,
enabling the control-plane to function within a single namespace. With
the introduction of ServiceProfiles, and upcoming identity changes, this
single namespace mode of operation is becoming less viable.

This change removes the `--single-namespace` install flag, and all
underlying support. The control-plane must have cluster-wide access to
operate.

A few related changes:
- Remove `--single-namespace` from `linkerd check`, this motivates
  combining some check categories, as we can always assume cluster-wide
  requirements.
- Simplify the `k8s.ResourceAuthz` API, as callers no longer need to
  make a decision based on cluster-wide vs. namespace-wide access.
  Components either have access, or they error out.
- Modify the web dashboard to always assume ServiceProfiles are enabled.

Reverts #1721
Part of #2337

Signed-off-by: Andrew Seigner <siggy@buoyant.io>
2019-03-12 00:17:22 -07:00
..
api Remove single namespace functionality (#2474) 2019-03-12 00:17:22 -07:00
ca Require cluster-wide k8s API access (#2428) 2019-03-07 10:23:18 -08:00
cmd Require cluster-wide k8s API access (#2428) 2019-03-07 10:23:18 -08:00
gen Public API endpoint `Config()` (#2455) 2019-03-07 17:37:46 -05:00
k8s Remove single namespace functionality (#2474) 2019-03-12 00:17:22 -07:00
proxy-injector Quiet inject logging (#2483) 2019-03-11 10:39:10 -07:00
script Add discovery package for managing discovery API (#2317) 2019-02-18 16:38:04 -08:00
tap Require cluster-wide k8s API access (#2428) 2019-03-07 10:23:18 -08:00
Dockerfile Bump Prometheus client to v0.9.2 (#2388) 2019-03-05 10:31:16 -08:00