diff --git a/docs/dyn/alloydb_v1alpha.projects.locations.clusters.instances.html b/docs/dyn/alloydb_v1alpha.projects.locations.clusters.instances.html
index 50982fec61..1de17c0012 100644
--- a/docs/dyn/alloydb_v1alpha.projects.locations.clusters.instances.html
+++ b/docs/dyn/alloydb_v1alpha.projects.locations.clusters.instances.html
@@ -180,6 +180,7 @@ <h3>Method Details</h3>
     &quot;outgoingServiceAttachmentLinks&quot;: [ # Optional. List of service attachments that this instance has created endpoints to connect with. Currently, only a single outgoing service attachment is supported per instance.
       &quot;A String&quot;,
     ],
+    &quot;pscDnsName&quot;: &quot;A String&quot;, # Output only. The DNS name of the instance for PSC connectivity. Name convention: ...alloydb-psc.goog
     &quot;pscEnabled&quot;: True or False, # Optional. Whether PSC connectivity is enabled for this instance. This is populated by referencing the value from the parent cluster.
     &quot;pscInterfaceConfigs&quot;: [ # Optional. Configurations for setting up PSC interfaces attached to the instance which are used for outbound connectivity. Only primary instances can have PSC interface attached. All the VMs created for the primary instance will share the same configurations. Currently we only support 0 or 1 PSC interface.
       { # Configuration for setting up a PSC interface. This information needs to be provided by the customer. PSC interfaces will be created and added to VMs via SLM (adding a network interface will require recreating the VM). For HA instances this will be done via LDTM.
@@ -314,6 +315,7 @@ <h3>Method Details</h3>
     &quot;outgoingServiceAttachmentLinks&quot;: [ # Optional. List of service attachments that this instance has created endpoints to connect with. Currently, only a single outgoing service attachment is supported per instance.
       &quot;A String&quot;,
     ],
+    &quot;pscDnsName&quot;: &quot;A String&quot;, # Output only. The DNS name of the instance for PSC connectivity. Name convention: ...alloydb-psc.goog
     &quot;pscEnabled&quot;: True or False, # Optional. Whether PSC connectivity is enabled for this instance. This is populated by referencing the value from the parent cluster.
     &quot;pscInterfaceConfigs&quot;: [ # Optional. Configurations for setting up PSC interfaces attached to the instance which are used for outbound connectivity. Only primary instances can have PSC interface attached. All the VMs created for the primary instance will share the same configurations. Currently we only support 0 or 1 PSC interface.
       { # Configuration for setting up a PSC interface. This information needs to be provided by the customer. PSC interfaces will be created and added to VMs via SLM (adding a network interface will require recreating the VM). For HA instances this will be done via LDTM.
@@ -539,6 +541,7 @@ <h3>Method Details</h3>
     &quot;outgoingServiceAttachmentLinks&quot;: [ # Optional. List of service attachments that this instance has created endpoints to connect with. Currently, only a single outgoing service attachment is supported per instance.
       &quot;A String&quot;,
     ],
+    &quot;pscDnsName&quot;: &quot;A String&quot;, # Output only. The DNS name of the instance for PSC connectivity. Name convention: ...alloydb-psc.goog
     &quot;pscEnabled&quot;: True or False, # Optional. Whether PSC connectivity is enabled for this instance. This is populated by referencing the value from the parent cluster.
     &quot;pscInterfaceConfigs&quot;: [ # Optional. Configurations for setting up PSC interfaces attached to the instance which are used for outbound connectivity. Only primary instances can have PSC interface attached. All the VMs created for the primary instance will share the same configurations. Currently we only support 0 or 1 PSC interface.
       { # Configuration for setting up a PSC interface. This information needs to be provided by the customer. PSC interfaces will be created and added to VMs via SLM (adding a network interface will require recreating the VM). For HA instances this will be done via LDTM.
@@ -724,6 +727,7 @@ <h3>Method Details</h3>
         &quot;outgoingServiceAttachmentLinks&quot;: [ # Optional. List of service attachments that this instance has created endpoints to connect with. Currently, only a single outgoing service attachment is supported per instance.
           &quot;A String&quot;,
         ],
+        &quot;pscDnsName&quot;: &quot;A String&quot;, # Output only. The DNS name of the instance for PSC connectivity. Name convention: ...alloydb-psc.goog
         &quot;pscEnabled&quot;: True or False, # Optional. Whether PSC connectivity is enabled for this instance. This is populated by referencing the value from the parent cluster.
         &quot;pscInterfaceConfigs&quot;: [ # Optional. Configurations for setting up PSC interfaces attached to the instance which are used for outbound connectivity. Only primary instances can have PSC interface attached. All the VMs created for the primary instance will share the same configurations. Currently we only support 0 or 1 PSC interface.
           { # Configuration for setting up a PSC interface. This information needs to be provided by the customer. PSC interfaces will be created and added to VMs via SLM (adding a network interface will require recreating the VM). For HA instances this will be done via LDTM.
@@ -847,6 +851,7 @@ <h3>Method Details</h3>
     &quot;outgoingServiceAttachmentLinks&quot;: [ # Optional. List of service attachments that this instance has created endpoints to connect with. Currently, only a single outgoing service attachment is supported per instance.
       &quot;A String&quot;,
     ],
+    &quot;pscDnsName&quot;: &quot;A String&quot;, # Output only. The DNS name of the instance for PSC connectivity. Name convention: ...alloydb-psc.goog
     &quot;pscEnabled&quot;: True or False, # Optional. Whether PSC connectivity is enabled for this instance. This is populated by referencing the value from the parent cluster.
     &quot;pscInterfaceConfigs&quot;: [ # Optional. Configurations for setting up PSC interfaces attached to the instance which are used for outbound connectivity. Only primary instances can have PSC interface attached. All the VMs created for the primary instance will share the same configurations. Currently we only support 0 or 1 PSC interface.
       { # Configuration for setting up a PSC interface. This information needs to be provided by the customer. PSC interfaces will be created and added to VMs via SLM (adding a network interface will require recreating the VM). For HA instances this will be done via LDTM.
diff --git a/docs/dyn/alloydb_v1beta.projects.locations.clusters.instances.html b/docs/dyn/alloydb_v1beta.projects.locations.clusters.instances.html
index c6b42ee6a4..faa104084c 100644
--- a/docs/dyn/alloydb_v1beta.projects.locations.clusters.instances.html
+++ b/docs/dyn/alloydb_v1beta.projects.locations.clusters.instances.html
@@ -180,6 +180,7 @@ <h3>Method Details</h3>
     &quot;outgoingServiceAttachmentLinks&quot;: [ # Optional. List of service attachments that this instance has created endpoints to connect with. Currently, only a single outgoing service attachment is supported per instance.
       &quot;A String&quot;,
     ],
+    &quot;pscDnsName&quot;: &quot;A String&quot;, # Output only. The DNS name of the instance for PSC connectivity. Name convention: ...alloydb-psc.goog
     &quot;pscEnabled&quot;: True or False, # Optional. Whether PSC connectivity is enabled for this instance. This is populated by referencing the value from the parent cluster.
     &quot;pscInterfaceConfigs&quot;: [ # Optional. Configurations for setting up PSC interfaces attached to the instance which are used for outbound connectivity. Only primary instances can have PSC interface attached. All the VMs created for the primary instance will share the same configurations. Currently we only support 0 or 1 PSC interface.
       { # Configuration for setting up a PSC interface. This information needs to be provided by the customer. PSC interfaces will be created and added to VMs via SLM (adding a network interface will require recreating the VM). For HA instances this will be done via LDTM.
@@ -313,6 +314,7 @@ <h3>Method Details</h3>
     &quot;outgoingServiceAttachmentLinks&quot;: [ # Optional. List of service attachments that this instance has created endpoints to connect with. Currently, only a single outgoing service attachment is supported per instance.
       &quot;A String&quot;,
     ],
+    &quot;pscDnsName&quot;: &quot;A String&quot;, # Output only. The DNS name of the instance for PSC connectivity. Name convention: ...alloydb-psc.goog
     &quot;pscEnabled&quot;: True or False, # Optional. Whether PSC connectivity is enabled for this instance. This is populated by referencing the value from the parent cluster.
     &quot;pscInterfaceConfigs&quot;: [ # Optional. Configurations for setting up PSC interfaces attached to the instance which are used for outbound connectivity. Only primary instances can have PSC interface attached. All the VMs created for the primary instance will share the same configurations. Currently we only support 0 or 1 PSC interface.
       { # Configuration for setting up a PSC interface. This information needs to be provided by the customer. PSC interfaces will be created and added to VMs via SLM (adding a network interface will require recreating the VM). For HA instances this will be done via LDTM.
@@ -537,6 +539,7 @@ <h3>Method Details</h3>
     &quot;outgoingServiceAttachmentLinks&quot;: [ # Optional. List of service attachments that this instance has created endpoints to connect with. Currently, only a single outgoing service attachment is supported per instance.
       &quot;A String&quot;,
     ],
+    &quot;pscDnsName&quot;: &quot;A String&quot;, # Output only. The DNS name of the instance for PSC connectivity. Name convention: ...alloydb-psc.goog
     &quot;pscEnabled&quot;: True or False, # Optional. Whether PSC connectivity is enabled for this instance. This is populated by referencing the value from the parent cluster.
     &quot;pscInterfaceConfigs&quot;: [ # Optional. Configurations for setting up PSC interfaces attached to the instance which are used for outbound connectivity. Only primary instances can have PSC interface attached. All the VMs created for the primary instance will share the same configurations. Currently we only support 0 or 1 PSC interface.
       { # Configuration for setting up a PSC interface. This information needs to be provided by the customer. PSC interfaces will be created and added to VMs via SLM (adding a network interface will require recreating the VM). For HA instances this will be done via LDTM.
@@ -721,6 +724,7 @@ <h3>Method Details</h3>
         &quot;outgoingServiceAttachmentLinks&quot;: [ # Optional. List of service attachments that this instance has created endpoints to connect with. Currently, only a single outgoing service attachment is supported per instance.
           &quot;A String&quot;,
         ],
+        &quot;pscDnsName&quot;: &quot;A String&quot;, # Output only. The DNS name of the instance for PSC connectivity. Name convention: ...alloydb-psc.goog
         &quot;pscEnabled&quot;: True or False, # Optional. Whether PSC connectivity is enabled for this instance. This is populated by referencing the value from the parent cluster.
         &quot;pscInterfaceConfigs&quot;: [ # Optional. Configurations for setting up PSC interfaces attached to the instance which are used for outbound connectivity. Only primary instances can have PSC interface attached. All the VMs created for the primary instance will share the same configurations. Currently we only support 0 or 1 PSC interface.
           { # Configuration for setting up a PSC interface. This information needs to be provided by the customer. PSC interfaces will be created and added to VMs via SLM (adding a network interface will require recreating the VM). For HA instances this will be done via LDTM.
@@ -843,6 +847,7 @@ <h3>Method Details</h3>
     &quot;outgoingServiceAttachmentLinks&quot;: [ # Optional. List of service attachments that this instance has created endpoints to connect with. Currently, only a single outgoing service attachment is supported per instance.
       &quot;A String&quot;,
     ],
+    &quot;pscDnsName&quot;: &quot;A String&quot;, # Output only. The DNS name of the instance for PSC connectivity. Name convention: ...alloydb-psc.goog
     &quot;pscEnabled&quot;: True or False, # Optional. Whether PSC connectivity is enabled for this instance. This is populated by referencing the value from the parent cluster.
     &quot;pscInterfaceConfigs&quot;: [ # Optional. Configurations for setting up PSC interfaces attached to the instance which are used for outbound connectivity. Only primary instances can have PSC interface attached. All the VMs created for the primary instance will share the same configurations. Currently we only support 0 or 1 PSC interface.
       { # Configuration for setting up a PSC interface. This information needs to be provided by the customer. PSC interfaces will be created and added to VMs via SLM (adding a network interface will require recreating the VM). For HA instances this will be done via LDTM.
diff --git a/googleapiclient/discovery_cache/documents/alloydb.v1.json b/googleapiclient/discovery_cache/documents/alloydb.v1.json
index 0c2502fd38..93808d0272 100644
--- a/googleapiclient/discovery_cache/documents/alloydb.v1.json
+++ b/googleapiclient/discovery_cache/documents/alloydb.v1.json
@@ -1489,7 +1489,7 @@
 }
 }
 },
-"revision": "20240223",
+"revision": "20240228",
 "rootUrl": "https://alloydb.googleapis.com/",
 "schemas": {
 "AutomatedBackupPolicy": {
@@ -3638,7 +3638,7 @@ false
 },
 "primaryResourceId": {
 "$ref": "StorageDatabasecenterPartnerapiV1mainDatabaseResourceId",
-"description": "Identifier for this resource's immediate parent/primary resource if the current resource is a replica or derived form of another Database resource. Else it would be NULL. REQUIRED if the immediate parent exists when first time resource is getting ingested"
+"description": "Identifier for this resource's immediate parent/primary resource if the current resource is a replica or derived form of another Database resource. Else it would be NULL. REQUIRED if the immediate parent exists when first time resource is getting ingested, otherwise optional."
 },
 "product": {
 "$ref": "StorageDatabasecenterProtoCommonProduct",
diff --git a/googleapiclient/discovery_cache/documents/alloydb.v1alpha.json b/googleapiclient/discovery_cache/documents/alloydb.v1alpha.json
index 9f127594e5..2ea2f4f54a 100644
--- a/googleapiclient/discovery_cache/documents/alloydb.v1alpha.json
+++ b/googleapiclient/discovery_cache/documents/alloydb.v1alpha.json
@@ -1489,7 +1489,7 @@
 }
 }
 },
-"revision": "20240223",
+"revision": "20240228",
 "rootUrl": "https://alloydb.googleapis.com/",
 "schemas": {
 "AuthorizedNetwork": {
@@ -2924,6 +2924,11 @@ false
 },
 "type": "array"
 },
+"pscDnsName": {
+"description": "Output only. The DNS name of the instance for PSC connectivity. Name convention: ...alloydb-psc.goog",
+"readOnly": true,
+"type": "string"
+},
 "pscEnabled": {
 "description": "Optional. Whether PSC connectivity is enabled for this instance. This is populated by referencing the value from the parent cluster.",
 "type": "boolean"
@@ -3806,7 +3811,7 @@ false
 },
 "primaryResourceId": {
 "$ref": "StorageDatabasecenterPartnerapiV1mainDatabaseResourceId",
-"description": "Identifier for this resource's immediate parent/primary resource if the current resource is a replica or derived form of another Database resource. Else it would be NULL. REQUIRED if the immediate parent exists when first time resource is getting ingested"
+"description": "Identifier for this resource's immediate parent/primary resource if the current resource is a replica or derived form of another Database resource. Else it would be NULL. REQUIRED if the immediate parent exists when first time resource is getting ingested, otherwise optional."
 },
 "product": {
 "$ref": "StorageDatabasecenterProtoCommonProduct",
diff --git a/googleapiclient/discovery_cache/documents/alloydb.v1beta.json b/googleapiclient/discovery_cache/documents/alloydb.v1beta.json
index e31cd0ea12..552af6ff96 100644
--- a/googleapiclient/discovery_cache/documents/alloydb.v1beta.json
+++ b/googleapiclient/discovery_cache/documents/alloydb.v1beta.json
@@ -1486,7 +1486,7 @@
 }
 }
 },
-"revision": "20240223",
+"revision": "20240228",
 "rootUrl": "https://alloydb.googleapis.com/",
 "schemas": {
 "AuthorizedNetwork": {
@@ -2900,6 +2900,11 @@ false
 },
 "type": "array"
 },
+"pscDnsName": {
+"description": "Output only. The DNS name of the instance for PSC connectivity. Name convention: ...alloydb-psc.goog",
+"readOnly": true,
+"type": "string"
+},
 "pscEnabled": {
 "description": "Optional. Whether PSC connectivity is enabled for this instance. This is populated by referencing the value from the parent cluster.",
 "type": "boolean"
@@ -3782,7 +3787,7 @@ false
 },
 "primaryResourceId": {
 "$ref": "StorageDatabasecenterPartnerapiV1mainDatabaseResourceId",
-"description": "Identifier for this resource's immediate parent/primary resource if the current resource is a replica or derived form of another Database resource. Else it would be NULL. REQUIRED if the immediate parent exists when first time resource is getting ingested"
+"description": "Identifier for this resource's immediate parent/primary resource if the current resource is a replica or derived form of another Database resource. Else it would be NULL. REQUIRED if the immediate parent exists when first time resource is getting ingested, otherwise optional."
 },
 "product": {
 "$ref": "StorageDatabasecenterProtoCommonProduct",