NamespacesResourceQuotaOptionsV1Update

The ResourceQuotaOptionsV1Update structure represents the changes to resource quota limits which are set on the namespace. Refer to <\a> Kubernetes Resource Quota for information related to the properties of this object and what they map to.


Properties

integer
config_map_count Optional

This represents the new value for ‘configMapCount’ option which is the maximum number of ConfigMaps in the namespace. This field is ignored if ResourceQuotaOptionsV1Update.config-map-count-unset is set to true. If unset, the existing ‘configMapCount’ limit will be unchanged if ResourceQuotaOptionsV1Update.config-map-count-unset is unset or set to false.


boolean
config_map_count_unset Optional

This represents the intent of the change to ResourceQuotaOptionsV1Update.config-map-count. If this field is set to true, the existing ‘configMapCount’ limit on the namespace will be reset. If this field is set to false, the existing configmap count limit will be changed to the value specified in ResourceQuotaOptionsV1Update.config-map-count, if any. If unset, the existing ‘configMapCount’ limit will be changed to the value specified in ResourceQuotaOptionsV1Update.config-map-count, if any.


integer
cpu_limit Optional

This represents the new value for ‘limits.cpu’ option which is equivalent to the maximum CPU limit (in MHz) across all pods in the namespace. This field is ignored if ResourceQuotaOptionsV1Update.cpu-limit-unset is set to true. If specified, this limit should be at least 10 MHz. If unset, the existing CPU limit on the ResourcePool will be unchanged if ResourceQuotaOptionsV1Update.cpu-limit-unset is unset or set to false.


integer
cpu_limit_default Optional

This represents the new value for the default CPU limit (in Mhz) for containers in the pod. This field is ignored if ResourceQuotaOptionsV1Update.cpu-limit-default-unset is set to true. If specified, this limit should be at least 10 MHz. If unset, the existing default CPU limit will be unchanged if ResourceQuotaOptionsV1Update.cpu-limit-default-unset is unset or set to false.


boolean
cpu_limit_default_unset Optional

This represents the intent of the change to ResourceQuotaOptionsV1Update.cpu-limit-default. If this field is set to true, the existing default CPU limit on containers in the pod is removed. If this field is set to false, the existing default CPU limit will be changed to the value specified in ResourceQuotaOptionsV1Update.cpu-limit-default, if any. If unset, the existing default CPU limit will be changed to the value specified in ResourceQuotaOptionsV1Update.cpu-limit-default, if any.


boolean
cpu_limit_unset Optional

This represents the intent of the change to ResourceQuotaOptionsV1Update.cpu-limit. If this field is set to true, the existing CPU limit on the ResourcePool is removed. If this field is set to false, the existing CPU limit will be changed to the value specified in ResourceQuotaOptionsV1Update.cpu-limit, if any. If unset, the existing CPU limit will be changed to the value specified in ResourceQuotaOptionsV1Update.memory-limit, if any.


integer
cpu_request_default Optional

This represents the new value for the default CPU request (in Mhz) for containers in the pod. This field is ignored if ResourceQuotaOptionsV1Update.cpu-request-default-unset is set to true. If specified, this field should be at least 10 MHz. If unset, the existing default CPU request will be unchanged if ResourceQuotaOptionsV1Update.cpu-request-default-unset is unset or set to false.


boolean
cpu_request_default_unset Optional

This represents the intent of the change to ResourceQuotaOptionsV1Update.cpu-request-default. If this field is set to true, the existing default CPU request on containers in the pod is removed. If this field is set to false, the existing default CPU request will be changed to the value specified in ResourceQuotaOptionsV1Update.cpu-request-default, if any. If unset, the existing default CPU request will be changed to the value specified in ResourceQuotaOptionsV1Update.cpu-request-default, if any.


integer
daemon_set_count Optional

This represents the new value for ‘daemonSetCount’ option which is the maximum number of DaemonSets in the namespace. This field is ignored if ResourceQuotaOptionsV1Update.daemon-set-count-unset is set to true. If unset, the existing ‘daemonSetCount’ limit will be unchanged if ResourceQuotaOptionsV1Update.daemon-set-count-unset is unset or set to false.


boolean
daemon_set_count_unset Optional

