cluster

Steps to reproduce the issue:

1. minikube -p p1 start and wait for cluster p1 to be ready => minikube created network 6775a57b0a2c p1 bridge local
2. minikube -p p1 stop => cluster stop, network p1 still exists (as expected)
3. minikube -p p2 start and wait for cluster p2 to be

Required by DataGrip. See crate/crate#11726

The full query is

select L.transactionid::varchar::bigint as transaction_id
from pg_catalog.pg_locks L                                                                               
where L.transactionid is not null                                                                        
order by pg_catalog.age(L

--api-port seems the only way to change the clusters.cluster.server: server name in the kubeconfig. However, the port is forced and server name is optional. I'd like the ability to set the hostname without having to also set the port. This would be to preserve the random port created.

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

Initial questions

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

Background

In #1638 I described in detail the process I went thro

We had issues with state file corruption before, however we often have a hard time debugging this because often the corrupt file was deleted to get Icinga running again. Therefore the following proposal: When Icinga fails due to a corrupt state file, it could write a crash report including a copy of the state file in question.

Given that state files can grow quite large in size, we should avoid

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