We do not support old docker daemon versions in docker driver because of docker network inspect minikube output format. But the error message is very confusing (see below). We need to check docker version on start and if it's too old (>18.06.3 should be fine, but need to verify) we should report an error and exit

ilyaz@debian:~$ minikube start 
* minikube v1.17.0 on Debian 8.11
* Usi

We should remove Guava as a dependency from the server module.

Most of the functionality we used from Guava are provided by the JDK by now.
The stuff that is missing from the JDK has mostly been added in the utilities we inherited from Elasticsearch, due to their decision to remove Guava completely.
Any functionality that we use which isn't present in the JDK can be co

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

Scope of your request

Use only mirrored container-images for k3d.

Describe the solution you'd like

K3d already provides --image for nodes image. It would be nice to be able to do the same for "the rest" like

• rancher/k3d-proxy:v3.0.2
• traefik
• other images used "by default" or configurable by options.

This way we would be more self-sustaining and ease the pull from docke

• Which image of the operator are you using? registry.opensource.zalan.do/acid/postgres-operator:v1.5.0
• Where do you run it - cloud or metal? Kubernetes or OpenShift? GKE
• Are you running Postgres Operator in production? no
• Type of issue? Bug/Feature

The Postgres Operator currently supports setting [custom TLS certificates](https://postgres-operator.readthedocs.io/en/lat

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/

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