4 ms·

Congratulations, you all just suggested re-inventing Deis workflow (with a few additional pieces) :) There are a lot of elements indeed, https://docs.teamhephy

by yebyen 4y ago

Congratulations, you all just suggested re-inventing Deis workflow (with a few additional pieces) :) There are a lot of elements indeed, https://docs.teamhephy.com/understanding-workflow/components/ https://docs.teamhephy.com/understanding-workflow/components... This is classic literature: https://docs.teamhephy.com/understanding-workflow/architecture/ https://docs.teamhephy.com/understanding-workflow/architectu... It is much easier to just use it than to try and re-invent your own: https://docs.teamhephy.com/quickstart/ https://docs.teamhephy.com/quickstart/ I cannot guarantee the cloud provider bits all work, I don't use them so I don't maintain them, but if you have Kubernetes with persistent disk provided, which any managed Kubernetes can most certainly do, it's easy enough to hook up generic Minio (which has the added benefit of working just as well on bare metal hosts), and I'm certain that does work as I use it.

viraptor 4y ago
> It is much easier to just use it than to try and re-invent your own Now listen buddy... That CV is not gonna pad itself, ok? Seriously though, if you have time and curiosity, I'd recommend putting together a monitoring stack by hand once. There's a lot to learn from that experience.
- yebyen 4y ago
  My go-to stack is Prometheus and Grafana with kube-prometheus-stack Helm chart for Kubernetes. I'm sure I'm not configuring it well. There are too many leaps I couldn't follow directly in how to make the config, and there's something about how arrays merge in YAML that makes it harder to write a config like this in Helm... so there is a lot of what I've written here that shouldn't need to be in my own config, because they are the standard default alerts, but I wound up having to include them to make my one extra alert join the rest (and this is my excuse for why it is several hundred lines long, when in reality it's mostly stock.) This config goes so far as making alerts to Slack with Alertmanager that work out of the box! https://github.com/kingdonb/flux2/blob/monitoring/manifests/monitoring/kube-prometheus-stack/release.yaml#L11 https://github.com/kingdonb/flux2/blob/monitoring/manifests/... :sunglasses:

by yebyen 4y ago

viraptor 4y ago

> It is much easier to just use it than to try and re-invent your own Now listen buddy... That CV is not gonna pad itself, ok? Seriously though, if you have time and curiosity, I'd recommend putting together a monitoring stack by hand once. There's a lot to learn from that experience.

yebyen 4y ago
My go-to stack is Prometheus and Grafana with kube-prometheus-stack Helm chart for Kubernetes. I'm sure I'm not configuring it well. There are too many leaps I couldn't follow directly in how to make the config, and there's something about how arrays merge in YAML that makes it harder to write a config like this in Helm... so there is a lot of what I've written here that shouldn't need to be in my own config, because they are the standard default alerts, but I wound up having to include them to make my one extra alert join the rest (and this is my excuse for why it is several hundred lines long, when in reality it's mostly stock.) This config goes so far as making alerts to Slack with Alertmanager that work out of the box! https://github.com/kingdonb/flux2/blob/monitoring/manifests/monitoring/kube-prometheus-stack/release.yaml#L11 https://github.com/kingdonb/flux2/blob/monitoring/manifests/... :sunglasses: