feat(gkeonprem): update the api

#### gkeonprem:v1

The following keys were deleted:
- schemas.EnrollVmwareAdminClusterRequest.properties.localName.type (Total Keys: 1)

The following keys were added:
- resources.projects.resources.locations.resources.bareMetalClusters.resources.bareMetalNodePools.methods.get.parameters.view (Total Keys: 2)
- resources.projects.resources.locations.resources.bareMetalClusters.resources.bareMetalNodePools.methods.list.parameters.view (Total Keys: 2)
- resources.projects.resources.locations.resources.bareMetalClusters.resources.bareMetalNodePools.methods.patch.parameters.allowMissing (Total Keys: 2)
- resources.projects.resources.locations.resources.bareMetalStandaloneClusters.resources.bareMetalStandaloneNodePools.methods.enroll (Total Keys: 12)
- resources.projects.resources.locations.resources.vmwareAdminClusters.methods.get.parameters.view (Total Keys: 2)
- resources.projects.resources.locations.resources.vmwareClusters.resources.vmwareNodePools.methods.get.parameters.view (Total Keys: 2)
- resources.projects.resources.locations.resources.vmwareClusters.resources.vmwareNodePools.methods.list.parameters.view (Total Keys: 2)
- resources.projects.resources.locations.resources.vmwareClusters.resources.vmwareNodePools.methods.unenroll.parameters.allowMissing (Total Keys: 2)
- schemas.EnrollBareMetalStandaloneNodePoolRequest (Total Keys: 4)
- schemas.OperationMetadata.properties.controlPlaneDisconnected (Total Keys: 2)

Author: yoshi-automation

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

