Hono Load Tests with CoAP devices

# Configuration properties for protocol adapters.
adapters:
  # kafkaMessagingSpec contains the configuration used by all protocol
  # adapters for connecting to the Kafka cluster to be used for messaging.
  # This property MUST be set if "messagingNetworkTypes" contains "kafka" and
  # "kafkaMessagingClusterExample.enabled" is set to false.
  # Please refer to https://www.eclipse.org/hono/docs/admin-guide/common-config/#kafka-based-messaging-configuration
  # for a description of supported properties.
  kafkaMessagingSpec:
    commonClientConfig:
      bootstrap.servers: "xxx"
      ssl.endpoint.identification.algorithm: https
      security.protocol: SSL
      connections.max.idle.ms: 240000
    command:
      consumerConfig:
        "compression.type": none
    commandInternal:
      adminClientConfig:
        "compression.type": none
    commandResponse:
      producerConfig:
        acks: all
        delivery.timeout.ms: 5000
        request.timeout.ms: 1250
        max.block.ms: 2500
        "compression.type": none
    event:
      producerConfig:
        acks: all
        delivery.timeout.ms: 5000
        request.timeout.ms: 1250
        max.block.ms: 2500
        "compression.type": none
    telemetry:
      producerConfig:
        acks: all
        delivery.timeout.ms: 5000
        request.timeout.ms: 1250
        max.block.ms: 2500
        "compression.type": none

  # tenantSpec contains Hono client properties used by all protocol adapters for
  # connecting to the Tenant service.
  # This property MUST be set if "deviceRegistryExample.enabled" is set to false.
  # Please refer to https://www.eclipse.org/hono/docs/admin-guide/hono-client-configuration/
  # for a description of supported properties.
  tenantSpec:
    flowLatency: 1000
    requestTimeout: 500

  # deviceRegistrationSpec contains Hono client properties used by all protocol adapters for
  # connecting to the Device Registration service.
  # This property MUST be set if "deviceRegistryExample.enabled" is set to false.
  # Please refer to https://www.eclipse.org/hono/docs/admin-guide/hono-client-configuration/
  # for a description of supported properties.
  deviceRegistrationSpec:
    flowLatency: 1000
    responseCacheMaxSize: 10000
    requestTimeout: 500

  # credentialsSpec contains Hono client properties used by all protocol adapters for
  # connecting to the Credentials service.
  # This property MUST be set if "deviceRegistryExample.enabled" is set to false.
  # Please refer to https://www.eclipse.org/hono/docs/admin-guide/hono-client-configuration/
  # for a description of supported properties.
  credentialsSpec:
    flowLatency: 1000
    requestTimeout: 500

  # commandRouterSpec contains Hono client properties used by all protocol adapters for
  # connecting to the Command Router service.
  # If not set, default properties will be used for establishing a TLS based connection
  # to the command router server.
  # Please refer to https://www.eclipse.org/hono/docs/admin-guide/hono-client-configuration/
  # for a description of supported properties.
  commandRouterSpec:
    flowLatency: 1000
    requestTimeout: 500

  amqp:
    enabled: false

  coap:
    enabled: true

    # quarkusLoggingProfile indicates at which level the Quarkus based variant of the component should log.
    # Supported values are "prod", "dev" or "trace"
    quarkusLoggingProfile: "prod"
    # resources contains the container's requests and limits for CPU and memory
    # as defined by the Kubernetes API.
    # Refer to https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
    # for a description of the properties' semantics.
    resources:
      requests:
        cpu: "500m"
        memory: "640Mi"
      limits:
        cpu: "3"
        memory: "2048Mi"
    svc:
      # Provide Network Load Balancer service to make the CoAP server accessible from internet
      annotations:
        service.beta.kubernetes.io/aws-load-balancer-type: "nlb"
        service.beta.kubernetes.io/aws-load-balancer-nlb-target-type: "instance"
        service.beta.kubernetes.io/aws-load-balancer-scheme: "internet-facing"
        service.beta.kubernetes.io/aws-load-balancer-cross-zone-load-balancing-enabled: "true"
        service.beta.kubernetes.io/aws-load-balancer-healthcheck-interval: "10"
        service.beta.kubernetes.io/aws-load-balancer-healthcheck-timeout: "6"
        service.beta.kubernetes.io/aws-load-balancer-healthcheck-unhealthy-threshold: "2"

    # hono contains the adapter's configuration properties
    hono:
      # coap contains configuration properties for the adapter's
      # exposed CoAP endpoints.
      # If not set, the adapter by default exposes the secure port
      # using an example key and certificate.
      coap:
         tenantIdleTimeout: "1h"
         maxPayloadSize: 64000
         timeoutToAck: 500
         coapThreads: 8
         dtlsThreads: 8
         maxConnections: 80000

  http:
    enabled: false

  mqtt:
    enabled: false

