Fix version_6_upgrade.html.markdown (#11209) (#18804)

[upstream:d49eb280fc75989458a918fe313ff27a1ea9727c]

Signed-off-by: Modular Magician <[email protected]>

.changelog/11209.txt

@@ -0,0 +1,3 @@
+```release-note:none
+
+```

website/docs/guides/version_6_upgrade.html.markdown

@@ -126,8 +126,49 @@ An empty value means the setting should be cleared.
 
 To apply the IAP settings to the backend service, `true` needs to be set for `enabled` field.
 
+### `outlier_detection` subfields default values removed
+
+Empty values mean the setting should be cleared
+
 ## Resource: `google_compute_region_backend_service`
 
 ### `iap.enabled` is now required in the `iap` block
 
 To apply the IAP settings to the backend service, `true` needs to be set for `enabled` field.
+
+### `outlier_detection` subfields default values removed
+
+Empty values mean the setting should be cleared.
+
+### `connection_draining_timeout_sec` default value changed
+
+An empty value now means 300.
+
+### `balancing_mode` default value changed
+
+An empty value now means UTILIZATION.
+
+## Resource: `google_vpc_access_connector`
+
+### Fields `min_throughput` and `max_throughput` no longer have default values
+
+The fields `min_throughput` and `max_throughput` no longer have default values 
+set by the provider. This was necessary to add conflicting field validation, also
+described in this guide.
+
+No configuration changes are needed for existing resources as these fields' values
+will default to values present in data returned from the API.
+
+### Conflicting field validation added for `min_throughput` and `min_instances`, and `max_throughput` and `max_instances`
+
+The provider will now enforce that `google_vpc_access_connector` resources can only
+include one of `min_throughput` and `min_instances` and one of `max_throughput`and 
+`max_instances`. Previously if a user included all four fields in a resource block
+they would experience a permadiff. This is a result of how `min_instances` and
+`max_instances` fields' values take precedence in the API, and how the API calculates
+values for `min_throughput` and `max_throughput` that match the number of instances.
+
+Users will need to check their configuration for any `google_vpc_access_connector`
+resource blocks that contain both fields in a conflicting pair, and remove one of those fields.
+The fields that are removed from the configuration will still have Computed values,
+that are derived from the API.