The error on this line links to a dead resource: https://docs.doInfo.com/engine/install/linux-postinstall/#your-kernel-does-not-support-cgroup-swap-limit-capabilities

Use case:
As a user I want to get a clear error message, when I try to connect to a CrateDB Cluster, that enforces TLS and doesn't allow non-ecrypted connections.

Right now I only see a message, that doesn't make this clear: e.g.:

Npgsql.PostgresException (0x80004005): 28000: No valid auth.host_based entry found for host "10.0.0.89", user "defaultuser"

Feature description

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

• Which image of the operator are you using? e.g.
  registry.opensource.zalan.do/acid/postgres-operator:v1.6.1

• Where do you run it - cloud or metal? Kubernetes or OpenShift? [AWS K8s | GCP ... | Bare Metal K8s]
  Baremetal k8s

• Are you running Postgres Operator in production? [yes | no]
  yes

• Type of issue?
  feature request.

Currently it's not possible to start the ope

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