FEATURE REQUEST:
Hi,

I see that there is nothing in the kargo repo related to docker login stuff and more precisely nothing about the ability to make kubernetes pull images from private registries such as ECR.

I have a solution for this that currently works for ECR and CoreOS and that could be extended to different registries solutions (azure one, custom private registry on premi

Default step does not make much sense if the scrape interval is common (e.g 15s). Getting too low makes things extremely slow for no good reason.

Flag on querier might be a good idea.

We want to have consistent and structured logs to improve the ability to filter and analyse longhorn-manager logs.
Currently the controller uses the global logrus package logger, the task here would be to switch the log calls to the instance logger that was implemented in longhorn/longhorn-manager#661

While doing this also improve the log messages, where possible.
For an example of a successf

currently "option forwardfor" cant't be unset, so there is no way to enable it in the default section and disable it in a particular frontend

https://github.com/google/starlark-go/blob/master/doc/spec.md

It should satisfy our reproducibility needs (like jsonnet) and could be easier to write agola config files.

Like in #137 we should provide build context information.

To reproduce:

make cluster NODES=3
# In shell in tmux run this line of commands twice
pg_autoctl set formation number-sync-standbys 0 && pg_autoctl set node candidate-priority --name node3 0 && pg_autoctl set node replication-quorum --name node3 false

second time it fails like this:

16:52:06 9301 INFO  Waiting for the settings to have been applied to the monitor and primary nod