Agent Configuration
potctl provides an AgentConfig resource for dynamic management of Agents.
AgentConfig is usually deployed after an Agent in order to modify its behavior. Note that the Agent kind also contains configuration details in the same way that AgentConfig does which means that you can specify custom configuration of Agents at deploy-time.
An Agent Configuration can be retrieved using potctl describe agent-config <AGENT_NAME>.
An Agent Configuration can be deployed using potctl deploy -f agent-config.yaml. The following is a sample of AgentConfig YAML content:
apiVersion: datasance.com/v3
kind: AgentConfig
metadata:
name: agent-1 \# ioFog Agent name
spec:
\# All fields are optional - Only the specified fields will be updated
name: agent-1
description: agent running on VM
latitude: 46.204391
longitude: 6.143158
agentType: auto
dockerUrl: unix:///var/run/docker.sock
diskLimit: 10
diskDirectory: /var/lib/iofog-agent/
memoryLimit: 4096
cpuLimit: 80
logLimit: 10
logDirectory: /var/log/iofog-agent/
logFileCount: 10
statusFrequency: 10
changeFrequency: 10
deviceScanFrequency: 60
bluetoothEnabled: true
watchdogEnabled: false
abstractedHardwareEnabled: false
upstreamRouters: ['default-router']
networkRouter: ''
host: 34.44.56.64
routerConfig:
routerMode: edge
messagingPort: 5672
edgeRouterPort: 56721
interRouterPort: 56722
dockerPruningFrequency: 1
logLevel: INFO
availableDiskThreshold: 90
A complete reference of AgentConfig kind is available in the relevant section in potctl reference documentation.
Details as to what the Agent configuration files look like on Agent hosts can be found on the Agent Reference - Configuration page.