Environment:
Minikube on Mac OS X

What happened:

I am trying to load NGINX-Ingress with a custom tls certificate, in this case a trusted TLS certificate I generated on my machine. I start minikube, then enable the ingress-nginx addon which deploys nginx to the kube-system namespace successfully. I create my certificate in the kube-system namespace with the title mkcert.

I then modified

Currently sum aggregations on numeric columns of type REAL or DOUBLE PRECISION uses a straight forward x + y operation (Double::sum).

SELECT sum(real_column) FROM tbl

There would be the [Kahan summation algorithm](https

The example configs don't contain an example of setting the display name in yaml configs.

Also --display-name is missing from the README.md docs for flags

Given an existing cluster, is there any way to check
A) whether a local registry is enabled for that cluster, and
B) the value of registry-port/registry-name?

Relatedly: given a cluster that was started without the --enable-registry flag, is there any way to enable the registry post-facto?

Describe the bug

/usr/share/icinga2/include/command-plugins.conf provides the http CheckCommand. Since version 2.3.0 there is a new option in check_http which allows for checking the correctness of a certificate and hostname match: --verify-host. Please add this to the built in template library.

https://icinga.com/docs/icinga2/latest/doc/10-icinga-template-library/

$ /usr/

Hello

I would like to have pgbouncer-exporter as a sidecar for the connection pooler.
I don't think it's possible right now.

It would be great to have the same options for sidecars as in the cluster.

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