diff --git a/README.md b/README.md index 570119aa..ed10e0c6 100644 --- a/README.md +++ b/README.md @@ -49,13 +49,16 @@ for details on installing the Application addon. **Note**: If you are using Argo similar script [argoDeploy.sh](deploy/argoDeploy.sh) is provided that does not require the Application Lifecycle addon. -The policies are applied to all managed clusters that are available, and have the `environment` set -to `dev`. If policies need to be applied to another set of clusters, update the -`Placement.spec.predicates.requiredClusterSelector.labelSelector.matchExpressions` section in the policies. - **Note**: As new clusters are added that fit the criteria previously mentioned, the policies are applied automatically. +**Important**: The `PlacementRule` resource has been deprecated so policy users must begin moving to +the Placement API instead. See the +[Transitioning from `PlacementRule`(deprecated) to `Placement`](#transitioning-from-placementruledeprecated-to-placement) +that provides details below to learn how to begin using Placement. Policies will no longer include +placement details as part of contributions since placement resources can be shared to avoid +duplication and to allow users to choose different ways of including placement with gitops. + ### Subscription Administrator In new versions of Open Cluster Management you must be a subscription administrator in order to @@ -199,8 +202,8 @@ following steps on migrating from `PlacementRule` to `Placement`: - {key: environment, operator: In, values: ["dev"]} ``` - See the [Placement documentation](https://open-cluster-management.io/concepts/placement/) for - additional details on selecting managed clusters using `Placement`. +See the [Placement documentation](https://open-cluster-management.io/concepts/placement/) for +additional details on selecting managed clusters using `Placement`. 4. Identify any `PlacementBinding` resources that reference a `PlacementRule`. Update the `PlacementBinding` to reference the new `Placement`: