cluster

It's not possible to enable addons with --no-kubernetes passed because the addons in their current state are deployed to Kubernetes. So if a user tries to enable an addon with --no-kubernetes output a message notifying them that it's not possible without Kubernetes and exit execution.

Related kubernetes/minikube#13461

In https://github.com/taosdata/TDengine/blob/develop/src/client/src/tscPrepare.c, Local variable loopCont is assigned only once, to a constant value, making it effectively constant throughout its scope. If this is not the intent, examine the logic to see if there is a missing assignment that would make loopCont not remain constant.

So the 1567th line should be removed.
![image](https://user-im

Use case:
Postgres compatible tools like Datagrip, DBeaver, etc. want to get (and sometimes set e.g. Azure Data Studio) the datestyle used by the database. It seems like there is already some implementation for that.

Feature description:
As a db tool engineer I want to be able to fetch the set datestyle of a database to be know how to interpret dates in my tool.

extra: ability

Problem

I would like to be able to have different names for my node to help with discovery in tools like k9s.

If I (a) create the cluster and then (b) create the nodes I can achieve this.

But if I need to create the cluster and nodes at the same time i.e. via -agents flag then this is not possible.
And some use cases e.g. per-node volumes are only possible using this approach

• Which image of the operator are you using? The latest, I'm looking at the codebase.
• **Where do you run it - Metal. Kubernetes.
• Type of issue? - Bug report.

Sometimes secrets don't show up for a few moments, for example if using ExternalSecrets.

The [current code](https://github.com/zalando/postgres-operator/blob/master/pkg/cluster/k8sres

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

fixes #8585

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