feat(gkeonprem): update the api

#### gkeonprem:v1

The following keys were added:
- schemas.EnrollBareMetalClusterRequest.properties.localNamespace.type (Total Keys: 1)
- schemas.VmwareAdminCluster.properties.privateRegistryConfig.$ref (Total Keys: 1)
- schemas.VmwareAdminPrivateRegistryConfig (Total Keys: 4)

Author: yoshi-automation

docs/dyn/gkeonprem_v1.projects.locations.bareMetalClusters.html

@@ -506,6 +506,7 @@ <h3>Method Details</h3>
   &quot;adminClusterMembership&quot;: &quot;A String&quot;, # Required. The admin cluster this bare metal user cluster belongs to. This is the full resource name of the admin cluster&#x27;s fleet membership. In the future, references to other resource types might be allowed if admin clusters are modeled as their own resources.
   &quot;bareMetalClusterId&quot;: &quot;A String&quot;, # User provided OnePlatform identifier that is used as part of the resource name. This must be unique among all bare metal clusters within a project and location and will return a 409 if the cluster already exists. (https://tools.ietf.org/html/rfc1123) format.
   &quot;localName&quot;: &quot;A String&quot;, # Optional. The object name of the bare metal cluster custom resource on the associated admin cluster. This field is used to support conflicting resource names when enrolling existing clusters to the API. When not provided, this field will resolve to the bare_metal_cluster_id. Otherwise, it must match the object name of the bare metal cluster custom resource. It is not modifiable outside / beyond the enrollment operation.
+  &quot;localNamespace&quot;: &quot;A String&quot;, # Optional. The namespace of the cluster.
 }
 
   x__xgafv: string, V1 error format.

docs/dyn/gkeonprem_v1.projects.locations.vmwareAdminClusters.html

@@ -312,6 +312,10 @@ <h3>Method Details</h3>
   &quot;preparedSecrets&quot;: { # VmwareAdminPreparedSecretsConfig represents configuration for admin cluster prepared secrets. # Output only. The VMware admin cluster prepared secrets configuration. It should always be enabled by the Central API, instead of letting users set it.
     &quot;enabled&quot;: True or False, # Whether prepared secrets is enabled.
   },
