Change release note

Signed-off-by: Lubron Zhan <lubronzhan@gmail.com>

changelogs/unreleased/6148-lubronzhan-minor.md

@@ -0,0 +1,3 @@
+## Add anti-affinity rule for envoy deployed by provisioner
+
+Now by default, the envoy deployment created by gateway provistioner will include anti-affinity rule. Also the anti-affinity rule in [default envoy deployment manifest](../../examples/deployment/03-envoy-deployment.yaml) is updated to `preferredDuringSchedulingIgnoredDuringExecution` to be consistent with contour deployment

site/content/resources/upgrading.md

@@ -19,7 +19,7 @@ If you choose to skip versions while upgrading, please note that this may lead t
 
 1. Envoy pod stuck in pending state
 
-    If number of envoy instances is no less than number of kubernetes nodes in the clusters, during rolling upgrade, new envoy pod will be stuck in pending stage because old envoy pod is occupying host pod.
+    If Envoy is deployed with a Deployment and the number of envoy instances is not less than number of kubernetes nodes in the clusters, during rolling upgrade, new envoy pod will be stuck in pending stage because old envoy pod is occupying host port.
 
     Workaround: Delete the envoy instance of older version manually. This will cause a little bit of downtime but it's pretty short.