@@ -147,7 +147,7 @@ <h3>Method Details</h3>
     ],
     &quot;controlPlaneNodePoolConfig&quot;: { # BareMetalAdminControlPlaneNodePoolConfig specifies the control plane node pool configuration. We have a control plane specific node pool config so that we can flexible about supporting control plane specific fields in the future. # Configures the node pool running the control plane. If specified the corresponding NodePool will be created for the cluster&#x27;s control plane. The NodePool will have the same name and namespace as the cluster.
       &quot;nodePoolConfig&quot;: { # BareMetalNodePoolConfig describes the configuration of all nodes within a given bare metal node pool. # The generic configuration for a node pool running the control plane.
-        &quot;kubeletConfig&quot;: { # KubeletConfig defines the modifiable kubelet configurations for baremetal machines. Note: this list includes fields supported in GKE (see https://cloud.google.com/kubernetes-engine/docs/how-to/node-system-config#kubelet-options). # The modifiable kubelet configurations for the baremetal machines.
+        &quot;kubeletConfig&quot;: { # KubeletConfig defines the modifiable kubelet configurations for bare metal machines. Note: this list includes fields supported in GKE (see https://cloud.google.com/kubernetes-engine/docs/how-to/node-system-config#kubelet-options). # The modifiable kubelet configurations for the bare metal machines.
           &quot;registryBurst&quot;: 42, # The maximum size of bursty pulls, temporarily allows pulls to burst to this number, while still not exceeding registry_pull_qps. The value must not be a negative number. Updating this field may impact scalability by changing the amount of traffic produced by image pulls. Defaults to 10.
           &quot;registryPullQps&quot;: 42, # The limit of registry pulls per second. Setting this value to 0 means no limit. Updating this field may impact scalability by changing the amount of traffic produced by image pulls. Defaults to 5.
           &quot;serializeImagePullsDisabled&quot;: True or False, # Prevents the Kubelet from pulling multiple images at a time. We recommend *not* changing the default value on nodes that run docker daemon with version &lt; 1.9 or an Another Union File System (Aufs) storage backend. Issue https://github.com/kubernetes/kubernetes/issues/10959 has more details.
@@ -243,7 +243,7 @@ <h3>Method Details</h3>
   &quot;reconciling&quot;: True or False, # Output only. If set, there are currently changes in flight to the bare metal Admin Cluster.
   &quot;securityConfig&quot;: { # Specifies the security related settings for the bare metal admin cluster. # Security related configuration.
     &quot;authorization&quot;: { # Authorization defines the On-Prem cluster authorization configuration to bootstrap onto the admin cluster. # Configures user access to the admin cluster.
-      &quot;adminUsers&quot;: [ # Required. For VMware user, bare metal user and standalone clusters, users that will be granted the cluster-admin role on the cluster, providing full access to the cluster. For bare metal Admin cluster, users will be granted the view role, which is a view only access.
+      &quot;adminUsers&quot;: [ # Required. For VMware and bare metal user clusters, users will be granted the cluster-admin role on the cluster, which provides full administrative access to the cluster. For bare metal admin clusters, users will be granted the cluster-view role, which limits users to read-only access.
         { # ClusterUser configures user principals for an RBAC policy.
           &quot;username&quot;: &quot;A String&quot;, # Required. The name of the user, e.g. `[email protected]`.
         },
@@ -405,7 +405,7 @@ <h3>Method Details</h3>
     ],
     &quot;controlPlaneNodePoolConfig&quot;: { # BareMetalAdminControlPlaneNodePoolConfig specifies the control plane node pool configuration. We have a control plane specific node pool config so that we can flexible about supporting control plane specific fields in the future. # Configures the node pool running the control plane. If specified the corresponding NodePool will be created for the cluster&#x27;s control plane. The NodePool will have the same name and namespace as the cluster.
       &quot;nodePoolConfig&quot;: { # BareMetalNodePoolConfig describes the configuration of all nodes within a given bare metal node pool. # The generic configuration for a node pool running the control plane.
-        &quot;kubeletConfig&quot;: { # KubeletConfig defines the modifiable kubelet configurations for baremetal machines. Note: this list includes fields supported in GKE (see https://cloud.google.com/kubernetes-engine/docs/how-to/node-system-config#kubelet-options). # The modifiable kubelet configurations for the baremetal machines.
+        &quot;kubeletConfig&quot;: { # KubeletConfig defines the modifiable kubelet configurations for bare metal machines. Note: this list includes fields supported in GKE (see https://cloud.google.com/kubernetes-engine/docs/how-to/node-system-config#kubelet-options). # The modifiable kubelet configurations for the bare metal machines.
           &quot;registryBurst&quot;: 42, # The maximum size of bursty pulls, temporarily allows pulls to burst to this number, while still not exceeding registry_pull_qps. The value must not be a negative number. Updating this field may impact scalability by changing the amount of traffic produced by image pulls. Defaults to 10.
           &quot;registryPullQps&quot;: 42, # The limit of registry pulls per second. Setting this value to 0 means no limit. Updating this field may impact scalability by changing the amount of traffic produced by image pulls. Defaults to 5.
           &quot;serializeImagePullsDisabled&quot;: True or False, # Prevents the Kubelet from pulling multiple images at a time. We recommend *not* changing the default value on nodes that run docker daemon with version &lt; 1.9 or an Another Union File System (Aufs) storage backend. Issue https://github.com/kubernetes/kubernetes/issues/10959 has more details.
@@ -501,7 +501,7 @@ <h3>Method Details</h3>
   &quot;reconciling&quot;: True or False, # Output only. If set, there are currently changes in flight to the bare metal Admin Cluster.
   &quot;securityConfig&quot;: { # Specifies the security related settings for the bare metal admin cluster. # Security related configuration.
     &quot;authorization&quot;: { # Authorization defines the On-Prem cluster authorization configuration to bootstrap onto the admin cluster. # Configures user access to the admin cluster.
-      &quot;adminUsers&quot;: [ # Required. For VMware user, bare metal user and standalone clusters, users that will be granted the cluster-admin role on the cluster, providing full access to the cluster. For bare metal Admin cluster, users will be granted the view role, which is a view only access.
+      &quot;adminUsers&quot;: [ # Required. For VMware and bare metal user clusters, users will be granted the cluster-admin role on the cluster, which provides full administrative access to the cluster. For bare metal admin clusters, users will be granted the cluster-view role, which limits users to read-only access.
         { # ClusterUser configures user principals for an RBAC policy.
           &quot;username&quot;: &quot;A String&quot;, # Required. The name of the user, e.g. `[email protected]`.
         },
@@ -629,7 +629,7 @@ <h3>Method Details</h3>
         ],
         &quot;controlPlaneNodePoolConfig&quot;: { # BareMetalAdminControlPlaneNodePoolConfig specifies the control plane node pool configuration. We have a control plane specific node pool config so that we can flexible about supporting control plane specific fields in the future. # Configures the node pool running the control plane. If specified the corresponding NodePool will be created for the cluster&#x27;s control plane. The NodePool will have the same name and namespace as the cluster.
           &quot;nodePoolConfig&quot;: { # BareMetalNodePoolConfig describes the configuration of all nodes within a given bare metal node pool. # The generic configuration for a node pool running the control plane.
-            &quot;kubeletConfig&quot;: { # KubeletConfig defines the modifiable kubelet configurations for baremetal machines. Note: this list includes fields supported in GKE (see https://cloud.google.com/kubernetes-engine/docs/how-to/node-system-config#kubelet-options). # The modifiable kubelet configurations for the baremetal machines.
+            &quot;kubeletConfig&quot;: { # KubeletConfig defines the modifiable kubelet configurations for bare metal machines. Note: this list includes fields supported in GKE (see https://cloud.google.com/kubernetes-engine/docs/how-to/node-system-config#kubelet-options). # The modifiable kubelet configurations for the bare metal machines.
               &quot;registryBurst&quot;: 42, # The maximum size of bursty pulls, temporarily allows pulls to burst to this number, while still not exceeding registry_pull_qps. The value must not be a negative number. Updating this field may impact scalability by changing the amount of traffic produced by image pulls. Defaults to 10.
               &quot;registryPullQps&quot;: 42, # The limit of registry pulls per second. Setting this value to 0 means no limit. Updating this field may impact scalability by changing the amount of traffic produced by image pulls. Defaults to 5.
               &quot;serializeImagePullsDisabled&quot;: True or False, # Prevents the Kubelet from pulling multiple images at a time. We recommend *not* changing the default value on nodes that run docker daemon with version &lt; 1.9 or an Another Union File System (Aufs) storage backend. Issue https://github.com/kubernetes/kubernetes/issues/10959 has more details.
@@ -725,7 +725,7 @@ <h3>Method Details</h3>
       &quot;reconciling&quot;: True or False, # Output only. If set, there are currently changes in flight to the bare metal Admin Cluster.
       &quot;securityConfig&quot;: { # Specifies the security related settings for the bare metal admin cluster. # Security related configuration.
         &quot;authorization&quot;: { # Authorization defines the On-Prem cluster authorization configuration to bootstrap onto the admin cluster. # Configures user access to the admin cluster.
-          &quot;adminUsers&quot;: [ # Required. For VMware user, bare metal user and standalone clusters, users that will be granted the cluster-admin role on the cluster, providing full access to the cluster. For bare metal Admin cluster, users will be granted the view role, which is a view only access.
+          &quot;adminUsers&quot;: [ # Required. For VMware and bare metal user clusters, users will be granted the cluster-admin role on the cluster, which provides full administrative access to the cluster. For bare metal admin clusters, users will be granted the cluster-view role, which limits users to read-only access.
             { # ClusterUser configures user principals for an RBAC policy.
               &quot;username&quot;: &quot;A String&quot;, # Required. The name of the user, e.g. `[email protected]`.
             },
@@ -824,7 +824,7 @@ <h3>Method Details</h3>
     ],
     &quot;controlPlaneNodePoolConfig&quot;: { # BareMetalAdminControlPlaneNodePoolConfig specifies the control plane node pool configuration. We have a control plane specific node pool config so that we can flexible about supporting control plane specific fields in the future. # Configures the node pool running the control plane. If specified the corresponding NodePool will be created for the cluster&#x27;s control plane. The NodePool will have the same name and namespace as the cluster.
       &quot;nodePoolConfig&quot;: { # BareMetalNodePoolConfig describes the configuration of all nodes within a given bare metal node pool. # The generic configuration for a node pool running the control plane.
-        &quot;kubeletConfig&quot;: { # KubeletConfig defines the modifiable kubelet configurations for baremetal machines. Note: this list includes fields supported in GKE (see https://cloud.google.com/kubernetes-engine/docs/how-to/node-system-config#kubelet-options). # The modifiable kubelet configurations for the baremetal machines.
+        &quot;kubeletConfig&quot;: { # KubeletConfig defines the modifiable kubelet configurations for bare metal machines. Note: this list includes fields supported in GKE (see https://cloud.google.com/kubernetes-engine/docs/how-to/node-system-config#kubelet-options). # The modifiable kubelet configurations for the bare metal machines.
           &quot;registryBurst&quot;: 42, # The maximum size of bursty pulls, temporarily allows pulls to burst to this number, while still not exceeding registry_pull_qps. The value must not be a negative number. Updating this field may impact scalability by changing the amount of traffic produced by image pulls. Defaults to 10.
           &quot;registryPullQps&quot;: 42, # The limit of registry pulls per second. Setting this value to 0 means no limit. Updating this field may impact scalability by changing the amount of traffic produced by image pulls. Defaults to 5.
           &quot;serializeImagePullsDisabled&quot;: True or False, # Prevents the Kubelet from pulling multiple images at a time. We recommend *not* changing the default value on nodes that run docker daemon with version &lt; 1.9 or an Another Union File System (Aufs) storage backend. Issue https://github.com/kubernetes/kubernetes/issues/10959 has more details.
@@ -920,7 +920,7 @@ <h3>Method Details</h3>
   &quot;reconciling&quot;: True or False, # Output only. If set, there are currently changes in flight to the bare metal Admin Cluster.
   &quot;securityConfig&quot;: { # Specifies the security related settings for the bare metal admin cluster. # Security related configuration.
     &quot;authorization&quot;: { # Authorization defines the On-Prem cluster authorization configuration to bootstrap onto the admin cluster. # Configures user access to the admin cluster.
-      &quot;adminUsers&quot;: [ # Required. For VMware user, bare metal user and standalone clusters, users that will be granted the cluster-admin role on the cluster, providing full access to the cluster. For bare metal Admin cluster, users will be granted the view role, which is a view only access.
+      &quot;adminUsers&quot;: [ # Required. For VMware and bare metal user clusters, users will be granted the cluster-admin role on the cluster, which provides full administrative access to the cluster. For bare metal admin clusters, users will be granted the cluster-view role, which limits users to read-only access.
         { # ClusterUser configures user principals for an RBAC policy.
           &quot;username&quot;: &quot;A String&quot;, # Required. The name of the user, e.g. `[email protected]`.
         },