feat(container): update the api

#### container:v1

The following keys were added:
- schemas.MemoryManager (Total Keys: 3)
- schemas.NodeKubeletConfig.properties.memoryManager.$ref (Total Keys: 1)
- schemas.NodeKubeletConfig.properties.topologyManager.$ref (Total Keys: 1)
- schemas.TopologyManager (Total Keys: 4)

#### container:v1beta1

The following keys were added:
- schemas.MemoryManager (Total Keys: 3)
- schemas.NodeKubeletConfig.properties.memoryManager.$ref (Total Keys: 1)
- schemas.NodeKubeletConfig.properties.topologyManager.$ref (Total Keys: 1)
- schemas.TopologyManager (Total Keys: 4)

Author: yoshi-automation

docs/dyn/container_v1.projects.locations.clusters.html

@@ -2660,7 +2660,7 @@
 }
 }
 },
-"revision": "20250408",
+"revision": "20250429",
 "rootUrl": "https://container.googleapis.com/",
 "schemas": {
 "AcceleratorConfig": {
@@ -5501,6 +5501,17 @@ false
 },
 "type": "object"
 },
+"MemoryManager": {
+"description": "The option enables the Kubernetes NUMA-aware Memory Manager feature. Detailed description about the feature can be found [here](https://kubernetes.io/docs/tasks/administer-cluster/memory-manager/).",
+"id": "MemoryManager",
+"properties": {
+"policy": {
+"description": "Controls the memory management policy on the Node. See https://kubernetes.io/docs/tasks/administer-cluster/memory-manager/#policies The following values are allowed. * \"none\" * \"static\" The default value is 'none' if unspecified.",
+"type": "string"
+}
+},
+"type": "object"
+},
 "MeshCertificates": {
 "description": "Configuration for issuance of mTLS keys and certificates to Kubernetes pods.",
 "id": "MeshCertificates",
@@ -6123,10 +6134,18 @@ false
 "description": "Enable or disable Kubelet read only port.",
 "type": "boolean"
 },
+"memoryManager": {
+"$ref": "MemoryManager",
+"description": "Optional. Controls NUMA-aware Memory Manager configuration on the node. For more information, see: https://kubernetes.io/docs/tasks/administer-cluster/memory-manager/"
+},
 "podPidsLimit": {
 "description": "Set the Pod PID limits. See https://kubernetes.io/docs/concepts/policy/pid-limiting/#pod-pid-limits Controls the maximum number of processes allowed to run in a pod. The value must be greater than or equal to 1024 and less than 4194304.",
 "format": "int64",
 "type": "string"
+},
+"topologyManager": {
+"$ref": "TopologyManager",
+"description": "Optional. Controls Topology Manager configuration on the node. For more information, see: https://kubernetes.io/docs/tasks/administer-cluster/topology-manager/"
 }
 },
 "type": "object"
@@ -8125,6 +8144,21 @@ false
 },
 "type": "object"
 },
+"TopologyManager": {
+"description": "TopologyManager defines the configuration options for Topology Manager feature. See https://kubernetes.io/docs/tasks/administer-cluster/topology-manager/",
+"id": "TopologyManager",
+"properties": {
+"policy": {
+"description": "Configures the strategy for resource alignment. Allowed values are: * none: the default policy, and does not perform any topology alignment. * restricted: the topology manager stores the preferred NUMA node affinity for the container, and will reject the pod if the affinity if not preferred. * best-effort: the topology manager stores the preferred NUMA node affinity for the container. If the affinity is not preferred, the topology manager will admit the pod to the node anyway. * single-numa-node: the topology manager determines if the single NUMA node affinity is possible. If it is, Topology Manager will store this and the Hint Providers can then use this information when making the resource allocation decision. If, however, this is not possible then the Topology Manager will reject the pod from the node. This will result in a pod in a Terminated state with a pod admission failure. The default policy value is 'none' if unspecified. Details about each strategy can be found [here](https://kubernetes.io/docs/tasks/administer-cluster/topology-manager/#topology-manager-policies).",
+"type": "string"
+},
+"scope": {
+"description": "The Topology Manager aligns resources in following scopes: * container * pod The default scope is 'container' if unspecified. See https://kubernetes.io/docs/tasks/administer-cluster/topology-manager/#topology-manager-scopes",
+"type": "string"
+}
+},
+"type": "object"
+},
 "UpdateClusterRequest": {
 "description": "UpdateClusterRequest updates the settings of a cluster.",
 "id": "UpdateClusterRequest",

docs/dyn/container_v1.projects.locations.clusters.nodePools.html

@@ -2685,7 +2685,7 @@
 }
 }
 },
