In what area(s)?

/area-k8sinjector

What version of Dapr?

0.11.3

Expected Behavior

When the daprd docker image (daprio/daprd:0.11.3) is already on the machine, it is not pulled from the registry every time I deploy my application to k8s.

Actual Behavior

Every time I deploy my application to k8s, for every pod that is configured to be injected with a sidecar (using

Environment

• VerneMQ Version: 1.11.0
• OS: CentOS 8.0
• Erlang/OTP version (if building from source):
• VerneMQ configuration (vernemq.conf) or the changes from the default :
  listener.ssl.default = 0.0.0.0:8883
  listener.ssl.allowed_protocol_versions = 3,4,5
  listener.ssl.require_certificate = on
  mqtt_connect_timeout = 30000
• Cluster size/standalone:

Expected behaviour

Set

Currently we don't have any mechanism to limit the maximum number of clients that could be handled simultaneously.

This feature should be designed properly. Here is some clue: https://redis.io/topics/clients#maximum-number-of-clients