This represents the intent of the change to ResourceQuotaOptionsV1Update.daemon-set-count. If this field is set to true, the existing ‘daemonSetCount’ limit on the namespace will be reset. If this field is set to false, the existing daemonset count limit will be changed to the value specified in ResourceQuotaOptionsV1Update.daemon-set-count, if any. If unset, the existing ‘daemonSetCount’ limit will be changed to the value specified in ResourceQuotaOptionsV1Update.daemon-set-count, if any.


integer
deployment_count Optional

This represents the new value for ‘deploymentCount’ option which is the maximum number of deployments in the namespace. This field is ignored if ResourceQuotaOptionsV1Update.deployment-count-unset is set to true. If unset, the existing ‘deploymentCount’ limit will be unchanged if ResourceQuotaOptionsV1Update.deployment-count-unset is unset or set to false.


boolean
deployment_count_unset Optional

This represents the intent of the change to ResourceQuotaOptionsV1Update.deployment-count. If this field is set to true, the existing ‘deploymentCount’ limit on the namespace will be reset. If this field is set to false, the existing deployment count limit will be changed to the value specified in ResourceQuotaOptionsV1Update.deployment-count, if any. If unset, the existing ‘deploymentCount’ limit will be changed to the value specified in ResourceQuotaOptionsV1Update.deployment-count, if any.


integer
job_count Optional

This represents the new value for ‘jobCount’ option which is the maximum number of jobs in the namespace. This field is ignored if ResourceQuotaOptionsV1Update.job-count-unset is set to true. If unset, the existing ‘jobCount’ limit will be unchanged if ResourceQuotaOptionsV1Update.job-count-unset is unset or set to false.


boolean
job_count_unset Optional

This represents the intent of the change to ResourceQuotaOptionsV1Update.job-count. If this field is set to true, the existing ‘jobCount’ limit on the namespace will be reset. If this field is set to false, the existing secret count limit will be changed to the value specified in ResourceQuotaOptionsV1Update.job-count, if any. If unset, the existing ‘jobCount’ limit will be changed to the value specified in ResourceQuotaOptionsV1Update.job-count, if any.


integer
memory_limit Optional

This represents the new value for ‘limits.memory’ option which is equivalent to the maximum memory limit (in mebibytes) across all pods in the namespace. This field is ignored if ResourceQuotaOptionsV1Update.memory-limit-unset is set to true. If unset, the existing memory limit on the ResourcePool will be unchanged if ResourceQuotaOptionsV1Update.memory-limit-unset is unset or set to false.


integer
memory_limit_default Optional

This represents the new value for the default memory limit (in mebibytes) for containers in the pod. This field is ignored if ResourceQuotaOptionsV1Update.memory-limit-default-unset is set to true. If unset, the existing memory limit will be unchanged if ResourceQuotaOptionsV1Update.memory-limit-default-unset is unset or set to false.


boolean
memory_limit_default_unset Optional

This represents the intent of the change to ResourceQuotaOptionsV1Update.memory-limit-default. If this field is set to true, the existing default memory limit on containers in the pod is removed. If this field is set to false, the existing default memory limit will be changed to the value specified in ResourceQuotaOptionsV1Update.memory-limit-default, if any. If unset, the existing default memory limit will be changed to the value specified in ResourceQuotaOptionsV1Update.memory-limit-default, if any.


boolean
memory_limit_unset Optional

This represents the intent of the change to ResourceQuotaOptionsV1Update.memory-limit. If this field is set to true, the existing memory limit on the ResourcePool is removed. If this field is set to false, the existing memory limit will be changed to the value specified in ResourceQuotaOptionsV1Update.memory-limit, if any. If unset, the existing memory limit will be changed to the value specified in ResourceQuotaOptionsV1Update.memory-limit, if any.


integer
memory_request_default Optional

This represents the new value for the default memory request (in mebibytes) for containers in the pod. This field is ignored if ResourceQuotaOptionsV1Update.memory-request-default-unset is set to true. If unset, the existing memory request will be unchanged if ResourceQuotaOptionsV1Update.memory-request-default-unset is unset or set to false.


boolean
memory_request_default_unset Optional

This represents the intent of the change to ResourceQuotaOptionsV1Update.memory-request-default. If this field is set to true, the existing default memory request on containers in the pod will be removed. If this field is set to false, the existing default memory request will be changed to the value specified in ResourceQuotaOptionsV1Update.memory-request-default, if any. If unset, the existing default memory request will be changed to the value specified in ResourceQuotaOptionsV1Update.memory-request-default, if any.


