feat(gkeonprem): update the api

#### gkeonprem:v1

The following keys were added:
- schemas.VmwareAdminMetalLbConfig.properties.enabled.type (Total Keys: 1)

Author: yoshi-automation

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

@@ -177,6 +177,7 @@ <h3>Method Details</h3>
       &quot;konnectivityServerNodePort&quot;: 42, # NodePort for konnectivity server service running as a sidecar in each kube-apiserver pod (ex. 30564).
     },
     &quot;metalLbConfig&quot;: { # VmwareAdminMetalLbConfig represents configuration parameters for a MetalLB load balancer. For admin clusters, currently no configurations is needed. # MetalLB load balancers.
+      &quot;enabled&quot;: True or False, # Whether MetalLB is enabled.
     },
     &quot;seesawConfig&quot;: { # 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 &#x27;CreateVmwareCluster&#x27; API method. First you will need to create the user cluster&#x27;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 &#x27;VmwareCluster.local_name&#x27; to disambiguate collisions; for more context see the documentation of &#x27;VmwareCluster.local_name&#x27;. 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 &#x27;user-cluster-creds&#x27; and contain Seesaw&#x27;s SSH and Cert credentials. The credentials must be keyed with the following names: &#x27;seesaw-ssh-private-key&#x27;, &#x27;seesaw-ssh-public-key&#x27;, &#x27;seesaw-ssh-ca-key&#x27;, &#x27;seesaw-ssh-ca-cert&#x27;. # Output only. Configuration for Seesaw typed load balancers.
       &quot;enableHa&quot;: True or False, # Enable two load balancer VMs to achieve a highly-available Seesaw load balancer.
@@ -508,6 +509,7 @@ <h3>Method Details</h3>
       &quot;konnectivityServerNodePort&quot;: 42, # NodePort for konnectivity server service running as a sidecar in each kube-apiserver pod (ex. 30564).
     },
     &quot;metalLbConfig&quot;: { # VmwareAdminMetalLbConfig represents configuration parameters for a MetalLB load balancer. For admin clusters, currently no configurations is needed. # MetalLB load balancers.
+      &quot;enabled&quot;: True or False, # Whether MetalLB is enabled.
     },
     &quot;seesawConfig&quot;: { # 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 &#x27;CreateVmwareCluster&#x27; API method. First you will need to create the user cluster&#x27;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 &#x27;VmwareCluster.local_name&#x27; to disambiguate collisions; for more context see the documentation of &#x27;VmwareCluster.local_name&#x27;. 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 &#x27;user-cluster-creds&#x27; and contain Seesaw&#x27;s SSH and Cert credentials. The credentials must be keyed with the following names: &#x27;seesaw-ssh-private-key&#x27;, &#x27;seesaw-ssh-public-key&#x27;, &#x27;seesaw-ssh-ca-key&#x27;, &#x27;seesaw-ssh-ca-cert&#x27;. # Output only. Configuration for Seesaw typed load balancers.
       &quot;enableHa&quot;: True or False, # Enable two load balancer VMs to achieve a highly-available Seesaw load balancer.
@@ -808,6 +810,7 @@ <h3>Method Details</h3>
           &quot;konnectivityServerNodePort&quot;: 42, # NodePort for konnectivity server service running as a sidecar in each kube-apiserver pod (ex. 30564).
         },
         &quot;metalLbConfig&quot;: { # VmwareAdminMetalLbConfig represents configuration parameters for a MetalLB load balancer. For admin clusters, currently no configurations is needed. # MetalLB load balancers.
+          &quot;enabled&quot;: True or False, # Whether MetalLB is enabled.
         },
         &quot;seesawConfig&quot;: { # 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 &#x27;CreateVmwareCluster&#x27; API method. First you will need to create the user cluster&#x27;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 &#x27;VmwareCluster.local_name&#x27; to disambiguate collisions; for more context see the documentation of &#x27;VmwareCluster.local_name&#x27;. 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 &#x27;user-cluster-creds&#x27; and contain Seesaw&#x27;s SSH and Cert credentials. The credentials must be keyed with the following names: &#x27;seesaw-ssh-private-key&#x27;, &#x27;seesaw-ssh-public-key&#x27;, &#x27;seesaw-ssh-ca-key&#x27;, &#x27;seesaw-ssh-ca-cert&#x27;. # Output only. Configuration for Seesaw typed load balancers.
           &quot;enableHa&quot;: True or False, # Enable two load balancer VMs to achieve a highly-available Seesaw load balancer.
@@ -1070,6 +1073,7 @@ <h3>Method Details</h3>
       &quot;konnectivityServerNodePort&quot;: 42, # NodePort for konnectivity server service running as a sidecar in each kube-apiserver pod (ex. 30564).
     },
     &quot;metalLbConfig&quot;: { # VmwareAdminMetalLbConfig represents configuration parameters for a MetalLB load balancer. For admin clusters, currently no configurations is needed. # MetalLB load balancers.
+      &quot;enabled&quot;: True or False, # Whether MetalLB is enabled.
     },
     &quot;seesawConfig&quot;: { # 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 &#x27;CreateVmwareCluster&#x27; API method. First you will need to create the user cluster&#x27;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 &#x27;VmwareCluster.local_name&#x27; to disambiguate collisions; for more context see the documentation of &#x27;VmwareCluster.local_name&#x27;. 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 &#x27;user-cluster-creds&#x27; and contain Seesaw&#x27;s SSH and Cert credentials. The credentials must be keyed with the following names: &#x27;seesaw-ssh-private-key&#x27;, &#x27;seesaw-ssh-public-key&#x27;, &#x27;seesaw-ssh-ca-key&#x27;, &#x27;seesaw-ssh-ca-cert&#x27;. # Output only. Configuration for Seesaw typed load balancers.
       &quot;enableHa&quot;: True or False, # Enable two load balancer VMs to achieve a highly-available Seesaw load balancer.

googleapiclient/discovery_cache/documents/gkeonprem.v1.json

@@ -3094,7 +3094,7 @@
 }
 }
 },
-"revision": "20241023",
+"revision": "20241110",
 "rootUrl": "https://gkeonprem.googleapis.com/",
 "schemas": {
 "Authorization": {
@@ -5837,7 +5837,12 @@
 "VmwareAdminMetalLbConfig": {
 "description": "VmwareAdminMetalLbConfig represents configuration parameters for a MetalLB load balancer. For admin clusters, currently no configurations is needed.",
 "id": "VmwareAdminMetalLbConfig",
-"properties": {},
+"properties": {
+"enabled": {
+"description": "Whether MetalLB is enabled.",
+"type": "boolean"
+}
+},
 "type": "object"
 },
 "VmwareAdminNetworkConfig": {