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

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

Use case:
Concatenate TEXT or to TEXT castable type values using a given separator, for example concatenate address parts by comma.

SELECT concat_ws(',', '535 Mission St.', '14th floor', 'San Francisco', 'CA', '94105') AS address;
--> 535 Mission St., 14th floor, San Francisco, CA 94105

Feature description:
Add support for the `concat_ws ( sep text, val1 "any" [

Currently it is only possible to specify cpu and memory limits. Given Kubernetes has Huge Page Support, and huge pages are very applicable to databases, I suggest that it would be useful to be able to do the following:

    resources:
      limits:
        cpu: 1
        memory: 1024Mi
        hugepages-2

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

The API happily accepts attribute updates for host_name and service_name of Downtime objects. That doesn't sound like a good idea to me, just look at the inconsistency between the object name and its attributes in the console transcript below.

I haven't checked any other object types for similar issues, so there might be more as well.

$ downtime=$(curl -skSu root:icinga -H 

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