Agents provide resources for order runs. When users schedule orders, they can allocate disk space and memory for running those orders from the resources supplied by agents. The scheduler resides in a Kubernetes Master and order runs execute within Kubernetes components for secure, scaled, dependable management.
Customers can host and maintain their own pool of agents, a designation that DataKitchen implementation engineers configure to constrain all kitchens to the private pools. In this case, customers can define Agent Groups to segregate their agents by environment.
DataKitchen also offers a default agent pool from which customers can allocate resources. At the time of any order run, the system provides the best available agent to use.
Customers may place constraints on resource usage by specifying agent groups that subdivide their agent pools. Agent groups enable users to reserve or restrict the resources for specific kitchens.
For example, in a pool of three agents, a DataKitchen customer may want a production kitchen to use agent1, a staging or UAT kitchen to use agent2, and all remaining kitchens to share agent3. This method ensures that production deployments will always have sufficient resources.
Specify an agent group for kitchen order runs
When your organization has chosen to segregate its agent pool with named agent groups, users can designate a valid agent group for each kitchen.
- On the Kitchens page, find the kitchen and click the associated wrench icon to configure the kitchen.
- Click the Agents tab.
- Enter a valid name in the Agent Group field.
Note that this field is disabled where there are no customer-specific agents.
- Click the Update button.
Updated 19 days ago