# authServer contains configuration properties for the Auth Server component.
authServer:
  # quarkusLoggingProfile indicates at which level the Quarkus based variant of the component should log.
  # Supported values are "prod", "dev" or "trace"
  quarkusLoggingProfile: "prod"
  # resources contains the container's requests and limits for CPU and memory
  # as defined by the Kubernetes API.
  # Refer to https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
  # for a description of the properties' semantics.
  resources:
    requests:
      cpu: "500m"
      memory: "512Mi"
    limits:
      cpu: "3"
      memory: "1Gi"

# deviceRegistryExample contains configuration properties for the
# example Device Registry.
deviceRegistryExample:

  # Sets the type of the device registry to be deployed. The following types are defined:
  # - embedded: Embedded JDBC based device registry. Also refer to the section "embeddedJdbcDeviceRegistry"
  # for additional configuration.
  # - mongodb: MongoDB based device registry. Also refer to the section "mongoDBBasedDeviceRegistry"
  # for additional configuration.
  # - jdbc: JDBC based device registry. Also refer to the section "jdbcBasedDeviceRegistry"
  # for additional configuration.
  type: "mongodb"

  # addExampleData indicates whether example data is inserted after the device registry is deployed
  addExampleData: false

  # hono contains the Device Registry's configuration properties as defined in
  # https://www.eclipseorg/hono/docs/admin-guide/device-registry-config/
  hono:
    # auth contains Hono client properties used by the example registry for
    # connecting to the Authentication service.
    # If not set, the registry by default uses the Auth Server component to
    # authenticate clients.
    auth:
      flowLatency: 1000
      connectTimeout: 2000

  # mongoDBBasedDeviceRegistry contains configuration properties specific to the
  # MongoDB based device registry.
  mongoDBBasedDeviceRegistry:

    # quarkusLoggingProfile indicates at which level the Quarkus based variant of the component should log.
    # Supported values are "prod", "dev" or "trace"
    quarkusLoggingProfile: "prod"

    # resources contains the container's requests and limits for CPU and memory
    # as defined by the Kubernetes API.
    # Refer to https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
    # for a description of the properties' semantics.
    resources:
      requests:
        cpu: "500m"
        memory: "512Mi"
      limits:
        cpu: "3"
        memory: "2Gi"
    # mongodb contains the configuration properties to connect to the MongoDB database instance.
    # If you would like to use an already existing MongoDB database instance, then configure
    # the below section accordingly.
    mongodb:
      # The connection string for MongoDb.
      # Could be taken from Atlas UI with username and password substitution and adding the database name as a suffix.
      # Optional parameters could be passed as well (using '?')
      connectionString: "xxx"

