update: added goal to point out maintaining partition resize after installation

Signed-off-by: ehila <[email protected]>

Author: eggfoobar

enhancements/workload-partitioning/wide-availability-workload-partitioning.md

@@ -66,6 +66,9 @@ determinism required of my applications.
 - We want to be clear with customers that this enhancement is a day 0 supported
   feature only. We do not support turning it off after the installation is done
   and the feature is on.
+- We want to maintain the ability to configure the partition size after
+  installation, we do not support turning off the partition feature but we do
+  support changing the CPU partition size post day 0.
 
 ### Non-Goals
 
@@ -302,9 +305,10 @@ should be a cluster wide feature.
 A risk we can run into is that a customer can apply a CPU set that is too small
 or out of bounds can cause problems such as extremely poor performance or start
 up errors. Mitigation of this scenario will be to provide proper guidance and
-guidelines for customers who enable this enhancement. Furthermore, the
+guidelines for customers who enable this enhancement. As mentioned in our goal
+we do support re-configuring the CPUSet partition size after installation. The
 performance team would need to be reached out to for more specific information
-around upper and lower bounds of CPU sets for running an Openshift cluster.
+around upper and lower bounds of CPU sets for running an Openshift cluster
 
 It is possible to build a cluster with the feature enabled and then add a node
 in a way that does not configure the workload partitions only for that node. We