high-availability

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

Is your proposal related to a problem?

Replication is currently slow.

Describe the solution you'd like

tools bucket replicate could upload a few objects at a time instead of one by one

Describe alternatives you've considered

Copying the objects with some other tool but tools bucket replicate is way too convenient because you can use two completely different object st

What language are you using?

C++

What operating system (Linux, Ubuntu, …) and version?

Linux

What runtime / compiler are you using (e.g. jdk version or version of gcc)

4.8.5

Make sure you include information that can help us debug (full error message, exception listing, stack trace, logs).
tars的发布流程：tarsweb上传安装包 -> tarsAdminRegistry开始发布 -> tarspatch 从/usr/local/app/p

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 we have a mix of:

• Out of memory error.
• Out of memory error
• out of memory error
• out of memory
• out of memory.
• out of memory [some context]

All these should be adjusted to use the same wording for consistency and it should also make the executable a little bit smaller 😄

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.

This is something that came up with our experiments in migrating our cluster from 1.3 to 1.5.

Our process is essentially as follows:

1. create cluster as is with a single primary
2. disable monitor on primary with --force on it pg_autoctl disable monitor --force --pgdata /var/lib/postgresql/12/main_cluster/
3. stop pg_autoctl service with sudo service postgresql_main_cluster stop
4. e