# commandRouterService contains configuration properties for the
# Command Router service.
commandRouterService:

  # quarkusLoggingProfile indicates at which level the Quarkus based variant of the component should log.
  # Supported values are "prod", "dev" or "trace"
  quarkusLoggingProfile: "prod"
  # resources contains the container's requests and limits for CPU and memory
  # as defined by the Kubernetes API.
  # Refer to https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
  # for a description of the properties' semantics.
  resources:
    requests:
      cpu: "500m"
      memory: "512Mi"
    limits:
      cpu: "3"
      memory: "1Gi"

  # hono contains the service's configuration properties as defined in
  # https://www.eclipse.org/hono/docs/admin-guide/command-router-config/
  hono:
    app:
      # maxInstances defines the number of adapter Verticle instances to deploy
      # to the vert.x runtime during start-up.
      maxInstances: 2
    # auth contains Hono client properties used by the service for
    # connecting to the Authentication service.
    # If not set, the service by default uses the Auth Server component to
    # authenticate clients.
    auth:
      flowLatency: 1000

    commandRouter:
      # cache contains properties configuring the embedded or remote cache that
      # the Command Router uses for storing routing information. Please refer to Hono's Command Router admin guide at
      # https://www.eclipse.org/hono/docs/admin-guide/command-router-config/#data-grid-connection-configuration for
      # details regarding cache configuration.
      # If not set explicitly here and "dataGridExample.enabled" is "true", the example data grid is used.
      # If "dataGridExample.enabled" is "false", an embedded cache with a default configuration will be used.
      # Note that when using the embedded cache, the Command Router pod does NOT support scaling up to a replica
      # count > 1
      cache:
        remote:
          serverList: "eclipse-hono-data-grid:11222"
          authServerName: "eclipse-hono-data-grid"
          authUsername: "xxx"
          authPassword: "xxx"
          authRealm: "ApplicationRealm"
          saslMechanism: "SCRAM-SHA-512"
          connectTimeout: 500
          socketTimeout: 500
          connectionPool:
            minIdle: 10
            maxActive: 10
            maxWait: 500
            maxPendingRequests: 400
          defaultExecutorFactory:
            poolSize: 200

# kafkaMessagingClusterExample contains properties for configuring an example Kafka cluster
# to be used for messaging if "messagingNetworkTypes" contains "kafka"
kafkaMessagingClusterExample:
  # set to false as external Kafka is used (MSK)
  enabled: false

jaegerBackendExample:
  enabled: true
  # resources contains the container's requests and limits for CPU and memory
  # as defined by the Kubernetes API.
  # Refer to https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
  # for a description of the properties' semantics.
  resources:
    requests:
      cpu: "1"
      memory: "1Gi"
    limits:
      cpu: "2"
      memory: "2Gi"

  # env contains environment variables to set for the Jaeger all-in-one container.
  env:
  - name: "MEMORY_MAX_TRACES"
    value: "20000"

# dataGridExample contains properties for configuring an example data grid
# to be used by the Command Router component
dataGridExample:
  enabled: true
  # resources contains the container's requests and limits for CPU and memory
  # as defined by the Kubernetes API.
  # Refer to https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
  # for a description of the properties' semantics.
  resources:
    requests:
      cpu: "500m"
      memory: "512Mi"
    limits:
      cpu: "3"
      memory: "2Gi"

# Remove device-registry public access manually as not possible via the helm chart
kubectl -n $namespace delete svc eclipse-hono-service-device-registry-ext
# Remove jaeger query public access manually as not possible via the helm chart
kubectl -n $namespace patch svc eclipse-hono-jaeger-query -p '{"spec": {"type":"ClusterIP"}}'

# Increase data grid memory as not possible via the helm chart
kubectl get cm eclipse-hono-data-grid-conf -n hono -o yaml | sed -e's|max-size=\"30 MB\"|max-size=\"100 MB\"|' | kubectl apply -f -
kubectl -n $namespace rollout restart statefulset eclipse-hono-data-grid
kubectl -n $namespace rollout status statefulset eclipse-hono-data-grid

# Scale infinispan manually as not possible via the helm chart
kubectl -n $namespace scale statefulset eclipse-hono-data-grid --replicas=3
# Scale auth service manually as not possible via the helm chart
kubectl -n $namespace scale deployment eclipse-hono-service-auth --replicas=2
# Scale device registry manually as not possible via the helm chart
kubectl -n $namespace scale deployment eclipse-hono-service-device-registry --replicas=2
# Scale command router manually as not possible via the helm chart
kubectl -n $namespace scale deployment eclipse-hono-service-command-router --replicas=2
# Scale coap adapter manually as not possible via the helm chart
kubectl -n $namespace scale deployment eclipse-hono-adapter-coap --replicas=3
# Scale command router manually as not possible via the helm chart
kubectl -n $namespace scale deployment eclipse-hono-service-command-router --replicas=2