Conversation
Signed-off-by: Tarun Pothulapati <[email protected]>
Signed-off-by: Tarun Pothulapati <[email protected]>
Signed-off-by: Tarun Pothulapati <[email protected]>
Signed-off-by: Tarun Pothulapati <[email protected]>
Signed-off-by: Tarun Pothulapati <[email protected]>
Signed-off-by: Tarun Pothulapati <[email protected]>
Signed-off-by: Tarun Pothulapati <[email protected]>
Signed-off-by: Tarun Pothulapati <[email protected]>
Signed-off-by: Tarun Pothulapati <[email protected]>
7a031d6 to
443f7fa
Compare
Signed-off-by: Tarun Pothulapati <[email protected]>
443f7fa to
ab854df
Compare
Signed-off-by: Tarun Pothulapati <[email protected]>
Signed-off-by: Tarun Pothulapati <[email protected]>
Signed-off-by: Tarun Pothulapati <[email protected]>
9d348b9 to
f8152de
Compare
Signed-off-by: Tarun Pothulapati <[email protected]>
Signed-off-by: Tarun Pothulapati <[email protected]>
Signed-off-by: Tarun Pothulapati <[email protected]>
alpeb
left a comment
There was a problem hiding this comment.
Looking good 👍
Can I ask you to make a parent issue, besides the couple of issues already referenced, with a list of checkboxes for the specific things that will be addressed in separate PRs? So that we can keep track of other things like the health checks, the extra validations the helm chart will require (discussed in the RFC), documentation, test plan issue, etc. And then that issue can be the main one that the RFC will link to. Makes sense?
I'll be thoroughly testing this tomorrow 😉
| @@ -34,7 +29,6 @@ data: | |||
| static_configs: | |||
| - targets: ['localhost:9090'] | |||
|
|
|||
| {{ if .Values.grafana.enabled -}} | |||
There was a problem hiding this comment.
@alpeb As grafana is a separate add-on, and those fields are only propagated into their sub-chart. We can't get this value in Prometheus add-on.
I don't think prometheus would have any problem regarding the scrape-config even when there is no grafana, but I will test this out!
For other fields that would need to be accessed across multiple add-ons, we can use the global and have that in linkerd-config-addons!
Signed-off-by: Tarun Pothulapati <[email protected]>
Signed-off-by: Tarun Pothulapati <[email protected]>
Signed-off-by: Tarun Pothulapati <[email protected]>
Signed-off-by: Tarun Pothulapati <[email protected]>
Signed-off-by: Tarun Pothulapati <[email protected]>
|
This PR also has the following additional changes:
|
|
|
||
| # controller configuration | ||
| controllerImage: gcr.io/linkerd-io/controller | ||
| controllerLogLevel: &controller_log_level info |
There was a problem hiding this comment.
@alpeb Though we moved this flag to be global like we should, but we don't actually have a way to use this directly in prometheus/values.yaml as we can't template values there. and putting that in the templates directly means that we don't have a way to merge them and appending might cause prometheus to complain just like it did with other values in configmap (I will try this out today)
Signed-off-by: Tarun Pothulapati <[email protected]>
Signed-off-by: Tarun Pothulapati <[email protected]>
|
Thanks @Pothulapati for the extended explanations 🙂 According to my understanding on how this should work, I suggest we remove the commented properties in And a comment like this in the header of Does that makes sense? |
|
@alpeb I was thinking that with Helm, when users want to overwrite they would use This way they still get
|
|
Ok cool. So the only thing we have to say is to not touch the |
Signed-off-by: Tarun Pothulapati <[email protected]>
|
@alpeb Yep, Updated |
Signed-off-by: Tarun Pothulapati <[email protected]>
|
@Pothulapati would you check the behavior of |
alpeb
left a comment
There was a problem hiding this comment.
It seems I had done a linkerd upgrade --addon-overwrite while at the same time changing something inside the main values.yaml, so that's the change I was seeing in linkerd-config-addons. So it's working as expected 👍
I did a round of tests with CLI and Helm for installs and upgrade, and it all seems correct to me 👍
Signed-off-by: Tarun Pothulapati <[email protected]>
Signed-off-by: Tarun Pothulapati <[email protected]>
Signed-off-by: Tarun Pothulapati <[email protected]>
Signed-off-by: Tarun Pothulapati <[email protected]>
Signed-off-by: Tarun Pothulapati <[email protected]>
files accordingly to include more Signed-off-by: Tarun Pothulapati <[email protected]>
Signed-off-by: Tarun Pothulapati <[email protected]>
There was a problem hiding this comment.
The addon-related changes still look good to me 👍
#4724 addresses the linkerd check changes required when the addon is disabled. There are still lots of other places that fail without it (heartbeat, dashboard (when accessed, the controller pod dies), smi-metrics, CLI commands).
What do you think about addressing the non-prometheus scenario in all those places before tackling the customized prom url case and the "addonification" of the other components? That way we don't leave that failed case open in the upcoming edges for too long. Definitely in a separate PR, so we can merge this one and move on.
Signed-off-by: Tarun Pothulapati <[email protected]>
Signed-off-by: Tarun Pothulapati <[email protected]>
This moves Prometheus as a add-on, thus making it optional but enabled by default. The also make `linkerd-prometheus` more configurable, and allow it to have its own life-cycle for upgrades, configuration, etc. This work will be followed by documentation that help users configure existing Prometheus to work with Linkerd. **Changes Include:** - moving prometheus manifests into a separate chart at `charts/add-ons/prometheus`, and adding it as a dependency to `linkerd2` - implement the `addOn` interface to support the same with CLI. - include configuration in `linkerd-config-addons` **User Facing Changes:** The default install experience does not change much but for users who have already configured Prometheus differently, would need to apply the same using the new configuration fields present in chart README Signed-off-by: Eric Solomon <[email protected]>
Fixes #3590, #3406
Implements first part of linkerd/rfc#16, #4375
This PR moves Prometheus as a add-on, thus making it optional but enabled by default. The main benefit of this work is to make
linkerd-prometheusmore configurable, and allow it to have its own life-cycle for upgrades, configuration, etc.This work will be followed by documentation that help users configure existing Prometheus to work with Linkerd.
Changes Include:
charts/add-ons/prometheus, and adding it as a dependency tolinkerd2addOninterface to support the same with CLI.linkerd-config-addons