AccumulateUniqueHostPorts extracts each HostPort of each Container, accumulating the results and returning an error if any ports conflict.

IsSecretKey tests for a string that conforms to the definition of a subdomain in DNS (RFC 1123), except that a leading dot is allowed.

IsValidPathSegmentName validates the name can be safely encoded as a path segment.

IsValidPathSegmentPrefix validates the name can be used as a prefix for a name which will be encoded as a path segment It does not check for exact matches with disallowed names, since an arbitrary suffix might make the name valid.

NameIsDNS952Label is a ValidateNameFunc for names that must be a DNS 952 label.

NameIsDNSLabel is a ValidateNameFunc for names that must be a DNS 1123 label.

NameIsDNSSubdomain is a ValidateNameFunc for names that must be a DNS subdomain.

ValidateAffinityInPodAnnotations tests that the serialized Affinity in Pod.Annotations has valid data.

ValidateAnnotations validates that a set of annotations are correctly defined.

ValidateConfigMap tests whether required fields in the ConfigMap are set.

ValidateConfigMapName can be used to check whether the given ConfigMap name is valid.

ValidateConfigMapUpdate tests if required fields in the ConfigMap are set.

ValidateEndpoints tests if required fields are set.

ValidateEndpointsName can be used to check whether the given endpoints name is valid.

ValidateEndpointsUpdate tests to make sure an endpoints update can be applied.

ValidateEvent makes sure that the event makes sense.

ValidateHasLabel requires that api.ObjectMeta has a Label with key and expectedValue.

ValidateLabels validates that a set of labels are correctly defined.

ValidateLimitRange tests if required fields in the LimitRange are set.

ValidateLimitRangeName can be used to check whether the given limit range name is valid.

ValidateLoadBalancerStatus validates required fields on a LoadBalancerStatus.

ValidateNamespace tests if required fields are set.

ValidateNamespaceFinalizeUpdate tests to see if the update is legal for an end user to make.

ValidateNamespaceName can be used to check whether the given namespace name is valid.

ValidateNamespaceStatusUpdate tests to see if the update is legal for an end user to make.

ValidateNamespaceUpdate tests to make sure a namespace update can be applied.

ValidateNode tests if required fields in the node are set.

ValidateNodeName can be used to check whether the given node name is valid.

ValidateNodeSelector tests that the specified nodeSelector fields has valid data.

ValidateNodeSelectorRequirement tests that the specified NodeSelectorRequirement fields has valid data.

ValidateNodeSelectorTerm tests that the specified node selector term has valid data.

ValidateNodeUpdate tests to make sure a node update can be applied.

Validates that the given selector is non-empty.

Validates that given value is not negative.

Validates that a Quantity is not negative.

ValidateObjectMeta validates an object's metadata on creation.

ValidateObjectMetaUpdate validates an object's metadata when updated.

ValidatePathSegmentName validates the name can be safely encoded as a path segment.

ValidatePersistentVolumeStatusUpdate tests to see if the status update is legal for an end user to make.

ValidatePersistentVolumeUpdate tests to see if the update is legal for an end user to make.

ValidatePod tests if required fields in the pod are set.

ValidatePodBinding tests if required fields in the pod binding are legal.

ValidatePodName can be used to check whether the given pod name is valid.

ValidatePodSecurityContext test that the specified PodSecurityContext has valid data.

ValidatePodSpec tests that the specified PodSpec has valid data.

ValidatePodStatusUpdate tests to see if the update is legal for an end user to make.

ValidatePodTemplate tests if required fields in the pod template are set.

ValidatePodTemplateSpec validates the spec of a pod template.

Validates the given template and ensures that it is in accordance with the desrired selector and replicas.

ValidatePodTemplateUpdate tests to see if the update is legal for an end user to make.

ValidatePodUpdate tests to see if the update is legal for an end user to make.

ValidatePreferredSchedulingTerms tests that the specified SoftNodeAffinity fields has valid data.

ValidateReplicationController tests if required fields in the replication controller are set.

ValidateReplicationControllerName can be used to check whether the given replication controller name is valid.

ValidateReplicationControllerSpec tests if required fields in the replication controller spec are set.

ValidateReplicationControllerStatusUpdate tests if required fields in the replication controller are set.

ValidateReplicationControllerUpdate tests if required fields in the replication controller are set.

ValidateResourceQuota tests if required fields in the ResourceQuota are set.

ValidateResourceQuotaName can be used to check whether the given resource quota name is valid.

ValidateResourceQuotaStatusUpdate tests to see if the status update is legal for an end user to make.

ValidateResourceQuotaUpdate tests to see if the update is legal for an end user to make.

Validates resource requirement spec.

ValidateSecret tests if required fields in the Secret are set.

ValidateSecretName can be used to check whether the given secret name is valid.

ValidateSecretUpdate tests if required fields in the Secret are set.

ValidateSecurityContext ensure the security context contains valid settings.

ValidateService tests if required fields in the service are set.

ValidateServiceAccount tests if required fields in the ServiceAccount are set.

ValidateServiceAccountName can be used to check whether the given service account name is valid.

ValidateServiceAccountUpdate tests if required fields in the ServiceAccount are set.

ValidateServiceName can be used to check whether the given service name is valid.

ValidateServiceStatusUpdate tests if required fields in the Service are set when updating status.

ValidateServiceUpdate tests if required fields in the service are set during an update.

NameMayNotBe specifies strings that cannot be used as names specified as path segments (like the REST API or etcd store).

NameMayNotContain specifies substrings that cannot be used in names specified as path segments (like the REST API or etcd store).

TODO: delete this global variable when we enable the validation of common fields by default.

Schema is an interface that knows how to validate an API object serialized to a byte array.

ValidateNameFunc validates that the provided name is valid for a given resource type.