+  &quot;privateRegistryConfig&quot;: { # VmwareAdminPrivateRegistryConfig represents configuration for admin cluster registry. # Configuration for registry.
+    &quot;address&quot;: &quot;A String&quot;, # The registry address.
+    &quot;caCert&quot;: &quot;A String&quot;, # When the container runtime pulls an image from private registry, the registry must prove its identity by presenting a certificate. The registry&#x27;s certificate is signed by a certificate authority (CA). The container runtime uses the CA&#x27;s certificate to validate the registry&#x27;s certificate.
+  },
   &quot;reconciling&quot;: True or False, # Output only. If set, there are currently changes in flight to the VMware admin cluster.
   &quot;state&quot;: &quot;A String&quot;, # Output only. The current state of VMware admin cluster.
   &quot;status&quot;: { # ResourceStatus describes why a cluster or node pool has a certain status. (e.g., ERROR or DEGRADED). # Output only. ResourceStatus representing detailed cluster state.
@@ -645,6 +649,10 @@ <h3>Method Details</h3>
   &quot;preparedSecrets&quot;: { # VmwareAdminPreparedSecretsConfig represents configuration for admin cluster prepared secrets. # Output only. The VMware admin cluster prepared secrets configuration. It should always be enabled by the Central API, instead of letting users set it.
     &quot;enabled&quot;: True or False, # Whether prepared secrets is enabled.
   },
+  &quot;privateRegistryConfig&quot;: { # VmwareAdminPrivateRegistryConfig represents configuration for admin cluster registry. # Configuration for registry.
+    &quot;address&quot;: &quot;A String&quot;, # The registry address.
+    &quot;caCert&quot;: &quot;A String&quot;, # When the container runtime pulls an image from private registry, the registry must prove its identity by presenting a certificate. The registry&#x27;s certificate is signed by a certificate authority (CA). The container runtime uses the CA&#x27;s certificate to validate the registry&#x27;s certificate.
+  },
   &quot;reconciling&quot;: True or False, # Output only. If set, there are currently changes in flight to the VMware admin cluster.
   &quot;state&quot;: &quot;A String&quot;, # Output only. The current state of VMware admin cluster.
   &quot;status&quot;: { # ResourceStatus describes why a cluster or node pool has a certain status. (e.g., ERROR or DEGRADED). # Output only. ResourceStatus representing detailed cluster state.
@@ -947,6 +955,10 @@ <h3>Method Details</h3>
       &quot;preparedSecrets&quot;: { # VmwareAdminPreparedSecretsConfig represents configuration for admin cluster prepared secrets. # Output only. The VMware admin cluster prepared secrets configuration. It should always be enabled by the Central API, instead of letting users set it.
         &quot;enabled&quot;: True or False, # Whether prepared secrets is enabled.
       },
+      &quot;privateRegistryConfig&quot;: { # VmwareAdminPrivateRegistryConfig represents configuration for admin cluster registry. # Configuration for registry.
+        &quot;address&quot;: &quot;A String&quot;, # The registry address.
+        &quot;caCert&quot;: &quot;A String&quot;, # When the container runtime pulls an image from private registry, the registry must prove its identity by presenting a certificate. The registry&#x27;s certificate is signed by a certificate authority (CA). The container runtime uses the CA&#x27;s certificate to validate the registry&#x27;s certificate.
+      },
       &quot;reconciling&quot;: True or False, # Output only. If set, there are currently changes in flight to the VMware admin cluster.
       &quot;state&quot;: &quot;A String&quot;, # Output only. The current state of VMware admin cluster.
       &quot;status&quot;: { # ResourceStatus describes why a cluster or node pool has a certain status. (e.g., ERROR or DEGRADED). # Output only. ResourceStatus representing detailed cluster state.
@@ -1211,6 +1223,10 @@ <h3>Method Details</h3>
   &quot;preparedSecrets&quot;: { # VmwareAdminPreparedSecretsConfig represents configuration for admin cluster prepared secrets. # Output only. The VMware admin cluster prepared secrets configuration. It should always be enabled by the Central API, instead of letting users set it.
     &quot;enabled&quot;: True or False, # Whether prepared secrets is enabled.
   },
+  &quot;privateRegistryConfig&quot;: { # VmwareAdminPrivateRegistryConfig represents configuration for admin cluster registry. # Configuration for registry.
+    &quot;address&quot;: &quot;A String&quot;, # The registry address.
+    &quot;caCert&quot;: &quot;A String&quot;, # When the container runtime pulls an image from private registry, the registry must prove its identity by presenting a certificate. The registry&#x27;s certificate is signed by a certificate authority (CA). The container runtime uses the CA&#x27;s certificate to validate the registry&#x27;s certificate.
+  },
   &quot;reconciling&quot;: True or False, # Output only. If set, there are currently changes in flight to the VMware admin cluster.
   &quot;state&quot;: &quot;A String&quot;, # Output only. The current state of VMware admin cluster.
   &quot;status&quot;: { # ResourceStatus describes why a cluster or node pool has a certain status. (e.g., ERROR or DEGRADED). # Output only. ResourceStatus representing detailed cluster state.

googleapiclient/discovery_cache/documents/gkeonprem.v1.json

@@ -3100,7 +3100,7 @@
 }
 }
 },
-"revision": "20250423",
+"revision": "20250519",
 "rootUrl": "https://gkeonprem.googleapis.com/",
 "schemas": {
 "Authorization": {
@@ -4578,6 +4578,10 @@
 "localName": {
 "description": "Optional. The object name of the bare metal cluster custom resource on the associated admin cluster. This field is used to support conflicting resource names when enrolling existing clusters to the API. When not provided, this field will resolve to the bare_metal_cluster_id. Otherwise, it must match the object name of the bare metal cluster custom resource. It is not modifiable outside / beyond the enrollment operation.",
 "type": "string"
+},
+"localNamespace": {
+"description": "Optional. The namespace of the cluster.",
+"type": "string"
 }
 },
 "type": "object"
@@ -5682,6 +5686,10 @@
 "description": "Output only. The VMware admin cluster prepared secrets configuration. It should always be enabled by the Central API, instead of letting users set it.",
 "readOnly": true
 },
+"privateRegistryConfig": {
+"$ref": "VmwareAdminPrivateRegistryConfig",
+"description": "Configuration for registry."
+},
 "reconciling": {
 "description": "Output only. If set, there are currently changes in flight to the VMware admin cluster.",
 "readOnly": true,
@@ -5912,6 +5920,21 @@
 },
 "type": "object"
 },
+"VmwareAdminPrivateRegistryConfig": {
+"description": "VmwareAdminPrivateRegistryConfig represents configuration for admin cluster registry.",
+"id": "VmwareAdminPrivateRegistryConfig",
+"properties": {
+"address": {
+"description": "The registry address.",
+"type": "string"
+},
+"caCert": {
+"description": "When the container runtime pulls an image from private registry, the registry must prove its identity by presenting a certificate. The registry's certificate is signed by a certificate authority (CA). The container runtime uses the CA's certificate to validate the registry's certificate.",
+"type": "string"
+}
+},
+"type": "object"
+},
 "VmwareAdminSeesawConfig": {
 "description": "VmwareSeesawConfig represents configuration parameters for an already existing Seesaw load balancer. IMPORTANT: Please note that the Anthos On-Prem API will not generate or update Seesaw configurations it can only bind a pre-existing configuration to a new user cluster. IMPORTANT: When attempting to create a user cluster with a pre-existing Seesaw load balancer you will need to follow some preparation steps before calling the 'CreateVmwareCluster' API method. First you will need to create the user cluster's namespace via kubectl. The namespace will need to use the following naming convention : -gke-onprem-mgmt or -gke-onprem-mgmt depending on whether you used the 'VmwareCluster.local_name' to disambiguate collisions; for more context see the documentation of 'VmwareCluster.local_name'. Once the namespace is created you will need to create a secret resource via kubectl. This secret will contain copies of your Seesaw credentials. The Secret must be called 'user-cluster-creds' and contain Seesaw's SSH and Cert credentials. The credentials must be keyed with the following names: 'seesaw-ssh-private-key', 'seesaw-ssh-public-key', 'seesaw-ssh-ca-key', 'seesaw-ssh-ca-cert'.",
 "id": "VmwareAdminSeesawConfig",