integer
persistent_volume_claim_count Optional

This represents the new value for ‘persistentVolumeClaimCount’ option which is the maximum number of PersistentVolumeClaims in the namespace. This field is ignored if ResourceQuotaOptionsV1Update.persistent-volume-claim-count-unset is set to true. If unset, the existing ‘persistentVolumeClaimCount’ limit will be unchanged if ResourceQuotaOptionsV1Update.persistent-volume-claim-count-unset is unset or set to false.


boolean
persistent_volume_claim_count_unset Optional

This represents the intent of the change to ResourceQuotaOptionsV1Update.persistent-volume-claim-count. If this field is set to true, the existing ‘persistentVolumeClaimCount’ limit on the namespace will be reset. If this field is set to false, the existing replicationcontroller count limit will be changed to the value specified in ResourceQuotaOptionsV1Update.persistent-volume-claim-count, if any. If unset, the existing ‘persistentVolumeClaimCount’ limit will be changed to the value specified in ResourceQuotaOptionsV1Update.persistent-volume-claim-count, if any.


integer
pod_count Optional

This represents the new value for ‘podCount’ option which is the maximum number of pods in the namespace. This field is ignored if ResourceQuotaOptionsV1Update.pod-count-unset is set to true. If unset, the existing ‘podCount’ limit will be unchanged if ResourceQuotaOptionsV1Update.pod-count-unset is unset or set to false.


boolean
pod_count_unset Optional

This represents the intent of the change to ResourceQuotaOptionsV1Update.pod-count. If this field is set to true, the existing ‘podCount’ limit on the namespace will be reset. If this field is set to false, the existing CPU limit will be changed to the value specified in ResourceQuotaOptionsV1Update.pod-count, if any. If unset, the existing ‘podCount’ limit will be changed to the value specified in ResourceQuotaOptionsV1Update.pod-count, if any.


integer
replica_set_count Optional

This represents the new value for ‘replicaSetCount’ option which is the maximum number of ReplicaSets in the namespace. This field is ignored if ResourceQuotaOptionsV1Update.replica-set-count-unset is set to true. If unset, the existing ‘replicaSetCount’ limit will be unchanged if ResourceQuotaOptionsV1Update.replica-set-count-unset is unset or set to false.


boolean
replica_set_count_unset Optional

This represents the intent of the change to ResourceQuotaOptionsV1Update.replica-set-count. If this field is set to true, the existing ‘replicaSetCount’ limit on the namespace will be reset. If this field is set to false, the existing replicaset count limit will be changed to the value specified in ResourceQuotaOptionsV1Update.replica-set-count, if any. If unset, the existing ‘replicaSetCount’ limit will be changed to the value specified in ResourceQuotaOptionsV1Update.replica-set-count, if any.


integer
replication_controller_count Optional

This represents the new value for ‘replicationControllerCount’ option which is the maximum number of ReplicationControllers in the namespace. This field is ignored if ResourceQuotaOptionsV1Update.replication-controller-count-unset is set to true. If unset, the existing ‘replicationControllerCount’ limit will be unchanged if ResourceQuotaOptionsV1Update.replication-controller-count-unset is unset or set to false.


boolean
replication_controller_count_unset Optional

This represents the intent of the change to ResourceQuotaOptionsV1Update.replication-controller-count. If this field is set to true, the existing ‘replicationControllerCount’ limit on the namespace will be reset. If this field is set to false, the existing replicationcontroller count limit will be changed to the value specified in ResourceQuotaOptionsV1Update.replication-controller-count, if any. If unset, the existing ‘replicationControllerCount’ limit will be changed to the value specified in ResourceQuotaOptionsV1Update.replication-controller-count, if any.


integer
secret_count Optional

This represents the new value for ‘secretCount’ option which is the maximum number of secrets in the namespace. This field is ignored if ResourceQuotaOptionsV1Update.secret-count-unset is set to true. If unset, the existing ‘secretCount’ limit will be unchanged if ResourceQuotaOptionsV1Update.secret-count-unset is unset or set to false.


boolean
secret_count_unset Optional

