mirror of https://github.com/linkerd/linkerd2.git
655632191b
When installing Linkerd, a user may override default settings, or may
explicitly configure defaults. Consider install options like `--ha
--controller-replicas=4` -- the `--ha` flag sets a new default value for
the controller-replicas, and then we override it.
When we later upgrade this cluster, how can we know how to configure the
cluster?
We could store EnableHA and ControllerReplicas configurations in the
config, but what if, in a later upgrade, the default value changes? How
can we know whether the user specified an override or just used the
default?
To solve this, we add an `Install` message into a new config.
This message includes (at least) the CLI flags used to invoke
install.
upgrade does not specify defaults for install/proxy-options fields and,
instead, uses the persisted install flags to populate default values,
before applying overrides from the upgrade invocation.
This change breaks the protobuf compatibility by altering the
`installation_uuid` field introduced in
|
||
|---|---|---|
| .. | ||
| addr | ||
| admin | ||
| config | ||
| filesonly | ||
| flags | ||
| healthcheck | ||
| identity | ||
| inject | ||
| k8s | ||
| profiles | ||
| prometheus | ||
| tls | ||
| util | ||
| version | ||