Merge branch 'tmccaslin-duo-network-additions' into 'master'

Add missing details for Duo network connections

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/150731



Merged-by: Suzanne Selhorn <sselhorn@gitlab.com>
Co-authored-by: Taylor McCaslin <tmccaslin@gitlab.com>

doc/subscriptions/subscription-add-ons.md

@@ -66,10 +66,10 @@ Prerequisites:
 
 #### Configure network and proxy settings
 
-For all self-managed AI features:
+For self-managed instances, to enable AI-powered features:
 
 - Your firewalls and HTTP/S proxy servers must allow outbound connections
-  to `cloud.gitlab.com` on port `443`.
+  to `cloud.gitlab.com` and `customers.gitlab.com` on port `443` both with `https://` and `wws://`.
 - Both `HTTP2` and the `'upgrade'` header must be allowed, because GitLab Duo
   uses both REST and WebSockets.
 - To use an HTTP/S proxy, both `gitLab_workhorse` and `gitLab_rails` must have the necessary

doc/user/ai_features.md

@@ -63,10 +63,10 @@ To enable Beta and Experimental AI-powered features, use the [Experiment and Bet
 
 To enable Beta and Experimental AI-powered features for GitLab versions where GitLab Duo Chat is not yet generally available, see the [GitLab Duo Chat documentation](gitlab_duo_chat.md#for-self-managed).
 
-### Enable outbound connections to enable GitLab Duo features on Self-managed instances
+### Enable outbound connections to enable GitLab Duo features on self-managed instances
 
 - Your firewalls and HTTP/S proxy servers must allow outbound connections
-  to `cloud.gitlab.com` on port `443`.
+  to `cloud.gitlab.com` and `customers.gitlab.com` on port `443` both with `https://` and `wws://`.
 - Both `HTTP2` and the `'upgrade'` header must be allowed, because GitLab Duo
   uses both REST and WebSockets.
 - To use an HTTP/S proxy, both `gitLab_workhorse` and `gitLab_rails` must have the necessary