This represents the intent of the change to ResourceQuotaOptionsV1Update.secret-count. If this field is set to true, the existing ‘secretCount’ limit on the namespace will be reset. If this field is set to false, the existing secret count limit will be changed to the value specified in ResourceQuotaOptionsV1Update.secret-count, if any. If unset, the existing ‘secretCount’ limit will be changed to the value specified in ResourceQuotaOptionsV1Update.secret-count, if any.


integer
service_count Optional

This represents the new value for ‘serviceCount’ option which is the maximum number of services in the namespace. This field is ignored if ResourceQuotaOptionsV1Update.service-count-unset is set to true. If unset, the existing ‘serviceCount’ limit will be unchanged if ResourceQuotaOptionsV1Update.service-count-unset is unset or set to false.


boolean
service_count_unset Optional

This represents the intent of the change to ResourceQuotaOptionsV1Update.service-count. If this field is set to true, the existing ‘serviceCount’ limit on the namespace will be reset. If this field is set to false, the existing service count limit will be changed to the value specified in ResourceQuotaOptionsV1Update.service-count, if any. If unset, the existing ‘serviceCount’ limit will be changed to the value specified in ResourceQuotaOptionsV1Update.service-count, if any.


integer
stateful_set_count Optional

This represents the new value for ‘statefulSetCount’ option which is the maximum number of StatefulSets in the namespace. This field is ignored if ResourceQuotaOptionsV1Update.stateful-set-count-unset is set to true. If unset, the existing ‘statefulSetCount’ limit will be unchanged if ResourceQuotaOptionsV1Update.stateful-set-count-unset is unset or set to false.


boolean
stateful_set_count_unset Optional

This represents the intent of the change to ResourceQuotaOptionsV1Update.stateful-set-count. If this field is set to true, the existing ‘statefulSetCount’ limit on the namespace will be reset. If this field is set to false, the existing statefulset count limit will be changed to the value specified in ResourceQuotaOptionsV1Update.stateful-set-count, if any. If unset, the existing ‘statefulSetCount’ limit will be changed to the value specified in ResourceQuotaOptionsV1Update.stateful-set-count, if any.


integer
storage_request_limit Optional

This represents the new value for ‘requests.storage’ which is the limit on storage requests (in mebibytes) across all persistent volume claims from pods in the namespace. This field is ignored if if ResourceQuotaOptionsV1Update.storage-request-limit-unset is set to true. If unset, the existing storage request limit will be unchanged if ResourceQuotaOptionsV1Update.storage-request-limit-unset is unset or set to false. the namespace.


boolean
storage_request_limit_unset Optional

This represents the intent of the change to ResourceQuotaOptionsV1Update.storage-request-limit. If this field is set to true, the existing storage request limit will be reset. If this field is set to false, the existing storage request limit will be changed to the value specified in ResourceQuotaOptionsV1Update.storage-request-limit, if any. If unset, the existing storage request limit will be changed to the value specified in ResourceQuotaOptionsV1Update.storage-request-limit, if any.

JSON Example

{
    "config_map_count": 0,
    "config_map_count_unset": false,
    "cpu_limit": 0,
    "cpu_limit_default": 0,
    "cpu_limit_default_unset": false,
    "cpu_limit_unset": false,
    "cpu_request_default": 0,
    "cpu_request_default_unset": false,
    "daemon_set_count": 0,
    "daemon_set_count_unset": false,
    "deployment_count": 0,
    "deployment_count_unset": false,
    "job_count": 0,
    "job_count_unset": false,
    "memory_limit": 0,
    "memory_limit_default": 0,
    "memory_limit_default_unset": false,
    "memory_limit_unset": false,
    "memory_request_default": 0,
    "memory_request_default_unset": false,
    "persistent_volume_claim_count": 0,
    "persistent_volume_claim_count_unset": false,
    "pod_count": 0,
    "pod_count_unset": false,
    "replica_set_count": 0,
    "replica_set_count_unset": false,
    "replication_controller_count": 0,
    "replication_controller_count_unset": false,
    "secret_count": 0,
    "secret_count_unset": false,
    "service_count": 0,
    "service_count_unset": false,
    "stateful_set_count": 0,
    "stateful_set_count_unset": false,
    "storage_request_limit": 0,
    "storage_request_limit_unset": false
}
Feedback

Was this page helpful?