Assigning Agents to Kubernetes Nodes for the connectware-agent Helm Chart

Assigning Agents to Kubernetes Nodes

You can target specific Kubernetes nodes with your agent using the Kubernetes node selector. This can for example be used to select a remote node close to your shop floor.

Kubernetes node selector is a set of one or more labels, that the target Kubernetes node must have, to be eligible to run the agent.

To set these node selector labels, use the nodeSelector value inside the agent’s entry in the protocolMapperAgents context of your values.yaml file.

Example

protocolMapperAgents:
    - name: bender-robots
      connectwareHost: connectware.cybus # adjust to actual hostname of Connectware
      nodeSelector:
          mycompany.tld/node-location: shopfloor
          mycompany.tld/building: 1a

Unsetting protocolMapperAgentDefaults Node Selector Labels

If you used the nodeSelector value in the protocolMapperAgentDefaults context of your values.yaml file, you can unset them for individual agents by setting the value of nodeSelector to {} inside the agents entry in the protocolMapperAgents context of your values.yaml.

Example

protocolMapperAgentDefaults:
    connectwareHost: connectware.cybus # adjust to actual hostname of Connectware
    nodeSelector:
        mycompany.tld/node-location: shopfloor
        mycompany.tld/building: 1a
protocolMapperAgents:
    - name: bender-robots # this agent will use the node selector labels
    - name: welder-robots # this agent will NOT use the node selector labels
      nodeSelector: {}