cluster

The files deploy/addons/aliyun_mirror.json and pkg/minikube/assets/addons.go should be updated to use the fully qualified image names docker.io/org/image instead of just org/image.

This should be done after https://github.

Bug Description
fix issues found by Coverity Scan in syncMain.c

To Reproduce
N/A

Expected Behavior
fix following issues:
| issue type | category | file path | function | line number |
| -------------------------- | -------------------------- | -------------------------- | -------------------------- |

Problem

I would like to be able to have different names for my node to help with discovery in tools like k9s.

If I (a) create the cluster and then (b) create the nodes I can achieve this.

But if I need to create the cluster and nodes at the same time i.e. via -agents flag then this is not possible.
And some use cases e.g. per-node volumes are only possible using this approach

Use case:

PosgreSQL client compatibility (e.g. Trino)
SQL compliance

CrateDB

CREATE TABLE doc.x (txt TEXT)
SELECT crate.doc.x.txt FROM crate.doc.x

PostgreSQL

postgres=# CREATE TABLE public.x (txt TEXT);
CREATE TABLE
postgres=# SELECT postgres.public.x.txt FROM postgres.public.x;
 txt 
-----
(0 rows)

[From PostgreSQL docs](https://www.postg

Hi There, noticed there is an environment variable to inject "etcd_host" but there are none in the repo for usernames and password. Could create a PR for that to add them to the operator configmap ?
Could enable etcd3 as well since there are no env variables for v3 (supported by Patroni).
Let me know what you guys think.

We had an issue where an api user was using the incorrect parameters on an API call. Having this feature would have made the API fail instead of proceeding. The bug would been found earlier.

I can see where this would be a hassle on many cases, But it would be nice for new projects.

I suppose it could be a global config item that could be overridden at the individual action level:

For

fixes #9262

Users that download the windows EXE will be prompted (by browser and OS) that it is not safe because the EXE isn't signed.

There is a GitHub Action for signing: https://github.com/marketplace/actions/code-sign-a-file-with-pfx-certificate

This would provide additional confidence for