Chỉnh sửa

Chia sẻ qua

Configure dataflow profile

  • Bài viết

Important

Azure IoT Operations Preview – enabled by Azure Arc is currently in preview. You shouldn't use this preview software in production environments.

You'll need to deploy a new Azure IoT Operations installation when a generally available release is made available. You won't be able to upgrade a preview installation.

See the Supplemental Terms of Use for Microsoft Azure Previews for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.

By default, when you deploy Azure IoT Operations, a dataflow profile is created with default settings. You can configure the dataflow profile to suit your needs.

Default dataflow profile

By default, a dataflow profile named "default" is created when Azure IoT Operations is deployed.

apiVersion: connectivity.iotoperations.azure.com/v1beta1
kind: DataflowProfile
metadata:
  name: default
  namespace: azure-iot-operations
spec:
  instanceCount: 1

In most cases, you don't need to change the default settings. However, you can create additional dataflow profiles and configure them as needed.

Scaling

To manually scale the dataflow profile, specify the maximum number of instances you want to run.

spec:
  instanceCount: 3

If not specified, Azure IoT Operations automatically scales the dataflow profile based on the dataflow configuration. The number of instances is determined by the number of dataflows and the shared subscription configuration.

Important

Currently in public preview, adjusting the instance count may result in message loss. At this time, it's recommended to not adjust the instance count.

Configure log level, node tolerations, diagnostic settings, and other deployment-wide settings

You can configure other deployment-wide settings such as log level, node tolerations, and diagnostic settings.

spec:
  logLevel: debug
  tolerations:
    - key: "node-role.kubernetes.io/edge"
      operator: "Equal"
      value: "true"
      effect: "NoSchedule"
  diagnostics:
    # ...