Grouping Workloads: Clusters and Inventory Filters

Are used to apply policy to a subset of the workloads in a scope.

Can be used to apply policy to a subset of the workloads in a scope.

Can also be used to apply policy to workloads regardless of scope (for example, to apply policy to all workloads running a particular operating system.)

Are defined by a query

Are defined by a query.

Can include only workloads in a single scope.

Can have membership restricted to a single scope or include workloads in any scope (for example, if the filter is based on operating system.)

Can only be used by policies in the same workspace and workspace version.

Can be used by policies in any scope and any workspace.

Can be automatically created during automatic policy discovery.

Must be manually created or converted from an existing cluster.

Can be overwritten during automatic policy discovery if not approved. Approving known good clusters can improve accuracy of other clusters in future discovery runs.

Are never modified by automatic policy discovery.

Benefit from important features of automatic policy discovery. They:

• Have a confidence rating that helps you evaluate whether the workloads in the group belong together.

• Can be compared with clusters generated during other policy discovery runs on the same workspace.

--

Cannot be used when configuring External Dependencies and other features related to cross-scope policies and policy discovery.

Can be used to configure granular policies involving external dependencies and other features related to cross-scope policies, such as auto-pilot rules.

See Clusters and subtopics.

See Create an Inventory Filter and Convert a Cluster to an Inventory Filter