minikube version: v1.12.3

The flags for setting disk size and memory have the same usage other than for the default value:

minikube start --help [snipped]
     --disk-size='20000mb': Disk size allocated to the minikube VM (format: <number>[<unit>], where unit = b, k, m or g).   
     --memory='': Amount of RAM to allocate to Kubernetes (format: <number>[<unit>], where unit = b

We should remove guava as dependency from the server module.

Most of the functionality we used from it 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 ES, due to their decision to remove guava completely.
Any functionality that we use which isn't present in the JDK can be copied over and integrated into our code

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?

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

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/

Hi, I try to use zalando/postgres-operator operator inside own operator (based on operator SDK) like this:
sample_types.go

package v1

import (
	acidv1 "github.com/zalando/postgres-operator/pkg/apis/acid.zalan.do/v1"
)

type SamleSpec struct {
	Postgres acidv1.PostgresSpec `json:"postgres"`
}

and get several errors when trying to building manifest files:

root@unassi

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