here we confuse the user with two things

❗ You cannot change the memory size for an exiting minikube cluster. Please first delete the cluster.
and

😿 Failed to start ssh bare metal machine. Running "minikube delete -p foo" may fix it: config: please provide an IP address

we should had sticked with first advice

drewpca(pts/0):~% minikube start -p foo --memory 6GB
😄  [foo] m

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

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

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

Hi Team,

While using OPR v1.6.1, we get the error seteuid: Operation not permitted due to cron binary unable to run.

zalando/spilo#562

We compared the old (1.5.0)and new operator (1.6.1) and observed the error is due to the allowPrivilegeEscalation: false under securityContext.

We see required either to remove the allowPrivilegeEscalation ( as in 1.

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