update API comments

Author: Arvind Thirumurugan

apis/placement/v1alpha1/disruptionbudget_types.go

@@ -44,8 +44,7 @@ type PlacementDisruptionBudgetSpec struct {
 	// If a percentage is specified, Fleet will calculate the corresponding absolute values
 	// as follows:
 	// * if the linked Placement object is of the PickFixed placement type,
-	//   the percentage is against the number of clusters specified in the placement (i.e., the
-	//   length of ClusterNames field in the placement policy);
+	//   we don't perform any calculation because eviction is not allowed for PickFixed CRP.
 	// * if the linked Placement object is of the PickAll placement type, MaxUnavailable cannot
 	//   be specified since we cannot derive the total number of clusters selected.
 	// * if the linked Placement object is of the PickN placement type,
@@ -74,8 +73,7 @@ type PlacementDisruptionBudgetSpec struct {
 	// If a percentage is specified, Fleet will calculate the corresponding absolute values
 	// as follows:
 	// * if the linked Placement object is of the PickFixed placement type,
-	//   the percentage is against the number of clusters specified in the placement (i.e., the
-	//   length of ClusterNames field in the placement policy);
+	//   we don't perform any calculation because eviction is not allowed for PickFixed CRP.
 	// * if the linked Placement object is of the PickAll placement type, MinAvailable can be
 	//   specified but only as an integer since we cannot derive the total number of clusters selected.
 	// * if the linked Placement object is of the PickN placement type,

apis/placement/v1alpha1/eviction_types.go

@@ -37,6 +37,10 @@ import (
 // (e.g., the CRP object or the placement appears later). To fix the situation, re-create the
 // Eviction object.
 //
+// Note: Eviction of resources from a cluster propagated by a PickFixed CRP is not allowed.
+// If the user wants to remove resources from a cluster propagated by a PickFixed CRP simply
+// remove the cluster name from cluster names field from the CRP spec.
+//
 // Executed evictions might be kept around for a while for auditing purposes; the Fleet controllers might
 // have a TTL set up for such objects and will garbage collect them automatically. For further
 // information, see the Fleet documentation.