-"revision": "20250408",
+"revision": "20250429",
 "rootUrl": "https://container.googleapis.com/",
 "schemas": {
 "AcceleratorConfig": {
@@ -5861,6 +5861,17 @@ false
 },
 "type": "object"
 },
+"MemoryManager": {
+"description": "The option enables the Kubernetes NUMA-aware Memory Manager feature. Detailed description about the feature can be found [here](https://kubernetes.io/docs/tasks/administer-cluster/memory-manager/).",
+"id": "MemoryManager",
+"properties": {
+"policy": {
+"description": "Controls the memory management policy on the Node. See https://kubernetes.io/docs/tasks/administer-cluster/memory-manager/#policies The following values are allowed. * \"none\" * \"static\" The default value is 'none' if unspecified.",
+"type": "string"
+}
+},
+"type": "object"
+},
 "MeshCertificates": {
 "description": "Configuration for issuance of mTLS keys and certificates to Kubernetes pods.",
 "id": "MeshCertificates",
@@ -6527,10 +6538,18 @@ false
 "description": "Enable or disable Kubelet read only port.",
 "type": "boolean"
 },
+"memoryManager": {
+"$ref": "MemoryManager",
+"description": "Optional. Controls NUMA-aware Memory Manager configuration on the node. For more information, see: https://kubernetes.io/docs/tasks/administer-cluster/memory-manager/"
+},
 "podPidsLimit": {
 "description": "Set the Pod PID limits. See https://kubernetes.io/docs/concepts/policy/pid-limiting/#pod-pid-limits Controls the maximum number of processes allowed to run in a pod. The value must be greater than or equal to 1024 and less than 4194304.",
 "format": "int64",
 "type": "string"
+},
+"topologyManager": {
+"$ref": "TopologyManager",
+"description": "Optional. Controls Topology Manager configuration on the node. For more information, see: https://kubernetes.io/docs/tasks/administer-cluster/topology-manager/"
 }
 },
 "type": "object"
@@ -8638,6 +8657,21 @@ false
 },
 "type": "object"
 },
+"TopologyManager": {
+"description": "TopologyManager defines the configuration options for Topology Manager feature. See https://kubernetes.io/docs/tasks/administer-cluster/topology-manager/",
+"id": "TopologyManager",
+"properties": {
+"policy": {
+"description": "Configures the strategy for resource alignment. Allowed values are: * none: the default policy, and does not perform any topology alignment. * restricted: the topology manager stores the preferred NUMA node affinity for the container, and will reject the pod if the affinity if not preferred. * best-effort: the topology manager stores the preferred NUMA node affinity for the container. If the affinity is not preferred, the topology manager will admit the pod to the node anyway. * single-numa-node: the topology manager determines if the single NUMA node affinity is possible. If it is, Topology Manager will store this and the Hint Providers can then use this information when making the resource allocation decision. If, however, this is not possible then the Topology Manager will reject the pod from the node. This will result in a pod in a Terminated state with a pod admission failure. The default policy value is 'none' if unspecified. Details about each strategy can be found [here](https://kubernetes.io/docs/tasks/administer-cluster/topology-manager/#topology-manager-policies).",
+"type": "string"
+},
+"scope": {
+"description": "The Topology Manager aligns resources in following scopes: * container * pod The default scope is 'container' if unspecified. See https://kubernetes.io/docs/tasks/administer-cluster/topology-manager/#topology-manager-scopes",
+"type": "string"
+}
+},
+"type": "object"
+},
 "TpuConfig": {
 "deprecated": true,
 "description": "Configuration for Cloud TPU. This message is deprecated due to the deprecation of 2VM TPU. The end of life date for 2VM TPU is 2025-04-25.",