2014-06-06 23:40:48 +00:00
|
|
|
/*
|
|
|
|
Copyright 2014 Google Inc. All rights reserved.
|
|
|
|
|
|
|
|
Licensed under the Apache License, Version 2.0 (the "License");
|
|
|
|
you may not use this file except in compliance with the License.
|
|
|
|
You may obtain a copy of the License at
|
|
|
|
|
|
|
|
http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
|
|
|
|
Unless required by applicable law or agreed to in writing, software
|
|
|
|
distributed under the License is distributed on an "AS IS" BASIS,
|
|
|
|
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
|
|
See the License for the specific language governing permissions and
|
|
|
|
limitations under the License.
|
|
|
|
*/
|
|
|
|
|
|
|
|
package api
|
|
|
|
|
2014-07-01 02:46:10 +00:00
|
|
|
import (
|
2015-01-03 03:10:03 +00:00
|
|
|
"github.com/GoogleCloudPlatform/kubernetes/pkg/api/resource"
|
2014-12-08 02:19:10 +00:00
|
|
|
"github.com/GoogleCloudPlatform/kubernetes/pkg/runtime"
|
2015-01-14 23:22:21 +00:00
|
|
|
"github.com/GoogleCloudPlatform/kubernetes/pkg/types"
|
2014-07-13 04:46:01 +00:00
|
|
|
"github.com/GoogleCloudPlatform/kubernetes/pkg/util"
|
2014-07-01 02:46:10 +00:00
|
|
|
)
|
|
|
|
|
2014-06-30 22:20:19 +00:00
|
|
|
// Common string formats
|
|
|
|
// ---------------------
|
|
|
|
// Many fields in this API have formatting requirements. The commonly used
|
|
|
|
// formats are defined here.
|
|
|
|
//
|
2014-10-22 15:08:38 +00:00
|
|
|
// C_IDENTIFIER: This is a string that conforms to the definition of an "identifier"
|
2014-06-30 22:20:19 +00:00
|
|
|
// in the C language. This is captured by the following regex:
|
|
|
|
// [A-Za-z_][A-Za-z0-9_]*
|
|
|
|
// This defines the format, but not the length restriction, which should be
|
|
|
|
// specified at the definition of any field of this type.
|
|
|
|
//
|
2014-07-08 20:44:30 +00:00
|
|
|
// DNS_LABEL: This is a string, no more than 63 characters long, that conforms
|
|
|
|
// to the definition of a "label" in RFCs 1035 and 1123. This is captured
|
|
|
|
// by the following regex:
|
2014-06-30 22:20:19 +00:00
|
|
|
// [a-z0-9]([-a-z0-9]*[a-z0-9])?
|
|
|
|
//
|
2014-07-26 00:59:41 +00:00
|
|
|
// DNS_SUBDOMAIN: This is a string, no more than 253 characters long, that conforms
|
2014-07-08 20:44:30 +00:00
|
|
|
// to the definition of a "subdomain" in RFCs 1035 and 1123. This is captured
|
|
|
|
// by the following regex:
|
2014-06-30 22:20:19 +00:00
|
|
|
// [a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*
|
|
|
|
// or more simply:
|
|
|
|
// DNS_LABEL(\.DNS_LABEL)*
|
|
|
|
|
2014-10-22 15:08:38 +00:00
|
|
|
// TypeMeta describes an individual object in an API response or request
|
|
|
|
// with strings representing the type of the object and its API schema version.
|
|
|
|
// Structures that are versioned or persisted should inline TypeMeta.
|
|
|
|
type TypeMeta struct {
|
|
|
|
// Kind is a string value representing the REST resource this object represents.
|
|
|
|
// Servers may infer this from the endpoint the client submits requests to.
|
2014-12-01 05:31:52 +00:00
|
|
|
Kind string `json:"kind,omitempty"`
|
2014-10-22 15:08:38 +00:00
|
|
|
|
|
|
|
// APIVersion defines the versioned schema of this representation of an object.
|
|
|
|
// Servers should convert recognized schemas to the latest internal value, and
|
|
|
|
// may reject unrecognized values.
|
2014-12-01 05:31:52 +00:00
|
|
|
APIVersion string `json:"apiVersion,omitempty"`
|
2014-10-22 15:08:38 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
// ListMeta describes metadata that synthetic resources must have, including lists and
|
|
|
|
// various status objects. A resource may have only one of {ObjectMeta, ListMeta}.
|
|
|
|
type ListMeta struct {
|
|
|
|
// SelfLink is a URL representing this object.
|
2014-12-01 05:31:52 +00:00
|
|
|
SelfLink string `json:"selfLink,omitempty"`
|
2014-10-22 15:08:38 +00:00
|
|
|
|
|
|
|
// An opaque value that represents the version of this response for use with optimistic
|
|
|
|
// concurrency and change monitoring endpoints. Clients must treat these values as opaque
|
|
|
|
// and values may only be valid for a particular resource or set of resources. Only servers
|
|
|
|
// will generate resource versions.
|
2014-12-01 05:31:52 +00:00
|
|
|
ResourceVersion string `json:"resourceVersion,omitempty"`
|
2014-10-22 15:08:38 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
// ObjectMeta is metadata that all persisted resources must have, which includes all objects
|
2015-01-27 23:56:38 +00:00
|
|
|
// users must create.
|
2014-10-22 15:08:38 +00:00
|
|
|
type ObjectMeta struct {
|
|
|
|
// Name is unique within a namespace. Name is required when creating resources, although
|
|
|
|
// some resources may allow a client to request the generation of an appropriate name
|
|
|
|
// automatically. Name is primarily intended for creation idempotence and configuration
|
|
|
|
// definition.
|
2014-12-01 05:31:52 +00:00
|
|
|
Name string `json:"name,omitempty"`
|
2014-10-22 15:08:38 +00:00
|
|
|
|
2015-01-27 23:56:38 +00:00
|
|
|
// GenerateName indicates that the name should be made unique by the server prior to persisting
|
|
|
|
// it. A non-empty value for the field indicates the name will be made unique (and the name
|
|
|
|
// returned to the client will be different than the name passed). The value of this field will
|
|
|
|
// be combined with a unique suffix on the server if the Name field has not been provided.
|
|
|
|
// The provided value must be valid within the rules for Name, and may be truncated by the length
|
|
|
|
// of the suffix required to make the value unique on the server.
|
|
|
|
//
|
|
|
|
// If this field is specified, and Name is not present, the server will NOT return a 409 if the
|
|
|
|
// generated name exists - instead, it will either return 201 Created or 500 with Reason
|
2015-02-12 17:24:34 +00:00
|
|
|
// ServerTimeout indicating a unique name could not be found in the time allotted, and the client
|
2015-01-27 23:56:38 +00:00
|
|
|
// should retry (optionally after the time indicated in the Retry-After header).
|
|
|
|
GenerateName string `json:"generateName,omitempty"`
|
|
|
|
|
2014-10-22 15:08:38 +00:00
|
|
|
// Namespace defines the space within which name must be unique. An empty namespace is
|
|
|
|
// equivalent to the "default" namespace, but "default" is the canonical representation.
|
|
|
|
// Not all objects are required to be scoped to a namespace - the value of this field for
|
|
|
|
// those objects will be empty.
|
2014-12-01 05:31:52 +00:00
|
|
|
Namespace string `json:"namespace,omitempty"`
|
2014-10-22 15:08:38 +00:00
|
|
|
|
|
|
|
// SelfLink is a URL representing this object.
|
2014-12-01 05:31:52 +00:00
|
|
|
SelfLink string `json:"selfLink,omitempty"`
|
2014-10-22 15:08:38 +00:00
|
|
|
|
|
|
|
// UID is the unique in time and space value for this object. It is typically generated by
|
|
|
|
// the server on successful creation of a resource and is not allowed to change on PUT
|
|
|
|
// operations.
|
2015-01-14 23:22:21 +00:00
|
|
|
UID types.UID `json:"uid,omitempty"`
|
2014-10-22 15:08:38 +00:00
|
|
|
|
|
|
|
// An opaque value that represents the version of this resource. May be used for optimistic
|
|
|
|
// concurrency, change detection, and the watch operation on a resource or set of resources.
|
|
|
|
// Clients must treat these values as opaque and values may only be valid for a particular
|
|
|
|
// resource or set of resources. Only servers will generate resource versions.
|
2014-12-01 05:31:52 +00:00
|
|
|
ResourceVersion string `json:"resourceVersion,omitempty"`
|
2014-10-22 15:08:38 +00:00
|
|
|
|
|
|
|
// CreationTimestamp is a timestamp representing the server time when this object was
|
|
|
|
// created. It is not guaranteed to be set in happens-before order across separate operations.
|
|
|
|
// Clients may not set this value. It is represented in RFC3339 form and is in UTC.
|
2014-12-01 05:31:52 +00:00
|
|
|
CreationTimestamp util.Time `json:"creationTimestamp,omitempty"`
|
2014-10-22 15:08:38 +00:00
|
|
|
|
|
|
|
// Labels are key value pairs that may be used to scope and select individual resources.
|
2014-11-20 06:27:11 +00:00
|
|
|
// Label keys are of the form:
|
|
|
|
// label-key ::= prefixed-name | name
|
|
|
|
// prefixed-name ::= prefix '/' name
|
|
|
|
// prefix ::= DNS_SUBDOMAIN
|
|
|
|
// name ::= DNS_LABEL
|
|
|
|
// The prefix is optional. If the prefix is not specified, the key is assumed to be private
|
|
|
|
// to the user. Other system components that wish to use labels must specify a prefix. The
|
|
|
|
// "kubernetes.io/" prefix is reserved for use by kubernetes components.
|
2014-10-22 15:08:38 +00:00
|
|
|
// TODO: replace map[string]string with labels.LabelSet type
|
2014-12-01 05:31:52 +00:00
|
|
|
Labels map[string]string `json:"labels,omitempty"`
|
2014-10-22 15:08:38 +00:00
|
|
|
|
|
|
|
// Annotations are unstructured key value data stored with a resource that may be set by
|
|
|
|
// external tooling. They are not queryable and should be preserved when modifying
|
2014-11-20 06:27:11 +00:00
|
|
|
// objects. Annotation keys have the same formatting restrictions as Label keys. See the
|
|
|
|
// comments on Labels for details.
|
2014-12-01 05:31:52 +00:00
|
|
|
Annotations map[string]string `json:"annotations,omitempty"`
|
2014-10-22 15:08:38 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
const (
|
|
|
|
// NamespaceDefault means the object is in the default namespace which is applied when not specified by clients
|
|
|
|
NamespaceDefault string = "default"
|
|
|
|
// NamespaceAll is the default argument to specify on a context when you want to list or filter resources across all namespaces
|
|
|
|
NamespaceAll string = ""
|
2014-12-12 05:39:56 +00:00
|
|
|
// NamespaceNone is the argument for a context when there is no namespace.
|
|
|
|
NamespaceNone string = ""
|
2014-11-05 19:08:26 +00:00
|
|
|
// TerminationMessagePathDefault means the default path to capture the application termination message running in a container
|
|
|
|
TerminationMessagePathDefault string = "/dev/termination-log"
|
2014-10-22 15:08:38 +00:00
|
|
|
)
|
|
|
|
|
2014-06-16 05:34:16 +00:00
|
|
|
// Volume represents a named volume in a pod that may be accessed by any containers in the pod.
|
2014-06-06 23:40:48 +00:00
|
|
|
type Volume struct {
|
2014-07-08 20:44:30 +00:00
|
|
|
// Required: This must be a DNS_LABEL. Each volume in a pod must have
|
|
|
|
// a unique name.
|
2014-12-01 05:31:52 +00:00
|
|
|
Name string `json:"name"`
|
2014-07-16 19:32:59 +00:00
|
|
|
// Source represents the location and type of a volume to mount.
|
|
|
|
// This is optional for now. If not specified, the Volume is implied to be an EmptyDir.
|
|
|
|
// This implied behavior is deprecated and will be removed in a future version.
|
2015-01-21 01:40:43 +00:00
|
|
|
Source VolumeSource `json:"source,omitempty"`
|
2014-07-16 19:32:59 +00:00
|
|
|
}
|
|
|
|
|
2015-01-21 01:40:43 +00:00
|
|
|
// VolumeSource represents the source location of a volume to mount.
|
2014-11-13 12:01:25 +00:00
|
|
|
// Only one of its members may be specified.
|
2014-07-16 19:32:59 +00:00
|
|
|
type VolumeSource struct {
|
2015-01-20 23:56:44 +00:00
|
|
|
// HostPath represents file or directory on the host machine that is
|
|
|
|
// directly exposed to the container. This is generally used for system
|
|
|
|
// agents or other privileged things that are allowed to see the host
|
|
|
|
// machine. Most containers will NOT need this.
|
2014-10-22 15:08:38 +00:00
|
|
|
// TODO(jonesdl) We need to restrict who can use host directory mounts and who can/can not
|
|
|
|
// mount host directories as read/write.
|
2015-01-20 23:56:44 +00:00
|
|
|
HostPath *HostPath `json:"hostPath"`
|
2014-10-01 20:35:21 +00:00
|
|
|
// EmptyDir represents a temporary directory that shares a pod's lifetime.
|
2014-12-01 05:31:52 +00:00
|
|
|
EmptyDir *EmptyDir `json:"emptyDir"`
|
2014-08-05 17:58:43 +00:00
|
|
|
// GCEPersistentDisk represents a GCE Disk resource that is attached to a
|
|
|
|
// kubelet's host machine and then exposed to the pod.
|
2014-12-01 05:31:52 +00:00
|
|
|
GCEPersistentDisk *GCEPersistentDisk `json:"persistentDisk"`
|
2014-10-21 23:23:05 +00:00
|
|
|
// GitRepo represents a git repository at a particular revision.
|
2014-12-01 05:31:52 +00:00
|
|
|
GitRepo *GitRepo `json:"gitRepo"`
|
2015-02-18 01:24:50 +00:00
|
|
|
// Secret represents a secret that should populate this volume.
|
|
|
|
Secret *SecretSource `json:"secret"`
|
2014-07-15 01:39:30 +00:00
|
|
|
}
|
|
|
|
|
2015-01-20 23:56:44 +00:00
|
|
|
// HostPath represents bare host directory volume.
|
|
|
|
type HostPath struct {
|
2014-12-01 05:31:52 +00:00
|
|
|
Path string `json:"path"`
|
2014-06-06 23:40:48 +00:00
|
|
|
}
|
|
|
|
|
2014-10-01 20:35:21 +00:00
|
|
|
type EmptyDir struct{}
|
2014-07-16 19:32:59 +00:00
|
|
|
|
2014-09-28 03:31:37 +00:00
|
|
|
// Protocol defines network protocols supported for things like conatiner ports.
|
|
|
|
type Protocol string
|
|
|
|
|
|
|
|
const (
|
|
|
|
// ProtocolTCP is the TCP protocol.
|
|
|
|
ProtocolTCP Protocol = "TCP"
|
|
|
|
// ProtocolUDP is the UDP protocol.
|
|
|
|
ProtocolUDP Protocol = "UDP"
|
|
|
|
)
|
|
|
|
|
2014-11-13 12:01:25 +00:00
|
|
|
// GCEPersistentDisk represents a Persistent Disk resource in Google Compute Engine.
|
|
|
|
//
|
2014-08-05 17:58:43 +00:00
|
|
|
// A GCE PD must exist and be formatted before mounting to a container.
|
|
|
|
// The disk must also be in the same GCE project and zone as the kubelet.
|
|
|
|
// A GCE PD can only be mounted as read/write once.
|
|
|
|
type GCEPersistentDisk struct {
|
|
|
|
// Unique name of the PD resource. Used to identify the disk in GCE
|
2014-12-01 05:31:52 +00:00
|
|
|
PDName string `json:"pdName"`
|
2014-08-05 17:58:43 +00:00
|
|
|
// Required: Filesystem type to mount.
|
|
|
|
// Must be a filesystem type supported by the host operating system.
|
|
|
|
// Ex. "ext4", "xfs", "ntfs"
|
|
|
|
// TODO: how do we prevent errors in the filesystem from compromising the machine
|
2014-12-01 05:31:52 +00:00
|
|
|
FSType string `json:"fsType,omitempty"`
|
2014-08-05 17:58:43 +00:00
|
|
|
// Optional: Partition on the disk to mount.
|
|
|
|
// If omitted, kubelet will attempt to mount the device name.
|
|
|
|
// Ex. For /dev/sda1, this field is "1", for /dev/sda, this field is 0 or empty.
|
2014-12-01 05:31:52 +00:00
|
|
|
Partition int `json:"partition,omitempty"`
|
2014-08-05 17:58:43 +00:00
|
|
|
// Optional: Defaults to false (read/write). ReadOnly here will force
|
|
|
|
// the ReadOnly setting in VolumeMounts.
|
2014-12-01 05:31:52 +00:00
|
|
|
ReadOnly bool `json:"readOnly,omitempty"`
|
2014-08-05 17:58:43 +00:00
|
|
|
}
|
|
|
|
|
2014-10-21 23:23:05 +00:00
|
|
|
// GitRepo represents a volume that is pulled from git when the pod is created.
|
|
|
|
type GitRepo struct {
|
2014-10-21 18:47:07 +00:00
|
|
|
// Repository URL
|
2014-12-01 05:31:52 +00:00
|
|
|
Repository string `json:"repository"`
|
2014-10-21 23:23:05 +00:00
|
|
|
// Commit hash, this is optional
|
2014-12-01 05:31:52 +00:00
|
|
|
Revision string `json:"revision"`
|
2014-10-21 23:23:05 +00:00
|
|
|
// TODO: Consider credentials here.
|
2014-10-21 18:47:07 +00:00
|
|
|
}
|
|
|
|
|
2015-02-18 01:26:41 +00:00
|
|
|
// Adapts a Secret into a VolumeSource.
|
|
|
|
//
|
|
|
|
// The contents of the target Secret's Data field will be presented in a volume
|
|
|
|
// as files using the keys in the Data field as the file names.
|
2015-02-18 01:24:50 +00:00
|
|
|
type SecretSource struct {
|
|
|
|
// Reference to a Secret
|
|
|
|
Target ObjectReference `json:"target"`
|
|
|
|
}
|
|
|
|
|
2014-08-05 17:58:43 +00:00
|
|
|
// Port represents a network port in a single container
|
2014-06-06 23:40:48 +00:00
|
|
|
type Port struct {
|
2014-07-08 20:44:30 +00:00
|
|
|
// Optional: If specified, this must be a DNS_LABEL. Each named port
|
|
|
|
// in a pod must have a unique name.
|
2014-12-01 05:31:52 +00:00
|
|
|
Name string `json:"name,omitempty"`
|
2014-08-19 22:18:49 +00:00
|
|
|
// Optional: If specified, this must be a valid port number, 0 < x < 65536.
|
2014-12-01 05:31:52 +00:00
|
|
|
HostPort int `json:"hostPort,omitempty"`
|
2014-06-30 22:20:19 +00:00
|
|
|
// Required: This must be a valid port number, 0 < x < 65536.
|
2014-12-01 05:31:52 +00:00
|
|
|
ContainerPort int `json:"containerPort"`
|
2015-02-18 19:09:49 +00:00
|
|
|
// Required: Supports "TCP" and "UDP".
|
2014-12-01 05:31:52 +00:00
|
|
|
Protocol Protocol `json:"protocol,omitempty"`
|
2014-07-09 05:44:15 +00:00
|
|
|
// Optional: What host IP to bind the external port to.
|
2014-12-01 05:31:52 +00:00
|
|
|
HostIP string `json:"hostIP,omitempty"`
|
2014-06-06 23:40:48 +00:00
|
|
|
}
|
|
|
|
|
2014-09-02 10:00:28 +00:00
|
|
|
// VolumeMount describes a mounting of a Volume within a container.
|
2014-06-06 23:40:48 +00:00
|
|
|
type VolumeMount struct {
|
2014-06-30 22:20:19 +00:00
|
|
|
// Required: This must match the Name of a Volume [above].
|
2014-12-01 05:31:52 +00:00
|
|
|
Name string `json:"name"`
|
2014-06-30 22:20:19 +00:00
|
|
|
// Optional: Defaults to false (read-write).
|
2014-12-01 05:31:52 +00:00
|
|
|
ReadOnly bool `json:"readOnly,omitempty"`
|
2014-06-30 22:20:19 +00:00
|
|
|
// Required.
|
2014-12-10 01:40:00 +00:00
|
|
|
MountPath string `json:"mountPath"`
|
2014-06-06 23:40:48 +00:00
|
|
|
}
|
|
|
|
|
2014-09-02 10:00:28 +00:00
|
|
|
// EnvVar represents an environment variable present in a Container.
|
2014-06-06 23:40:48 +00:00
|
|
|
type EnvVar struct {
|
2014-06-30 22:20:19 +00:00
|
|
|
// Required: This must be a C_IDENTIFIER.
|
2014-12-01 05:31:52 +00:00
|
|
|
Name string `json:"name"`
|
2014-06-30 22:20:19 +00:00
|
|
|
// Optional: defaults to "".
|
2014-12-01 05:31:52 +00:00
|
|
|
Value string `json:"value,omitempty"`
|
2014-06-06 23:40:48 +00:00
|
|
|
}
|
|
|
|
|
2014-08-26 21:32:00 +00:00
|
|
|
// HTTPGetAction describes an action based on HTTP Get requests.
|
|
|
|
type HTTPGetAction struct {
|
2014-08-11 06:26:42 +00:00
|
|
|
// Optional: Path to access on the HTTP server.
|
2014-12-01 05:31:52 +00:00
|
|
|
Path string `json:"path,omitempty"`
|
2014-08-11 06:26:42 +00:00
|
|
|
// Required: Name or number of the port to access on the container.
|
2014-12-01 05:31:52 +00:00
|
|
|
Port util.IntOrString `json:"port,omitempty"`
|
2014-08-11 06:26:42 +00:00
|
|
|
// Optional: Host name to connect to, defaults to the pod IP.
|
2014-12-01 05:31:52 +00:00
|
|
|
Host string `json:"host,omitempty"`
|
2014-07-03 05:35:50 +00:00
|
|
|
}
|
|
|
|
|
2014-08-26 21:32:00 +00:00
|
|
|
// TCPSocketAction describes an action based on opening a socket
|
|
|
|
type TCPSocketAction struct {
|
2014-08-11 06:44:42 +00:00
|
|
|
// Required: Port to connect to.
|
2014-12-01 05:31:52 +00:00
|
|
|
Port util.IntOrString `json:"port,omitempty"`
|
2014-08-01 00:35:54 +00:00
|
|
|
}
|
|
|
|
|
2014-08-26 21:32:00 +00:00
|
|
|
// ExecAction describes a "run in container" action.
|
|
|
|
type ExecAction struct {
|
2014-08-13 04:33:56 +00:00
|
|
|
// Command is the command line to execute inside the container, the working directory for the
|
|
|
|
// command is root ('/') in the container's filesystem. The command is simply exec'd, it is
|
|
|
|
// not run inside a shell, so traditional shell instructions ('|', etc) won't work. To use
|
2014-09-02 10:00:28 +00:00
|
|
|
// a shell, you need to explicitly call out to that shell.
|
2014-12-01 05:31:52 +00:00
|
|
|
Command []string `json:"command,omitempty"`
|
2014-08-13 04:33:56 +00:00
|
|
|
}
|
|
|
|
|
2015-01-27 00:35:52 +00:00
|
|
|
// Probe describes a liveness probe to be examined to the container.
|
|
|
|
type Probe struct {
|
|
|
|
// The action taken to determine the health of a container
|
|
|
|
Handler `json:",inline"`
|
2014-07-03 05:35:50 +00:00
|
|
|
// Length of time before health checking is activated. In seconds.
|
2014-12-01 05:31:52 +00:00
|
|
|
InitialDelaySeconds int64 `json:"initialDelaySeconds,omitempty"`
|
2015-01-29 04:35:49 +00:00
|
|
|
// Length of time before health checking times out. In seconds.
|
|
|
|
TimeoutSeconds int64 `json:"timeoutSeconds,omitempty"`
|
2014-07-03 05:35:50 +00:00
|
|
|
}
|
|
|
|
|
2014-09-26 04:53:17 +00:00
|
|
|
// PullPolicy describes a policy for if/when to pull a container image
|
|
|
|
type PullPolicy string
|
|
|
|
|
|
|
|
const (
|
2014-11-13 12:01:25 +00:00
|
|
|
// PullAlways means that kubelet always attempts to pull the latest image. Container will fail If the pull fails.
|
2015-01-21 04:30:42 +00:00
|
|
|
PullAlways PullPolicy = "Always"
|
2014-11-13 12:01:25 +00:00
|
|
|
// PullNever means that kubelet never pulls an image, but only uses a local image. Container will fail if the image isn't present
|
2015-01-21 04:30:42 +00:00
|
|
|
PullNever PullPolicy = "Never"
|
2014-11-13 12:01:25 +00:00
|
|
|
// PullIfNotPresent means that kubelet pulls if the image isn't present on disk. Container will fail if the image isn't present and the pull fails.
|
2015-01-21 04:30:42 +00:00
|
|
|
PullIfNotPresent PullPolicy = "IfNotPresent"
|
2014-09-26 04:53:17 +00:00
|
|
|
)
|
|
|
|
|
2014-12-15 13:08:08 +00:00
|
|
|
// CapabilityType represent POSIX capabilities type
|
|
|
|
type CapabilityType string
|
|
|
|
|
|
|
|
// Capabilities represent POSIX capabilities that can be added or removed to a running container.
|
|
|
|
type Capabilities struct {
|
|
|
|
// Added capabilities
|
|
|
|
Add []CapabilityType `json:"add,omitempty"`
|
|
|
|
// Removed capabilities
|
|
|
|
Drop []CapabilityType `json:"drop,omitempty"`
|
|
|
|
}
|
|
|
|
|
2015-02-09 22:44:32 +00:00
|
|
|
// ResourceRequirements describes the compute resource requirements.
|
|
|
|
type ResourceRequirements struct {
|
2015-01-25 04:19:36 +00:00
|
|
|
// Limits describes the maximum amount of compute resources required.
|
|
|
|
Limits ResourceList `json:"limits,omitempty"`
|
|
|
|
}
|
|
|
|
|
2014-06-06 23:40:48 +00:00
|
|
|
// Container represents a single container that is expected to be run on the host.
|
|
|
|
type Container struct {
|
2014-07-08 20:44:30 +00:00
|
|
|
// Required: This must be a DNS_LABEL. Each container in a pod must
|
|
|
|
// have a unique name.
|
2014-12-01 05:31:52 +00:00
|
|
|
Name string `json:"name"`
|
2014-06-30 22:20:19 +00:00
|
|
|
// Required.
|
2014-12-01 05:31:52 +00:00
|
|
|
Image string `json:"image"`
|
2014-06-30 22:20:19 +00:00
|
|
|
// Optional: Defaults to whatever is defined in the image.
|
2014-12-01 05:31:52 +00:00
|
|
|
Command []string `json:"command,omitempty"`
|
2014-06-30 22:20:19 +00:00
|
|
|
// Optional: Defaults to Docker's default.
|
2014-12-01 05:31:52 +00:00
|
|
|
WorkingDir string `json:"workingDir,omitempty"`
|
|
|
|
Ports []Port `json:"ports,omitempty"`
|
|
|
|
Env []EnvVar `json:"env,omitempty"`
|
2015-01-25 04:19:36 +00:00
|
|
|
// Compute resource requirements.
|
2015-02-03 02:24:25 +00:00
|
|
|
Resources ResourceRequirements `json:"resources,omitempty"`
|
|
|
|
VolumeMounts []VolumeMount `json:"volumeMounts,omitempty"`
|
|
|
|
LivenessProbe *Probe `json:"livenessProbe,omitempty"`
|
|
|
|
ReadinessProbe *Probe `json:"readinessProbe,omitempty"`
|
|
|
|
Lifecycle *Lifecycle `json:"lifecycle,omitempty"`
|
2015-02-18 19:09:49 +00:00
|
|
|
// Required.
|
2014-12-01 05:31:52 +00:00
|
|
|
TerminationMessagePath string `json:"terminationMessagePath,omitempty"`
|
2014-08-12 13:04:00 +00:00
|
|
|
// Optional: Default to false.
|
2014-12-01 05:31:52 +00:00
|
|
|
Privileged bool `json:"privileged,omitempty"`
|
2015-02-18 19:09:49 +00:00
|
|
|
// Required: Policy for pulling images for this container
|
2014-12-01 05:31:52 +00:00
|
|
|
ImagePullPolicy PullPolicy `json:"imagePullPolicy"`
|
2014-12-15 13:08:08 +00:00
|
|
|
// Optional: Capabilities for container.
|
|
|
|
Capabilities Capabilities `json:"capabilities,omitempty"`
|
2014-08-26 21:32:00 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
// Handler defines a specific action that should be taken
|
|
|
|
// TODO: pass structured data to these actions, and document that data here.
|
|
|
|
type Handler struct {
|
|
|
|
// One and only one of the following should be specified.
|
|
|
|
// Exec specifies the action to take.
|
2014-12-01 05:31:52 +00:00
|
|
|
Exec *ExecAction `json:"exec,omitempty"`
|
2014-08-26 21:32:00 +00:00
|
|
|
// HTTPGet specifies the http request to perform.
|
2014-12-01 05:31:52 +00:00
|
|
|
HTTPGet *HTTPGetAction `json:"httpGet,omitempty"`
|
2015-01-27 00:35:52 +00:00
|
|
|
// TCPSocket specifies an action involving a TCP port.
|
|
|
|
// TODO: implement a realistic TCP lifecycle hook
|
|
|
|
TCPSocket *TCPSocketAction `json:"tcpSocket,omitempty"`
|
2014-08-26 21:32:00 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
// Lifecycle describes actions that the management system should take in response to container lifecycle
|
|
|
|
// events. For the PostStart and PreStop lifecycle handlers, management of the container blocks
|
|
|
|
// until the action is complete, unless the container process fails, in which case the handler is aborted.
|
|
|
|
type Lifecycle struct {
|
|
|
|
// PostStart is called immediately after a container is created. If the handler fails, the container
|
|
|
|
// is terminated and restarted.
|
2014-12-01 05:31:52 +00:00
|
|
|
PostStart *Handler `json:"postStart,omitempty"`
|
2014-08-26 21:32:00 +00:00
|
|
|
// PreStop is called immediately before a container is terminated. The reason for termination is
|
|
|
|
// passed to the handler. Regardless of the outcome of the handler, the container is eventually terminated.
|
2014-12-01 05:31:52 +00:00
|
|
|
PreStop *Handler `json:"preStop,omitempty"`
|
2014-06-06 23:40:48 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
// The below types are used by kube_client and api_server.
|
|
|
|
|
2015-02-03 02:24:25 +00:00
|
|
|
type ConditionStatus string
|
2014-06-28 00:43:36 +00:00
|
|
|
|
2015-02-03 02:24:25 +00:00
|
|
|
// These are valid condition statuses. "ConditionFull" means a resource is in the condition;
|
|
|
|
// "ConditionNone" means a resource is not in the condition; "ConditionUnknown" means kubernetes
|
|
|
|
// can't decide if a resource is in the condition or not. In the future, we could add other
|
|
|
|
// intermediate conditions, e.g. ConditionDegraded.
|
2014-06-28 00:43:36 +00:00
|
|
|
const (
|
2015-02-03 02:24:25 +00:00
|
|
|
ConditionFull ConditionStatus = "Full"
|
|
|
|
ConditionNone ConditionStatus = "None"
|
|
|
|
ConditionUnknown ConditionStatus = "Unknown"
|
2014-06-28 00:43:36 +00:00
|
|
|
)
|
|
|
|
|
2014-09-10 23:57:10 +00:00
|
|
|
type ContainerStateWaiting struct {
|
2014-09-11 22:22:53 +00:00
|
|
|
// Reason could be pulling image,
|
2014-12-01 05:31:52 +00:00
|
|
|
Reason string `json:"reason,omitempty"`
|
2014-09-10 23:57:10 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
type ContainerStateRunning struct {
|
2014-12-10 22:00:41 +00:00
|
|
|
StartedAt util.Time `json:"startedAt,omitempty"`
|
2014-09-10 23:57:10 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
type ContainerStateTerminated struct {
|
2014-12-01 05:31:52 +00:00
|
|
|
ExitCode int `json:"exitCode"`
|
|
|
|
Signal int `json:"signal,omitempty"`
|
|
|
|
Reason string `json:"reason,omitempty"`
|
|
|
|
Message string `json:"message,omitempty"`
|
2014-12-10 22:00:41 +00:00
|
|
|
StartedAt util.Time `json:"startedAt,omitempty"`
|
|
|
|
FinishedAt util.Time `json:"finishedAt,omitempty"`
|
2014-09-10 23:57:10 +00:00
|
|
|
}
|
|
|
|
|
2014-11-13 12:01:25 +00:00
|
|
|
// ContainerState holds a possible state of container.
|
|
|
|
// Only one of its members may be specified.
|
|
|
|
// If none of them is specified, the default one is ContainerStateWaiting.
|
2014-09-10 23:57:10 +00:00
|
|
|
type ContainerState struct {
|
2014-12-01 05:31:52 +00:00
|
|
|
Waiting *ContainerStateWaiting `json:"waiting,omitempty"`
|
|
|
|
Running *ContainerStateRunning `json:"running,omitempty"`
|
|
|
|
Termination *ContainerStateTerminated `json:"termination,omitempty"`
|
2014-09-10 23:57:10 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
type ContainerStatus struct {
|
|
|
|
// TODO(dchen1107): Should we rename PodStatus to a more generic name or have a separate states
|
|
|
|
// defined for container?
|
2014-12-01 05:31:52 +00:00
|
|
|
State ContainerState `json:"state,omitempty"`
|
2015-02-03 02:24:25 +00:00
|
|
|
// Ready specifies whether the conatiner has passed its readiness check.
|
|
|
|
Ready bool `json:"ready"`
|
2014-10-28 00:29:55 +00:00
|
|
|
// Note that this is calculated from dead containers. But those containers are subject to
|
|
|
|
// garbage collection. This value will get capped at 5 by GC.
|
2014-12-01 05:31:52 +00:00
|
|
|
RestartCount int `json:"restartCount"`
|
2014-10-03 06:39:02 +00:00
|
|
|
// TODO(dchen1107): Deprecated this soon once we pull entire PodStatus from node,
|
|
|
|
// not just PodInfo. Now we need this to remove docker.Container from API
|
2014-12-01 05:31:52 +00:00
|
|
|
PodIP string `json:"podIP,omitempty"`
|
2014-10-06 18:54:51 +00:00
|
|
|
// TODO(dchen1107): Need to decide how to represent this in v1beta3
|
2014-12-03 08:31:42 +00:00
|
|
|
Image string `json:"image"`
|
2015-02-05 22:24:48 +00:00
|
|
|
ImageID string `json:"imageID" description:"ID of the container's image"`
|
2014-12-03 08:31:42 +00:00
|
|
|
ContainerID string `json:"containerID,omitempty" description:"container's ID in the format 'docker://<container_id>'"`
|
2014-09-10 23:57:10 +00:00
|
|
|
}
|
|
|
|
|
2015-02-03 02:24:25 +00:00
|
|
|
// PodPhase is a label for the condition of a pod at the current time.
|
|
|
|
type PodPhase string
|
|
|
|
|
|
|
|
// These are the valid statuses of pods.
|
|
|
|
const (
|
|
|
|
// PodPending means the pod has been accepted by the system, but one or more of the containers
|
|
|
|
// has not been started. This includes time before being bound to a node, as well as time spent
|
|
|
|
// pulling images onto the host.
|
|
|
|
PodPending PodPhase = "Pending"
|
|
|
|
// PodRunning means the pod has been bound to a node and all of the containers have been started.
|
|
|
|
// At least one container is still running or is in the process of being restarted.
|
|
|
|
PodRunning PodPhase = "Running"
|
|
|
|
// PodSucceeded means that all containers in the pod have voluntarily terminated
|
|
|
|
// with a container exit code of 0, and the system is not going to restart any of these containers.
|
|
|
|
PodSucceeded PodPhase = "Succeeded"
|
|
|
|
// PodFailed means that all containers in the pod have terminated, and at least one container has
|
|
|
|
// terminated in a failure (exited with a non-zero exit code or was stopped by the system).
|
|
|
|
PodFailed PodPhase = "Failed"
|
|
|
|
// PodUnknown means that for some reason the state of the pod could not be obtained, typically due
|
|
|
|
// to an error in communicating with the host of the pod.
|
|
|
|
PodUnknown PodPhase = "Unknown"
|
|
|
|
)
|
|
|
|
|
|
|
|
type PodConditionKind string
|
|
|
|
|
|
|
|
// These are valid conditions of pod.
|
|
|
|
const (
|
|
|
|
// PodReady means the pod is able to service requests and should be added to the
|
|
|
|
// load balancing pools of all matching services.
|
|
|
|
PodReady PodConditionKind = "Ready"
|
|
|
|
)
|
|
|
|
|
|
|
|
// TODO: add LastTransitionTime, Reason, Message to match NodeCondition api.
|
|
|
|
type PodCondition struct {
|
|
|
|
Kind PodConditionKind `json:"kind"`
|
|
|
|
Status ConditionStatus `json:"status"`
|
|
|
|
}
|
|
|
|
|
2014-07-01 22:35:56 +00:00
|
|
|
// PodInfo contains one entry for every container with available info.
|
2014-09-16 20:21:04 +00:00
|
|
|
type PodInfo map[string]ContainerStatus
|
2014-07-01 22:35:56 +00:00
|
|
|
|
2014-12-15 17:29:04 +00:00
|
|
|
// PodContainerInfo is a wrapper for PodInfo that can be encode/decoded
|
2015-01-14 02:11:24 +00:00
|
|
|
// DEPRECATED: Replaced with PodStatusResult
|
2014-12-15 17:29:04 +00:00
|
|
|
type PodContainerInfo struct {
|
|
|
|
TypeMeta `json:",inline"`
|
|
|
|
ObjectMeta `json:"metadata,omitempty"`
|
|
|
|
ContainerInfo PodInfo `json:"containerInfo"`
|
|
|
|
}
|
|
|
|
|
2014-08-26 18:25:17 +00:00
|
|
|
type RestartPolicyAlways struct{}
|
2014-07-22 18:45:12 +00:00
|
|
|
|
2014-08-26 18:25:17 +00:00
|
|
|
// TODO(dchen1107): Define what kinds of failures should restart.
|
|
|
|
// TODO(dchen1107): Decide whether to support policy knobs, and, if so, which ones.
|
|
|
|
type RestartPolicyOnFailure struct{}
|
|
|
|
|
|
|
|
type RestartPolicyNever struct{}
|
2014-07-22 18:45:12 +00:00
|
|
|
|
2014-11-13 12:01:25 +00:00
|
|
|
// RestartPolicy describes how the container should be restarted.
|
|
|
|
// Only one of the following restart policies may be specified.
|
|
|
|
// If none of the following policies is specified, the default one
|
|
|
|
// is RestartPolicyAlways.
|
2014-07-22 18:45:12 +00:00
|
|
|
type RestartPolicy struct {
|
2014-12-01 05:31:52 +00:00
|
|
|
Always *RestartPolicyAlways `json:"always,omitempty"`
|
|
|
|
OnFailure *RestartPolicyOnFailure `json:"onFailure,omitempty"`
|
|
|
|
Never *RestartPolicyNever `json:"never,omitempty"`
|
2014-07-22 18:45:12 +00:00
|
|
|
}
|
|
|
|
|
2014-07-08 07:08:58 +00:00
|
|
|
// PodList is a list of Pods.
|
2014-06-09 04:39:57 +00:00
|
|
|
type PodList struct {
|
2014-12-01 05:31:52 +00:00
|
|
|
TypeMeta `json:",inline"`
|
|
|
|
ListMeta `json:"metadata,omitempty"`
|
2014-10-22 15:08:38 +00:00
|
|
|
|
2014-12-01 05:31:52 +00:00
|
|
|
Items []Pod `json:"items"`
|
2014-06-06 23:40:48 +00:00
|
|
|
}
|
|
|
|
|
2014-11-12 05:21:40 +00:00
|
|
|
// DNSPolicy defines how a pod's DNS will be configured.
|
|
|
|
type DNSPolicy string
|
|
|
|
|
|
|
|
const (
|
|
|
|
// DNSClusterFirst indicates that the pod should use cluster DNS
|
|
|
|
// first, if it is available, then fall back on the default (as
|
|
|
|
// determined by kubelet) DNS settings.
|
|
|
|
DNSClusterFirst DNSPolicy = "ClusterFirst"
|
|
|
|
|
|
|
|
// DNSDefault indicates that the pod should use the default (as
|
|
|
|
// determined by kubelet) DNS settings.
|
|
|
|
DNSDefault DNSPolicy = "Default"
|
|
|
|
)
|
|
|
|
|
2014-11-07 02:06:58 +00:00
|
|
|
// PodSpec is a description of a pod
|
|
|
|
type PodSpec struct {
|
2014-12-01 05:31:52 +00:00
|
|
|
Volumes []Volume `json:"volumes"`
|
|
|
|
Containers []Container `json:"containers"`
|
|
|
|
RestartPolicy RestartPolicy `json:"restartPolicy,omitempty"`
|
2015-02-18 19:09:49 +00:00
|
|
|
// Required: Set DNS policy.
|
2014-11-12 05:21:40 +00:00
|
|
|
DNSPolicy DNSPolicy `json:"dnsPolicy,omitempty"`
|
2014-11-07 02:06:58 +00:00
|
|
|
// NodeSelector is a selector which must be true for the pod to fit on a node
|
2014-12-01 05:31:52 +00:00
|
|
|
NodeSelector map[string]string `json:"nodeSelector,omitempty"`
|
2014-12-18 22:12:58 +00:00
|
|
|
|
|
|
|
// Host is a request to schedule this pod onto a specific host. If it is non-empty,
|
|
|
|
// the the scheduler simply schedules this pod onto that host, assuming that it fits
|
|
|
|
// resource requirements.
|
|
|
|
Host string `json:"host,omitempty"`
|
2014-11-07 02:06:58 +00:00
|
|
|
}
|
|
|
|
|
2014-11-13 15:52:13 +00:00
|
|
|
// PodStatus represents information about the status of a pod. Status may trail the actual
|
|
|
|
// state of a system.
|
|
|
|
type PodStatus struct {
|
2015-02-03 02:24:25 +00:00
|
|
|
Phase PodPhase `json:"phase,omitempty"`
|
|
|
|
Conditions []PodCondition `json:"Condition,omitempty"`
|
2014-12-12 21:25:04 +00:00
|
|
|
// A human readable message indicating details about why the pod is in this state.
|
|
|
|
Message string `json:"message,omitempty"`
|
|
|
|
|
2014-11-13 15:52:13 +00:00
|
|
|
// Host is the name of the node that this Pod is currently bound to, or empty if no
|
|
|
|
// assignment has been done.
|
2014-12-01 05:31:52 +00:00
|
|
|
Host string `json:"host,omitempty"`
|
|
|
|
HostIP string `json:"hostIP,omitempty"`
|
|
|
|
PodIP string `json:"podIP,omitempty"`
|
2014-11-13 15:52:13 +00:00
|
|
|
|
|
|
|
// The key of this map is the *name* of the container within the manifest; it has one
|
|
|
|
// entry per container in the manifest. The value of this map is currently the output
|
|
|
|
// of `docker inspect`. This output format is *not* final and should not be relied
|
|
|
|
// upon.
|
|
|
|
// TODO: Make real decisions about what our info should look like. Re-enable fuzz test
|
|
|
|
// when we have done this.
|
2014-12-01 05:31:52 +00:00
|
|
|
Info PodInfo `json:"info,omitempty"`
|
2014-11-13 15:52:13 +00:00
|
|
|
}
|
|
|
|
|
2015-01-14 02:11:24 +00:00
|
|
|
// PodStatusResult is a wrapper for PodStatus returned by kubelet that can be encode/decoded
|
|
|
|
type PodStatusResult struct {
|
|
|
|
TypeMeta `json:",inline"`
|
|
|
|
ObjectMeta `json:"metadata,omitempty"`
|
|
|
|
// Status represents the current information about a pod. This data may not be up
|
|
|
|
// to date.
|
|
|
|
Status PodStatus `json:"status,omitempty"`
|
|
|
|
}
|
|
|
|
|
2014-09-02 10:00:28 +00:00
|
|
|
// Pod is a collection of containers, used as either input (create, update) or as output (list, get).
|
2014-06-09 04:17:53 +00:00
|
|
|
type Pod struct {
|
2014-12-01 05:31:52 +00:00
|
|
|
TypeMeta `json:",inline"`
|
|
|
|
ObjectMeta `json:"metadata,omitempty"`
|
2014-10-22 15:08:38 +00:00
|
|
|
|
2014-11-13 15:52:13 +00:00
|
|
|
// Spec defines the behavior of a pod.
|
2014-12-01 05:31:52 +00:00
|
|
|
Spec PodSpec `json:"spec,omitempty"`
|
2014-11-13 15:52:13 +00:00
|
|
|
|
|
|
|
// Status represents the current information about a pod. This data may not be up
|
|
|
|
// to date.
|
2014-12-01 05:31:52 +00:00
|
|
|
Status PodStatus `json:"status,omitempty"`
|
2014-06-06 23:40:48 +00:00
|
|
|
}
|
|
|
|
|
2014-11-07 02:06:58 +00:00
|
|
|
// PodTemplateSpec describes the data a pod should have when created from a template
|
|
|
|
type PodTemplateSpec struct {
|
|
|
|
// Metadata of the pods created from this template.
|
2014-12-01 05:31:52 +00:00
|
|
|
ObjectMeta `json:"metadata,omitempty"`
|
2014-11-07 02:06:58 +00:00
|
|
|
|
|
|
|
// Spec defines the behavior of a pod.
|
2014-12-01 05:31:52 +00:00
|
|
|
Spec PodSpec `json:"spec,omitempty"`
|
2014-06-06 23:40:48 +00:00
|
|
|
}
|
|
|
|
|
2014-11-07 02:06:58 +00:00
|
|
|
// PodTemplate describes a template for creating copies of a predefined pod.
|
|
|
|
type PodTemplate struct {
|
2014-12-01 05:31:52 +00:00
|
|
|
TypeMeta `json:",inline"`
|
|
|
|
ObjectMeta `json:"metadata,omitempty"`
|
2014-11-07 02:06:58 +00:00
|
|
|
|
|
|
|
// Spec defines the pods that will be created from this template
|
2014-12-01 05:31:52 +00:00
|
|
|
Spec PodTemplateSpec `json:"spec,omitempty"`
|
2014-11-07 02:06:58 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
// PodTemplateList is a list of PodTemplates.
|
|
|
|
type PodTemplateList struct {
|
2014-12-01 05:31:52 +00:00
|
|
|
TypeMeta `json:",inline"`
|
|
|
|
ListMeta `json:"metadata,omitempty"`
|
2014-10-22 15:08:38 +00:00
|
|
|
|
2014-12-01 05:31:52 +00:00
|
|
|
Items []PodTemplate `json:"items"`
|
2014-11-07 02:06:58 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
// ReplicationControllerSpec is the specification of a replication controller.
|
|
|
|
// As the internal representation of a replication controller, it may have either
|
|
|
|
// a TemplateRef or a Template set.
|
|
|
|
type ReplicationControllerSpec struct {
|
|
|
|
// Replicas is the number of desired replicas.
|
2014-12-01 05:31:52 +00:00
|
|
|
Replicas int `json:"replicas"`
|
2014-11-07 02:06:58 +00:00
|
|
|
|
|
|
|
// Selector is a label query over pods that should match the Replicas count.
|
2014-12-01 05:31:52 +00:00
|
|
|
Selector map[string]string `json:"selector"`
|
2014-11-07 02:06:58 +00:00
|
|
|
|
|
|
|
// TemplateRef is a reference to an object that describes the pod that will be created if
|
|
|
|
// insufficient replicas are detected. This reference is ignored if a Template is set.
|
|
|
|
// Must be set before converting to a v1beta3 API object
|
2014-12-01 05:31:52 +00:00
|
|
|
TemplateRef *ObjectReference `json:"templateRef,omitempty"`
|
2014-11-07 02:06:58 +00:00
|
|
|
|
|
|
|
// Template is the object that describes the pod that will be created if
|
|
|
|
// insufficient replicas are detected. Internally, this takes precedence over a
|
|
|
|
// TemplateRef.
|
|
|
|
// Must be set before converting to a v1beta1 or v1beta2 API object.
|
2014-12-01 05:31:52 +00:00
|
|
|
Template *PodTemplateSpec `json:"template,omitempty"`
|
2014-11-07 02:06:58 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
// ReplicationControllerStatus represents the current status of a replication
|
|
|
|
// controller.
|
|
|
|
type ReplicationControllerStatus struct {
|
|
|
|
// Replicas is the number of actual replicas.
|
2014-12-01 05:31:52 +00:00
|
|
|
Replicas int `json:"replicas"`
|
2014-06-06 23:40:48 +00:00
|
|
|
}
|
|
|
|
|
2014-09-02 10:00:28 +00:00
|
|
|
// ReplicationController represents the configuration of a replication controller.
|
2014-06-06 23:40:48 +00:00
|
|
|
type ReplicationController struct {
|
2014-12-01 05:31:52 +00:00
|
|
|
TypeMeta `json:",inline"`
|
|
|
|
ObjectMeta `json:"metadata,omitempty"`
|
2014-10-22 15:08:38 +00:00
|
|
|
|
2014-11-07 02:06:58 +00:00
|
|
|
// Spec defines the desired behavior of this replication controller.
|
2014-12-01 05:31:52 +00:00
|
|
|
Spec ReplicationControllerSpec `json:"spec,omitempty"`
|
2014-11-07 02:06:58 +00:00
|
|
|
|
|
|
|
// Status is the current status of this replication controller. This data may be
|
|
|
|
// out of date by some window of time.
|
2014-12-01 05:31:52 +00:00
|
|
|
Status ReplicationControllerStatus `json:"status,omitempty"`
|
2014-06-06 23:40:48 +00:00
|
|
|
}
|
|
|
|
|
2014-11-07 02:06:58 +00:00
|
|
|
// ReplicationControllerList is a collection of replication controllers.
|
|
|
|
type ReplicationControllerList struct {
|
2014-12-01 05:31:52 +00:00
|
|
|
TypeMeta `json:",inline"`
|
|
|
|
ListMeta `json:"metadata,omitempty"`
|
2014-11-07 02:06:58 +00:00
|
|
|
|
2014-12-01 05:31:52 +00:00
|
|
|
Items []ReplicationController `json:"items"`
|
2014-06-06 23:40:48 +00:00
|
|
|
}
|
|
|
|
|
2014-09-02 10:00:28 +00:00
|
|
|
// ServiceList holds a list of services.
|
2014-06-06 23:40:48 +00:00
|
|
|
type ServiceList struct {
|
2014-12-01 05:31:52 +00:00
|
|
|
TypeMeta `json:",inline"`
|
|
|
|
ListMeta `json:"metadata,omitempty"`
|
2014-10-22 15:08:38 +00:00
|
|
|
|
2014-12-01 05:31:52 +00:00
|
|
|
Items []Service `json:"items"`
|
2014-06-06 23:40:48 +00:00
|
|
|
}
|
|
|
|
|
2014-12-17 12:52:11 +00:00
|
|
|
// Session Affinity Type string
|
|
|
|
type AffinityType string
|
|
|
|
|
|
|
|
const (
|
|
|
|
// AffinityTypeClientIP is the Client IP based.
|
|
|
|
AffinityTypeClientIP AffinityType = "ClientIP"
|
|
|
|
|
|
|
|
// AffinityTypeNone - no session affinity.
|
|
|
|
AffinityTypeNone AffinityType = "None"
|
|
|
|
)
|
|
|
|
|
2014-10-30 13:29:11 +00:00
|
|
|
// ServiceStatus represents the current status of a service
|
|
|
|
type ServiceStatus struct{}
|
2014-09-10 16:53:40 +00:00
|
|
|
|
2014-10-30 13:29:11 +00:00
|
|
|
// ServiceSpec describes the attributes that a user creates on a service
|
|
|
|
type ServiceSpec struct {
|
|
|
|
// Port is the TCP or UDP port that will be made available to each pod for connecting to the pods
|
|
|
|
// proxied by this service.
|
2014-12-01 05:31:52 +00:00
|
|
|
Port int `json:"port"`
|
2014-06-18 23:01:49 +00:00
|
|
|
|
2015-02-18 19:09:49 +00:00
|
|
|
// Required: Supports "TCP" and "UDP".
|
2014-12-01 05:31:52 +00:00
|
|
|
Protocol Protocol `json:"protocol,omitempty"`
|
2014-07-13 04:46:01 +00:00
|
|
|
|
2014-11-18 17:49:00 +00:00
|
|
|
// This service will route traffic to pods having labels matching this selector. If empty or not present,
|
|
|
|
// the service is assumed to have endpoints set by an external process and Kubernetes will not modify
|
|
|
|
// those endpoints.
|
|
|
|
Selector map[string]string `json:"selector"`
|
2014-09-18 23:03:34 +00:00
|
|
|
|
2014-10-24 17:28:39 +00:00
|
|
|
// PortalIP is usually assigned by the master. If specified by the user
|
|
|
|
// we will try to respect it or else fail the request. This field can
|
|
|
|
// not be changed by updates.
|
2014-12-01 05:31:52 +00:00
|
|
|
PortalIP string `json:"portalIP,omitempty"`
|
2014-09-18 23:03:34 +00:00
|
|
|
|
2014-10-30 13:29:11 +00:00
|
|
|
// CreateExternalLoadBalancer indicates whether a load balancer should be created for this service.
|
2014-12-01 05:31:52 +00:00
|
|
|
CreateExternalLoadBalancer bool `json:"createExternalLoadBalancer,omitempty"`
|
2014-11-12 04:08:33 +00:00
|
|
|
// PublicIPs are used by external load balancers.
|
2014-12-01 05:31:52 +00:00
|
|
|
PublicIPs []string `json:"publicIPs,omitempty"`
|
2014-10-30 13:29:11 +00:00
|
|
|
|
2015-02-12 01:57:51 +00:00
|
|
|
// ContainerPort is the name or number of the port on the container to direct traffic to.
|
|
|
|
// This is useful if the containers the service points to have multiple open ports.
|
|
|
|
// Optional: If unspecified, the first port on the container will be used.
|
2014-12-01 05:31:52 +00:00
|
|
|
ContainerPort util.IntOrString `json:"containerPort,omitempty"`
|
2014-12-17 12:52:11 +00:00
|
|
|
|
2015-02-18 19:09:49 +00:00
|
|
|
// Required: Supports "ClientIP" and "None". Used to maintain session affinity.
|
2014-12-29 22:39:09 +00:00
|
|
|
SessionAffinity AffinityType `json:"sessionAffinity,omitempty"`
|
2014-10-30 13:29:11 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
// Service is a named abstraction of software service (for example, mysql) consisting of local port
|
|
|
|
// (for example 3306) that the proxy listens on, and the selector that determines which pods
|
|
|
|
// will answer requests sent through the proxy.
|
|
|
|
type Service struct {
|
2014-12-01 05:31:52 +00:00
|
|
|
TypeMeta `json:",inline"`
|
|
|
|
ObjectMeta `json:"metadata,omitempty"`
|
2014-10-30 13:29:11 +00:00
|
|
|
|
|
|
|
// Spec defines the behavior of a service.
|
2014-12-01 05:31:52 +00:00
|
|
|
Spec ServiceSpec `json:"spec,omitempty"`
|
2014-10-30 13:29:11 +00:00
|
|
|
|
|
|
|
// Status represents the current status of a service.
|
2014-12-01 05:31:52 +00:00
|
|
|
Status ServiceStatus `json:"status,omitempty"`
|
2014-06-06 23:40:48 +00:00
|
|
|
}
|
|
|
|
|
2014-07-08 07:08:58 +00:00
|
|
|
// Endpoints is a collection of endpoints that implement the actual service, for example:
|
2014-06-06 23:40:48 +00:00
|
|
|
// Name: "mysql", Endpoints: ["10.10.1.1:1909", "10.10.2.2:8834"]
|
|
|
|
type Endpoints struct {
|
2014-12-01 05:31:52 +00:00
|
|
|
TypeMeta `json:",inline"`
|
|
|
|
ObjectMeta `json:"metadata,omitempty"`
|
2014-10-22 15:08:38 +00:00
|
|
|
|
2014-12-01 05:31:52 +00:00
|
|
|
Endpoints []string `json:"endpoints,omitempty"`
|
2014-06-06 23:40:48 +00:00
|
|
|
}
|
2014-06-20 23:50:56 +00:00
|
|
|
|
2014-08-29 02:31:41 +00:00
|
|
|
// EndpointsList is a list of endpoints.
|
|
|
|
type EndpointsList struct {
|
2014-12-01 05:31:52 +00:00
|
|
|
TypeMeta `json:",inline"`
|
|
|
|
ListMeta `json:"metadata,omitempty"`
|
2014-10-22 15:08:38 +00:00
|
|
|
|
2014-12-01 05:31:52 +00:00
|
|
|
Items []Endpoints `json:"items"`
|
2014-08-29 02:31:41 +00:00
|
|
|
}
|
|
|
|
|
2014-11-19 22:39:10 +00:00
|
|
|
// NodeSpec describes the attributes that a node is created with.
|
|
|
|
type NodeSpec struct {
|
|
|
|
// Capacity represents the available resources of a node
|
2014-12-01 05:31:52 +00:00
|
|
|
Capacity ResourceList `json:"capacity,omitempty"`
|
2014-11-19 22:39:10 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
// NodeStatus is information about the current status of a node.
|
|
|
|
type NodeStatus struct {
|
|
|
|
// Queried from cloud provider, if available.
|
2014-12-01 05:31:52 +00:00
|
|
|
HostIP string `json:"hostIP,omitempty"`
|
2014-11-12 00:44:33 +00:00
|
|
|
// NodePhase is the current lifecycle phase of the node.
|
|
|
|
Phase NodePhase `json:"phase,omitempty"`
|
|
|
|
// Conditions is an array of current node conditions.
|
|
|
|
Conditions []NodeCondition `json:"conditions,omitempty"`
|
|
|
|
}
|
|
|
|
|
|
|
|
type NodePhase string
|
|
|
|
|
|
|
|
// These are the valid phases of node.
|
|
|
|
const (
|
|
|
|
// NodePending means the node has been created/added by the system, but not configured.
|
|
|
|
NodePending NodePhase = "Pending"
|
|
|
|
// NodeRunning means the node has been configured and has Kubernetes components running.
|
|
|
|
NodeRunning NodePhase = "Running"
|
|
|
|
// NodeTerminated means the node has been removed from the cluster.
|
|
|
|
NodeTerminated NodePhase = "Terminated"
|
|
|
|
)
|
|
|
|
|
|
|
|
type NodeConditionKind string
|
|
|
|
|
|
|
|
// These are valid conditions of node. Currently, we don't have enough information to decide
|
|
|
|
// node condition. In the future, we will add more. The proposed set of conditions are:
|
|
|
|
// NodeReachable, NodeLive, NodeReady, NodeSchedulable, NodeRunnable.
|
|
|
|
const (
|
|
|
|
// NodeReachable means the node can be reached (in the sense of HTTP connection) from node controller.
|
|
|
|
NodeReachable NodeConditionKind = "Reachable"
|
|
|
|
// NodeReady means the node returns StatusOK for HTTP health check.
|
|
|
|
NodeReady NodeConditionKind = "Ready"
|
|
|
|
)
|
|
|
|
|
|
|
|
type NodeCondition struct {
|
2015-02-03 02:24:25 +00:00
|
|
|
Kind NodeConditionKind `json:"kind"`
|
|
|
|
Status ConditionStatus `json:"status"`
|
|
|
|
LastProbeTime util.Time `json:"lastProbeTime,omitempty"`
|
|
|
|
LastTransitionTime util.Time `json:"lastTransitionTime,omitempty"`
|
|
|
|
Reason string `json:"reason,omitempty"`
|
|
|
|
Message string `json:"message,omitempty"`
|
2014-11-19 22:39:10 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
// NodeResources is an object for conveying resource information about a node.
|
2014-09-25 20:55:42 +00:00
|
|
|
// see https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/resources.md for more details.
|
2014-11-19 22:39:10 +00:00
|
|
|
// TODO: Use ResourceList instead?
|
2014-09-25 20:55:42 +00:00
|
|
|
type NodeResources struct {
|
2014-11-19 22:39:10 +00:00
|
|
|
// Capacity represents the available resources of a node
|
2014-12-01 05:31:52 +00:00
|
|
|
Capacity ResourceList `json:"capacity,omitempty"`
|
2014-09-25 20:55:42 +00:00
|
|
|
}
|
|
|
|
|
2015-01-03 03:10:03 +00:00
|
|
|
// ResourceName is the name identifying various resources in a ResourceList.
|
2014-09-25 20:55:42 +00:00
|
|
|
type ResourceName string
|
|
|
|
|
2015-01-03 03:10:03 +00:00
|
|
|
const (
|
|
|
|
// CPU, in cores. (500m = .5 cores)
|
|
|
|
ResourceCPU ResourceName = "cpu"
|
|
|
|
// Memory, in bytes. (500Gi = 500GiB = 500 * 1024 * 1024 * 1024)
|
|
|
|
ResourceMemory ResourceName = "memory"
|
|
|
|
)
|
|
|
|
|
|
|
|
// ResourceList is a set of (resource name, quantity) pairs.
|
|
|
|
type ResourceList map[ResourceName]resource.Quantity
|
|
|
|
|
|
|
|
// Get is a convenience function, which returns a 0 quantity if the
|
|
|
|
// resource list is nil, empty, or lacks a value for the requested resource.
|
|
|
|
// Treat as read only!
|
|
|
|
func (rl ResourceList) Get(name ResourceName) *resource.Quantity {
|
|
|
|
if rl == nil {
|
|
|
|
return &resource.Quantity{}
|
|
|
|
}
|
|
|
|
q := rl[name]
|
|
|
|
return &q
|
|
|
|
}
|
2014-09-25 20:55:42 +00:00
|
|
|
|
2014-12-08 03:44:27 +00:00
|
|
|
// Node is a worker node in Kubernetenes
|
|
|
|
// The name of the node according to etcd is in ObjectMeta.Name.
|
|
|
|
type Node struct {
|
2014-12-01 05:31:52 +00:00
|
|
|
TypeMeta `json:",inline"`
|
|
|
|
ObjectMeta `json:"metadata,omitempty"`
|
2014-10-22 15:08:38 +00:00
|
|
|
|
2014-11-19 22:39:10 +00:00
|
|
|
// Spec defines the behavior of a node.
|
2014-12-01 05:31:52 +00:00
|
|
|
Spec NodeSpec `json:"spec,omitempty"`
|
2014-11-19 22:39:10 +00:00
|
|
|
|
|
|
|
// Status describes the current status of a Node
|
2014-12-01 05:31:52 +00:00
|
|
|
Status NodeStatus `json:"status,omitempty"`
|
2014-06-20 21:01:16 +00:00
|
|
|
}
|
|
|
|
|
2014-12-08 03:44:27 +00:00
|
|
|
// NodeList is a list of minions.
|
|
|
|
type NodeList struct {
|
2014-12-01 05:31:52 +00:00
|
|
|
TypeMeta `json:",inline"`
|
|
|
|
ListMeta `json:"metadata,omitempty"`
|
2014-10-22 15:08:38 +00:00
|
|
|
|
2014-12-08 03:44:27 +00:00
|
|
|
Items []Node `json:"items"`
|
2014-06-20 21:01:16 +00:00
|
|
|
}
|
|
|
|
|
2015-01-19 21:50:00 +00:00
|
|
|
// NamespaceSpec describes the attributes on a Namespace
|
|
|
|
type NamespaceSpec struct {
|
|
|
|
}
|
|
|
|
|
|
|
|
// NamespaceStatus is information about the current status of a Namespace.
|
|
|
|
type NamespaceStatus struct {
|
|
|
|
}
|
|
|
|
|
|
|
|
// A namespace provides a scope for Names.
|
|
|
|
// Use of multiple namespaces is optional
|
|
|
|
type Namespace struct {
|
|
|
|
TypeMeta `json:",inline"`
|
|
|
|
ObjectMeta `json:"metadata,omitempty"`
|
|
|
|
|
|
|
|
// Spec defines the behavior of the Namespace.
|
|
|
|
Spec NamespaceSpec `json:"spec,omitempty"`
|
|
|
|
|
|
|
|
// Status describes the current status of a Namespace
|
|
|
|
Status NamespaceStatus `json:"status,omitempty"`
|
|
|
|
}
|
|
|
|
|
|
|
|
// NamespaceList is a list of Namespaces.
|
|
|
|
type NamespaceList struct {
|
|
|
|
TypeMeta `json:",inline"`
|
|
|
|
ListMeta `json:"metadata,omitempty"`
|
|
|
|
|
|
|
|
Items []Namespace `json:"items"`
|
|
|
|
}
|
|
|
|
|
2014-07-23 23:09:37 +00:00
|
|
|
// Binding is written by a scheduler to cause a pod to be bound to a host.
|
|
|
|
type Binding struct {
|
2014-12-01 05:31:52 +00:00
|
|
|
TypeMeta `json:",inline"`
|
|
|
|
ObjectMeta `json:"metadata,omitempty"`
|
2014-10-22 15:08:38 +00:00
|
|
|
|
2014-12-01 05:31:52 +00:00
|
|
|
PodID string `json:"podID"`
|
|
|
|
Host string `json:"host"`
|
2014-07-23 23:09:37 +00:00
|
|
|
}
|
|
|
|
|
2014-06-20 23:50:56 +00:00
|
|
|
// Status is a return value for calls that don't return other objects.
|
Evolve the api.Status object with Reason/Details
Contains breaking API change on api.Status#Details (type change)
Turn Details from string -> StatusDetails - a general
bucket for keyed error behavior. Define an open enumeration
ReasonType exposed as Reason on the status object to provide
machine readable subcategorization beyond HTTP Status Code. Define
a human readable field Message which is common convention (previously
this was joined into Details).
Precedence order: HTTP Status Code, Reason, Details. apiserver would
impose restraints on the ReasonTypes defined by the main apiobject,
and ensure their use is consistent.
There are four long term scenarios this change supports:
1. Allow a client access to a machine readable field that can be
easily switched on for improving or translating the generic
server Message.
2. Return a 404 when a composite operation on multiple resources
fails with enough data so that a client can distinguish which
item does not exist. E.g. resource Parent and resource Child,
POST /parents/1/children to create a new Child, but /parents/1
is deleted. POST returns 404, ReasonTypeNotFound, and
Details.ID = "1", Details.Kind = "parent"
3. Allow a client to receive validation data that is keyed by
attribute for building user facing UIs around field submission.
Validation is usually expressed as map[string][]string, but
that type is less appropriate for many other uses.
4. Allow specific API errors to return more granular failure status
for specific operations. An example might be a minion proxy,
where the operation that failed may be both proxying OR the
minion itself. In this case a reason may be defined "proxy_failed"
corresponding to 502, where the Details field may be extended
to contain a nested error object.
At this time only ID and Kind are exposed
2014-07-31 18:12:26 +00:00
|
|
|
// TODO: this could go in apiserver, but I'm including it here so clients needn't
|
2014-06-20 23:50:56 +00:00
|
|
|
// import both.
|
|
|
|
type Status struct {
|
2014-12-12 21:26:07 +00:00
|
|
|
TypeMeta `json:",inline"`
|
|
|
|
ListMeta `json:"metadata,omitempty"`
|
2014-10-22 15:08:38 +00:00
|
|
|
|
2015-01-29 04:41:37 +00:00
|
|
|
// One of: "Success" or "Failure"
|
2014-12-01 05:31:52 +00:00
|
|
|
Status string `json:"status,omitempty"`
|
2014-08-20 02:58:24 +00:00
|
|
|
// A human-readable description of the status of this operation.
|
2014-12-01 05:31:52 +00:00
|
|
|
Message string `json:"message,omitempty"`
|
2014-08-20 02:58:24 +00:00
|
|
|
// A machine-readable description of why this operation is in the
|
2015-01-29 04:41:37 +00:00
|
|
|
// "Failure" status. If this value is empty there
|
Evolve the api.Status object with Reason/Details
Contains breaking API change on api.Status#Details (type change)
Turn Details from string -> StatusDetails - a general
bucket for keyed error behavior. Define an open enumeration
ReasonType exposed as Reason on the status object to provide
machine readable subcategorization beyond HTTP Status Code. Define
a human readable field Message which is common convention (previously
this was joined into Details).
Precedence order: HTTP Status Code, Reason, Details. apiserver would
impose restraints on the ReasonTypes defined by the main apiobject,
and ensure their use is consistent.
There are four long term scenarios this change supports:
1. Allow a client access to a machine readable field that can be
easily switched on for improving or translating the generic
server Message.
2. Return a 404 when a composite operation on multiple resources
fails with enough data so that a client can distinguish which
item does not exist. E.g. resource Parent and resource Child,
POST /parents/1/children to create a new Child, but /parents/1
is deleted. POST returns 404, ReasonTypeNotFound, and
Details.ID = "1", Details.Kind = "parent"
3. Allow a client to receive validation data that is keyed by
attribute for building user facing UIs around field submission.
Validation is usually expressed as map[string][]string, but
that type is less appropriate for many other uses.
4. Allow specific API errors to return more granular failure status
for specific operations. An example might be a minion proxy,
where the operation that failed may be both proxying OR the
minion itself. In this case a reason may be defined "proxy_failed"
corresponding to 502, where the Details field may be extended
to contain a nested error object.
At this time only ID and Kind are exposed
2014-07-31 18:12:26 +00:00
|
|
|
// is no information available. A Reason clarifies an HTTP status
|
|
|
|
// code but does not override it.
|
2014-12-01 05:31:52 +00:00
|
|
|
Reason StatusReason `json:"reason,omitempty"`
|
Evolve the api.Status object with Reason/Details
Contains breaking API change on api.Status#Details (type change)
Turn Details from string -> StatusDetails - a general
bucket for keyed error behavior. Define an open enumeration
ReasonType exposed as Reason on the status object to provide
machine readable subcategorization beyond HTTP Status Code. Define
a human readable field Message which is common convention (previously
this was joined into Details).
Precedence order: HTTP Status Code, Reason, Details. apiserver would
impose restraints on the ReasonTypes defined by the main apiobject,
and ensure their use is consistent.
There are four long term scenarios this change supports:
1. Allow a client access to a machine readable field that can be
easily switched on for improving or translating the generic
server Message.
2. Return a 404 when a composite operation on multiple resources
fails with enough data so that a client can distinguish which
item does not exist. E.g. resource Parent and resource Child,
POST /parents/1/children to create a new Child, but /parents/1
is deleted. POST returns 404, ReasonTypeNotFound, and
Details.ID = "1", Details.Kind = "parent"
3. Allow a client to receive validation data that is keyed by
attribute for building user facing UIs around field submission.
Validation is usually expressed as map[string][]string, but
that type is less appropriate for many other uses.
4. Allow specific API errors to return more granular failure status
for specific operations. An example might be a minion proxy,
where the operation that failed may be both proxying OR the
minion itself. In this case a reason may be defined "proxy_failed"
corresponding to 502, where the Details field may be extended
to contain a nested error object.
At this time only ID and Kind are exposed
2014-07-31 18:12:26 +00:00
|
|
|
// Extended data associated with the reason. Each reason may define its
|
|
|
|
// own extended details. This field is optional and the data returned
|
|
|
|
// is not guaranteed to conform to any schema except that defined by
|
|
|
|
// the reason type.
|
2014-12-01 05:31:52 +00:00
|
|
|
Details *StatusDetails `json:"details,omitempty"`
|
2014-07-02 20:51:27 +00:00
|
|
|
// Suggested HTTP return code for this status, 0 if not set.
|
2014-12-01 05:31:52 +00:00
|
|
|
Code int `json:"code,omitempty"`
|
2014-06-20 23:50:56 +00:00
|
|
|
}
|
|
|
|
|
Evolve the api.Status object with Reason/Details
Contains breaking API change on api.Status#Details (type change)
Turn Details from string -> StatusDetails - a general
bucket for keyed error behavior. Define an open enumeration
ReasonType exposed as Reason on the status object to provide
machine readable subcategorization beyond HTTP Status Code. Define
a human readable field Message which is common convention (previously
this was joined into Details).
Precedence order: HTTP Status Code, Reason, Details. apiserver would
impose restraints on the ReasonTypes defined by the main apiobject,
and ensure their use is consistent.
There are four long term scenarios this change supports:
1. Allow a client access to a machine readable field that can be
easily switched on for improving or translating the generic
server Message.
2. Return a 404 when a composite operation on multiple resources
fails with enough data so that a client can distinguish which
item does not exist. E.g. resource Parent and resource Child,
POST /parents/1/children to create a new Child, but /parents/1
is deleted. POST returns 404, ReasonTypeNotFound, and
Details.ID = "1", Details.Kind = "parent"
3. Allow a client to receive validation data that is keyed by
attribute for building user facing UIs around field submission.
Validation is usually expressed as map[string][]string, but
that type is less appropriate for many other uses.
4. Allow specific API errors to return more granular failure status
for specific operations. An example might be a minion proxy,
where the operation that failed may be both proxying OR the
minion itself. In this case a reason may be defined "proxy_failed"
corresponding to 502, where the Details field may be extended
to contain a nested error object.
At this time only ID and Kind are exposed
2014-07-31 18:12:26 +00:00
|
|
|
// StatusDetails is a set of additional properties that MAY be set by the
|
|
|
|
// server to provide additional information about a response. The Reason
|
|
|
|
// field of a Status object defines what attributes will be set. Clients
|
|
|
|
// must ignore fields that do not match the defined type of each attribute,
|
|
|
|
// and should assume that any attribute may be empty, invalid, or under
|
|
|
|
// defined.
|
|
|
|
type StatusDetails struct {
|
2014-08-26 17:36:09 +00:00
|
|
|
// The ID attribute of the resource associated with the status StatusReason
|
Evolve the api.Status object with Reason/Details
Contains breaking API change on api.Status#Details (type change)
Turn Details from string -> StatusDetails - a general
bucket for keyed error behavior. Define an open enumeration
ReasonType exposed as Reason on the status object to provide
machine readable subcategorization beyond HTTP Status Code. Define
a human readable field Message which is common convention (previously
this was joined into Details).
Precedence order: HTTP Status Code, Reason, Details. apiserver would
impose restraints on the ReasonTypes defined by the main apiobject,
and ensure their use is consistent.
There are four long term scenarios this change supports:
1. Allow a client access to a machine readable field that can be
easily switched on for improving or translating the generic
server Message.
2. Return a 404 when a composite operation on multiple resources
fails with enough data so that a client can distinguish which
item does not exist. E.g. resource Parent and resource Child,
POST /parents/1/children to create a new Child, but /parents/1
is deleted. POST returns 404, ReasonTypeNotFound, and
Details.ID = "1", Details.Kind = "parent"
3. Allow a client to receive validation data that is keyed by
attribute for building user facing UIs around field submission.
Validation is usually expressed as map[string][]string, but
that type is less appropriate for many other uses.
4. Allow specific API errors to return more granular failure status
for specific operations. An example might be a minion proxy,
where the operation that failed may be both proxying OR the
minion itself. In this case a reason may be defined "proxy_failed"
corresponding to 502, where the Details field may be extended
to contain a nested error object.
At this time only ID and Kind are exposed
2014-07-31 18:12:26 +00:00
|
|
|
// (when there is a single ID which can be described).
|
2014-10-29 02:48:59 +00:00
|
|
|
// TODO: replace with Name with v1beta3
|
2014-12-01 05:31:52 +00:00
|
|
|
ID string `json:"id,omitempty"`
|
2014-08-26 17:36:09 +00:00
|
|
|
// The kind attribute of the resource associated with the status StatusReason.
|
Evolve the api.Status object with Reason/Details
Contains breaking API change on api.Status#Details (type change)
Turn Details from string -> StatusDetails - a general
bucket for keyed error behavior. Define an open enumeration
ReasonType exposed as Reason on the status object to provide
machine readable subcategorization beyond HTTP Status Code. Define
a human readable field Message which is common convention (previously
this was joined into Details).
Precedence order: HTTP Status Code, Reason, Details. apiserver would
impose restraints on the ReasonTypes defined by the main apiobject,
and ensure their use is consistent.
There are four long term scenarios this change supports:
1. Allow a client access to a machine readable field that can be
easily switched on for improving or translating the generic
server Message.
2. Return a 404 when a composite operation on multiple resources
fails with enough data so that a client can distinguish which
item does not exist. E.g. resource Parent and resource Child,
POST /parents/1/children to create a new Child, but /parents/1
is deleted. POST returns 404, ReasonTypeNotFound, and
Details.ID = "1", Details.Kind = "parent"
3. Allow a client to receive validation data that is keyed by
attribute for building user facing UIs around field submission.
Validation is usually expressed as map[string][]string, but
that type is less appropriate for many other uses.
4. Allow specific API errors to return more granular failure status
for specific operations. An example might be a minion proxy,
where the operation that failed may be both proxying OR the
minion itself. In this case a reason may be defined "proxy_failed"
corresponding to 502, where the Details field may be extended
to contain a nested error object.
At this time only ID and Kind are exposed
2014-07-31 18:12:26 +00:00
|
|
|
// On some operations may differ from the requested resource Kind.
|
2014-12-01 05:31:52 +00:00
|
|
|
Kind string `json:"kind,omitempty"`
|
2014-08-26 17:36:09 +00:00
|
|
|
// The Causes array includes more details associated with the StatusReason
|
|
|
|
// failure. Not all StatusReasons may provide detailed causes.
|
2014-12-01 05:31:52 +00:00
|
|
|
Causes []StatusCause `json:"causes,omitempty"`
|
Evolve the api.Status object with Reason/Details
Contains breaking API change on api.Status#Details (type change)
Turn Details from string -> StatusDetails - a general
bucket for keyed error behavior. Define an open enumeration
ReasonType exposed as Reason on the status object to provide
machine readable subcategorization beyond HTTP Status Code. Define
a human readable field Message which is common convention (previously
this was joined into Details).
Precedence order: HTTP Status Code, Reason, Details. apiserver would
impose restraints on the ReasonTypes defined by the main apiobject,
and ensure their use is consistent.
There are four long term scenarios this change supports:
1. Allow a client access to a machine readable field that can be
easily switched on for improving or translating the generic
server Message.
2. Return a 404 when a composite operation on multiple resources
fails with enough data so that a client can distinguish which
item does not exist. E.g. resource Parent and resource Child,
POST /parents/1/children to create a new Child, but /parents/1
is deleted. POST returns 404, ReasonTypeNotFound, and
Details.ID = "1", Details.Kind = "parent"
3. Allow a client to receive validation data that is keyed by
attribute for building user facing UIs around field submission.
Validation is usually expressed as map[string][]string, but
that type is less appropriate for many other uses.
4. Allow specific API errors to return more granular failure status
for specific operations. An example might be a minion proxy,
where the operation that failed may be both proxying OR the
minion itself. In this case a reason may be defined "proxy_failed"
corresponding to 502, where the Details field may be extended
to contain a nested error object.
At this time only ID and Kind are exposed
2014-07-31 18:12:26 +00:00
|
|
|
}
|
|
|
|
|
2014-06-20 23:50:56 +00:00
|
|
|
// Values of Status.Status
|
|
|
|
const (
|
2014-09-28 04:23:51 +00:00
|
|
|
StatusSuccess = "Success"
|
|
|
|
StatusFailure = "Failure"
|
2014-06-20 23:50:56 +00:00
|
|
|
)
|
2014-06-26 17:51:29 +00:00
|
|
|
|
2014-08-26 17:36:09 +00:00
|
|
|
// StatusReason is an enumeration of possible failure causes. Each StatusReason
|
Evolve the api.Status object with Reason/Details
Contains breaking API change on api.Status#Details (type change)
Turn Details from string -> StatusDetails - a general
bucket for keyed error behavior. Define an open enumeration
ReasonType exposed as Reason on the status object to provide
machine readable subcategorization beyond HTTP Status Code. Define
a human readable field Message which is common convention (previously
this was joined into Details).
Precedence order: HTTP Status Code, Reason, Details. apiserver would
impose restraints on the ReasonTypes defined by the main apiobject,
and ensure their use is consistent.
There are four long term scenarios this change supports:
1. Allow a client access to a machine readable field that can be
easily switched on for improving or translating the generic
server Message.
2. Return a 404 when a composite operation on multiple resources
fails with enough data so that a client can distinguish which
item does not exist. E.g. resource Parent and resource Child,
POST /parents/1/children to create a new Child, but /parents/1
is deleted. POST returns 404, ReasonTypeNotFound, and
Details.ID = "1", Details.Kind = "parent"
3. Allow a client to receive validation data that is keyed by
attribute for building user facing UIs around field submission.
Validation is usually expressed as map[string][]string, but
that type is less appropriate for many other uses.
4. Allow specific API errors to return more granular failure status
for specific operations. An example might be a minion proxy,
where the operation that failed may be both proxying OR the
minion itself. In this case a reason may be defined "proxy_failed"
corresponding to 502, where the Details field may be extended
to contain a nested error object.
At this time only ID and Kind are exposed
2014-07-31 18:12:26 +00:00
|
|
|
// must map to a single HTTP status code, but multiple reasons may map
|
|
|
|
// to the same HTTP status code.
|
|
|
|
// TODO: move to apiserver
|
2014-08-26 17:36:09 +00:00
|
|
|
type StatusReason string
|
Evolve the api.Status object with Reason/Details
Contains breaking API change on api.Status#Details (type change)
Turn Details from string -> StatusDetails - a general
bucket for keyed error behavior. Define an open enumeration
ReasonType exposed as Reason on the status object to provide
machine readable subcategorization beyond HTTP Status Code. Define
a human readable field Message which is common convention (previously
this was joined into Details).
Precedence order: HTTP Status Code, Reason, Details. apiserver would
impose restraints on the ReasonTypes defined by the main apiobject,
and ensure their use is consistent.
There are four long term scenarios this change supports:
1. Allow a client access to a machine readable field that can be
easily switched on for improving or translating the generic
server Message.
2. Return a 404 when a composite operation on multiple resources
fails with enough data so that a client can distinguish which
item does not exist. E.g. resource Parent and resource Child,
POST /parents/1/children to create a new Child, but /parents/1
is deleted. POST returns 404, ReasonTypeNotFound, and
Details.ID = "1", Details.Kind = "parent"
3. Allow a client to receive validation data that is keyed by
attribute for building user facing UIs around field submission.
Validation is usually expressed as map[string][]string, but
that type is less appropriate for many other uses.
4. Allow specific API errors to return more granular failure status
for specific operations. An example might be a minion proxy,
where the operation that failed may be both proxying OR the
minion itself. In this case a reason may be defined "proxy_failed"
corresponding to 502, where the Details field may be extended
to contain a nested error object.
At this time only ID and Kind are exposed
2014-07-31 18:12:26 +00:00
|
|
|
|
|
|
|
const (
|
2014-08-26 17:36:09 +00:00
|
|
|
// StatusReasonUnknown means the server has declined to indicate a specific reason.
|
Evolve the api.Status object with Reason/Details
Contains breaking API change on api.Status#Details (type change)
Turn Details from string -> StatusDetails - a general
bucket for keyed error behavior. Define an open enumeration
ReasonType exposed as Reason on the status object to provide
machine readable subcategorization beyond HTTP Status Code. Define
a human readable field Message which is common convention (previously
this was joined into Details).
Precedence order: HTTP Status Code, Reason, Details. apiserver would
impose restraints on the ReasonTypes defined by the main apiobject,
and ensure their use is consistent.
There are four long term scenarios this change supports:
1. Allow a client access to a machine readable field that can be
easily switched on for improving or translating the generic
server Message.
2. Return a 404 when a composite operation on multiple resources
fails with enough data so that a client can distinguish which
item does not exist. E.g. resource Parent and resource Child,
POST /parents/1/children to create a new Child, but /parents/1
is deleted. POST returns 404, ReasonTypeNotFound, and
Details.ID = "1", Details.Kind = "parent"
3. Allow a client to receive validation data that is keyed by
attribute for building user facing UIs around field submission.
Validation is usually expressed as map[string][]string, but
that type is less appropriate for many other uses.
4. Allow specific API errors to return more granular failure status
for specific operations. An example might be a minion proxy,
where the operation that failed may be both proxying OR the
minion itself. In this case a reason may be defined "proxy_failed"
corresponding to 502, where the Details field may be extended
to contain a nested error object.
At this time only ID and Kind are exposed
2014-07-31 18:12:26 +00:00
|
|
|
// The details field may contain other information about this error.
|
|
|
|
// Status code 500.
|
2014-08-26 17:36:09 +00:00
|
|
|
StatusReasonUnknown StatusReason = ""
|
Evolve the api.Status object with Reason/Details
Contains breaking API change on api.Status#Details (type change)
Turn Details from string -> StatusDetails - a general
bucket for keyed error behavior. Define an open enumeration
ReasonType exposed as Reason on the status object to provide
machine readable subcategorization beyond HTTP Status Code. Define
a human readable field Message which is common convention (previously
this was joined into Details).
Precedence order: HTTP Status Code, Reason, Details. apiserver would
impose restraints on the ReasonTypes defined by the main apiobject,
and ensure their use is consistent.
There are four long term scenarios this change supports:
1. Allow a client access to a machine readable field that can be
easily switched on for improving or translating the generic
server Message.
2. Return a 404 when a composite operation on multiple resources
fails with enough data so that a client can distinguish which
item does not exist. E.g. resource Parent and resource Child,
POST /parents/1/children to create a new Child, but /parents/1
is deleted. POST returns 404, ReasonTypeNotFound, and
Details.ID = "1", Details.Kind = "parent"
3. Allow a client to receive validation data that is keyed by
attribute for building user facing UIs around field submission.
Validation is usually expressed as map[string][]string, but
that type is less appropriate for many other uses.
4. Allow specific API errors to return more granular failure status
for specific operations. An example might be a minion proxy,
where the operation that failed may be both proxying OR the
minion itself. In this case a reason may be defined "proxy_failed"
corresponding to 502, where the Details field may be extended
to contain a nested error object.
At this time only ID and Kind are exposed
2014-07-31 18:12:26 +00:00
|
|
|
|
2015-01-07 19:33:21 +00:00
|
|
|
// StatusReasonForbidden means the server can be reached and understood the request, but refuses
|
|
|
|
// to take any further action. It is the result of the server being configured to deny access for some reason
|
|
|
|
// to the requested resource by the client.
|
|
|
|
// Details (optional):
|
|
|
|
// "kind" string - the kind attribute of the forbidden resource
|
|
|
|
// on some operations may differ from the requested
|
|
|
|
// resource.
|
|
|
|
// "id" string - the identifier of the forbidden resource
|
|
|
|
// Status code 403
|
|
|
|
StatusReasonForbidden StatusReason = "Forbidden"
|
|
|
|
|
2014-09-02 10:00:28 +00:00
|
|
|
// StatusReasonNotFound means one or more resources required for this operation
|
Evolve the api.Status object with Reason/Details
Contains breaking API change on api.Status#Details (type change)
Turn Details from string -> StatusDetails - a general
bucket for keyed error behavior. Define an open enumeration
ReasonType exposed as Reason on the status object to provide
machine readable subcategorization beyond HTTP Status Code. Define
a human readable field Message which is common convention (previously
this was joined into Details).
Precedence order: HTTP Status Code, Reason, Details. apiserver would
impose restraints on the ReasonTypes defined by the main apiobject,
and ensure their use is consistent.
There are four long term scenarios this change supports:
1. Allow a client access to a machine readable field that can be
easily switched on for improving or translating the generic
server Message.
2. Return a 404 when a composite operation on multiple resources
fails with enough data so that a client can distinguish which
item does not exist. E.g. resource Parent and resource Child,
POST /parents/1/children to create a new Child, but /parents/1
is deleted. POST returns 404, ReasonTypeNotFound, and
Details.ID = "1", Details.Kind = "parent"
3. Allow a client to receive validation data that is keyed by
attribute for building user facing UIs around field submission.
Validation is usually expressed as map[string][]string, but
that type is less appropriate for many other uses.
4. Allow specific API errors to return more granular failure status
for specific operations. An example might be a minion proxy,
where the operation that failed may be both proxying OR the
minion itself. In this case a reason may be defined "proxy_failed"
corresponding to 502, where the Details field may be extended
to contain a nested error object.
At this time only ID and Kind are exposed
2014-07-31 18:12:26 +00:00
|
|
|
// could not be found.
|
|
|
|
// Details (optional):
|
|
|
|
// "kind" string - the kind attribute of the missing resource
|
|
|
|
// on some operations may differ from the requested
|
|
|
|
// resource.
|
|
|
|
// "id" string - the identifier of the missing resource
|
|
|
|
// Status code 404
|
2014-09-28 04:32:53 +00:00
|
|
|
StatusReasonNotFound StatusReason = "NotFound"
|
Evolve the api.Status object with Reason/Details
Contains breaking API change on api.Status#Details (type change)
Turn Details from string -> StatusDetails - a general
bucket for keyed error behavior. Define an open enumeration
ReasonType exposed as Reason on the status object to provide
machine readable subcategorization beyond HTTP Status Code. Define
a human readable field Message which is common convention (previously
this was joined into Details).
Precedence order: HTTP Status Code, Reason, Details. apiserver would
impose restraints on the ReasonTypes defined by the main apiobject,
and ensure their use is consistent.
There are four long term scenarios this change supports:
1. Allow a client access to a machine readable field that can be
easily switched on for improving or translating the generic
server Message.
2. Return a 404 when a composite operation on multiple resources
fails with enough data so that a client can distinguish which
item does not exist. E.g. resource Parent and resource Child,
POST /parents/1/children to create a new Child, but /parents/1
is deleted. POST returns 404, ReasonTypeNotFound, and
Details.ID = "1", Details.Kind = "parent"
3. Allow a client to receive validation data that is keyed by
attribute for building user facing UIs around field submission.
Validation is usually expressed as map[string][]string, but
that type is less appropriate for many other uses.
4. Allow specific API errors to return more granular failure status
for specific operations. An example might be a minion proxy,
where the operation that failed may be both proxying OR the
minion itself. In this case a reason may be defined "proxy_failed"
corresponding to 502, where the Details field may be extended
to contain a nested error object.
At this time only ID and Kind are exposed
2014-07-31 18:12:26 +00:00
|
|
|
|
2014-08-26 17:36:09 +00:00
|
|
|
// StatusReasonAlreadyExists means the resource you are creating already exists.
|
Evolve the api.Status object with Reason/Details
Contains breaking API change on api.Status#Details (type change)
Turn Details from string -> StatusDetails - a general
bucket for keyed error behavior. Define an open enumeration
ReasonType exposed as Reason on the status object to provide
machine readable subcategorization beyond HTTP Status Code. Define
a human readable field Message which is common convention (previously
this was joined into Details).
Precedence order: HTTP Status Code, Reason, Details. apiserver would
impose restraints on the ReasonTypes defined by the main apiobject,
and ensure their use is consistent.
There are four long term scenarios this change supports:
1. Allow a client access to a machine readable field that can be
easily switched on for improving or translating the generic
server Message.
2. Return a 404 when a composite operation on multiple resources
fails with enough data so that a client can distinguish which
item does not exist. E.g. resource Parent and resource Child,
POST /parents/1/children to create a new Child, but /parents/1
is deleted. POST returns 404, ReasonTypeNotFound, and
Details.ID = "1", Details.Kind = "parent"
3. Allow a client to receive validation data that is keyed by
attribute for building user facing UIs around field submission.
Validation is usually expressed as map[string][]string, but
that type is less appropriate for many other uses.
4. Allow specific API errors to return more granular failure status
for specific operations. An example might be a minion proxy,
where the operation that failed may be both proxying OR the
minion itself. In this case a reason may be defined "proxy_failed"
corresponding to 502, where the Details field may be extended
to contain a nested error object.
At this time only ID and Kind are exposed
2014-07-31 18:12:26 +00:00
|
|
|
// Details (optional):
|
|
|
|
// "kind" string - the kind attribute of the conflicting resource
|
|
|
|
// "id" string - the identifier of the conflicting resource
|
|
|
|
// Status code 409
|
2014-09-28 04:32:53 +00:00
|
|
|
StatusReasonAlreadyExists StatusReason = "AlreadyExists"
|
Evolve the api.Status object with Reason/Details
Contains breaking API change on api.Status#Details (type change)
Turn Details from string -> StatusDetails - a general
bucket for keyed error behavior. Define an open enumeration
ReasonType exposed as Reason on the status object to provide
machine readable subcategorization beyond HTTP Status Code. Define
a human readable field Message which is common convention (previously
this was joined into Details).
Precedence order: HTTP Status Code, Reason, Details. apiserver would
impose restraints on the ReasonTypes defined by the main apiobject,
and ensure their use is consistent.
There are four long term scenarios this change supports:
1. Allow a client access to a machine readable field that can be
easily switched on for improving or translating the generic
server Message.
2. Return a 404 when a composite operation on multiple resources
fails with enough data so that a client can distinguish which
item does not exist. E.g. resource Parent and resource Child,
POST /parents/1/children to create a new Child, but /parents/1
is deleted. POST returns 404, ReasonTypeNotFound, and
Details.ID = "1", Details.Kind = "parent"
3. Allow a client to receive validation data that is keyed by
attribute for building user facing UIs around field submission.
Validation is usually expressed as map[string][]string, but
that type is less appropriate for many other uses.
4. Allow specific API errors to return more granular failure status
for specific operations. An example might be a minion proxy,
where the operation that failed may be both proxying OR the
minion itself. In this case a reason may be defined "proxy_failed"
corresponding to 502, where the Details field may be extended
to contain a nested error object.
At this time only ID and Kind are exposed
2014-07-31 18:12:26 +00:00
|
|
|
|
2014-09-02 10:00:28 +00:00
|
|
|
// StatusReasonConflict means the requested update operation cannot be completed
|
Evolve the api.Status object with Reason/Details
Contains breaking API change on api.Status#Details (type change)
Turn Details from string -> StatusDetails - a general
bucket for keyed error behavior. Define an open enumeration
ReasonType exposed as Reason on the status object to provide
machine readable subcategorization beyond HTTP Status Code. Define
a human readable field Message which is common convention (previously
this was joined into Details).
Precedence order: HTTP Status Code, Reason, Details. apiserver would
impose restraints on the ReasonTypes defined by the main apiobject,
and ensure their use is consistent.
There are four long term scenarios this change supports:
1. Allow a client access to a machine readable field that can be
easily switched on for improving or translating the generic
server Message.
2. Return a 404 when a composite operation on multiple resources
fails with enough data so that a client can distinguish which
item does not exist. E.g. resource Parent and resource Child,
POST /parents/1/children to create a new Child, but /parents/1
is deleted. POST returns 404, ReasonTypeNotFound, and
Details.ID = "1", Details.Kind = "parent"
3. Allow a client to receive validation data that is keyed by
attribute for building user facing UIs around field submission.
Validation is usually expressed as map[string][]string, but
that type is less appropriate for many other uses.
4. Allow specific API errors to return more granular failure status
for specific operations. An example might be a minion proxy,
where the operation that failed may be both proxying OR the
minion itself. In this case a reason may be defined "proxy_failed"
corresponding to 502, where the Details field may be extended
to contain a nested error object.
At this time only ID and Kind are exposed
2014-07-31 18:12:26 +00:00
|
|
|
// due to a conflict in the operation. The client may need to alter the request.
|
|
|
|
// Each resource may define custom details that indicate the nature of the
|
|
|
|
// conflict.
|
|
|
|
// Status code 409
|
2014-09-28 04:32:53 +00:00
|
|
|
StatusReasonConflict StatusReason = "Conflict"
|
2014-08-20 02:58:24 +00:00
|
|
|
|
2014-09-02 10:00:28 +00:00
|
|
|
// StatusReasonInvalid means the requested create or update operation cannot be
|
2014-08-20 02:58:24 +00:00
|
|
|
// completed due to invalid data provided as part of the request. The client may
|
|
|
|
// need to alter the request. When set, the client may use the StatusDetails
|
|
|
|
// message field as a summary of the issues encountered.
|
|
|
|
// Details (optional):
|
|
|
|
// "kind" string - the kind attribute of the invalid resource
|
|
|
|
// "id" string - the identifier of the invalid resource
|
|
|
|
// "causes" - one or more StatusCause entries indicating the data in the
|
|
|
|
// provided resource that was invalid. The code, message, and
|
|
|
|
// field attributes will be set.
|
|
|
|
// Status code 422
|
2014-09-28 04:32:53 +00:00
|
|
|
StatusReasonInvalid StatusReason = "Invalid"
|
2014-11-02 20:30:25 +00:00
|
|
|
|
2015-02-12 17:24:34 +00:00
|
|
|
// StatusReasonServerTimeout means the server can be reached and understood the request,
|
2015-01-29 04:11:29 +00:00
|
|
|
// but cannot complete the action in a reasonable time. The client should retry the request.
|
|
|
|
// This is may be due to temporary server load or a transient communication issue with
|
|
|
|
// another server. Status code 500 is used because the HTTP spec provides no suitable
|
|
|
|
// server-requested client retry and the 5xx class represents actionable errors.
|
|
|
|
// Details (optional):
|
|
|
|
// "kind" string - the kind attribute of the resource being acted on.
|
|
|
|
// "id" string - the operation that is being attempted.
|
|
|
|
// Status code 500
|
2015-02-12 17:24:34 +00:00
|
|
|
StatusReasonServerTimeout StatusReason = "ServerTimeout"
|
2015-01-29 04:11:29 +00:00
|
|
|
|
2015-01-22 05:20:57 +00:00
|
|
|
// StatusReasonTimeout means that the request could not be completed within the given time.
|
|
|
|
// Clients can get this response only when they specified a timeout param in the request.
|
|
|
|
// The request might succeed with an increased value of timeout param.
|
|
|
|
// Status code 504
|
|
|
|
StatusReasonTimeout StatusReason = "Timeout"
|
|
|
|
|
2014-11-02 20:30:25 +00:00
|
|
|
// StatusReasonBadRequest means that the request itself was invalid, because the request
|
|
|
|
// doesn't make any sense, for example deleting a read-only object. This is different than
|
|
|
|
// StatusReasonInvalid above which indicates that the API call could possibly succeed, but the
|
|
|
|
// data was invalid. API calls that return BadRequest can never succeed.
|
|
|
|
StatusReasonBadRequest StatusReason = "BadRequest"
|
2014-10-31 06:03:52 +00:00
|
|
|
|
2015-01-12 05:12:49 +00:00
|
|
|
// StatusReasonMethodNotAllowed means that the action the client attempted to perform on the
|
|
|
|
// resource was not supported by the code - for instance, attempting to delete a resource that
|
|
|
|
// can only be created. API calls that return MethodNotAllowed can never succeed.
|
|
|
|
StatusReasonMethodNotAllowed StatusReason = "MethodNotAllowed"
|
|
|
|
|
2014-10-31 06:03:52 +00:00
|
|
|
// StatusReasonInternalError indicates that an internal error occurred, it is unexpected
|
|
|
|
// and the outcome of the call is unknown.
|
|
|
|
// Details (optional):
|
|
|
|
// "causes" - The original error
|
|
|
|
// Status code 500
|
|
|
|
StatusReasonInternalError = "InternalError"
|
2014-08-20 02:58:24 +00:00
|
|
|
)
|
|
|
|
|
|
|
|
// StatusCause provides more information about an api.Status failure, including
|
|
|
|
// cases when multiple errors are encountered.
|
|
|
|
type StatusCause struct {
|
|
|
|
// A machine-readable description of the cause of the error. If this value is
|
|
|
|
// empty there is no information available.
|
2014-12-01 05:31:52 +00:00
|
|
|
Type CauseType `json:"reason,omitempty"`
|
2014-08-20 02:58:24 +00:00
|
|
|
// A human-readable description of the cause of the error. This field may be
|
|
|
|
// presented as-is to a reader.
|
2014-12-01 05:31:52 +00:00
|
|
|
Message string `json:"message,omitempty"`
|
2014-08-20 02:58:24 +00:00
|
|
|
// The field of the resource that has caused this error, as named by its JSON
|
|
|
|
// serialization. May include dot and postfix notation for nested attributes.
|
|
|
|
// Arrays are zero-indexed. Fields may appear more than once in an array of
|
|
|
|
// causes due to fields having multiple errors.
|
|
|
|
// Optional.
|
|
|
|
//
|
|
|
|
// Examples:
|
|
|
|
// "name" - the field "name" on the current resource
|
|
|
|
// "items[0].name" - the field "name" on the first array entry in "items"
|
2014-12-01 05:31:52 +00:00
|
|
|
Field string `json:"field,omitempty"`
|
2014-08-20 02:58:24 +00:00
|
|
|
}
|
|
|
|
|
2014-08-26 17:36:09 +00:00
|
|
|
// CauseType is a machine readable value providing more detail about what
|
|
|
|
// occured in a status response. An operation may have multiple causes for a
|
2015-01-29 04:41:37 +00:00
|
|
|
// status (whether Failure or Success).
|
2014-08-26 17:36:09 +00:00
|
|
|
type CauseType string
|
2014-08-20 02:58:24 +00:00
|
|
|
|
|
|
|
const (
|
2014-08-26 17:36:09 +00:00
|
|
|
// CauseTypeFieldValueNotFound is used to report failure to find a requested value
|
2014-08-20 02:58:24 +00:00
|
|
|
// (e.g. looking up an ID).
|
2014-09-28 04:48:35 +00:00
|
|
|
CauseTypeFieldValueNotFound CauseType = "FieldValueNotFound"
|
2014-11-13 12:01:25 +00:00
|
|
|
// CauseTypeFieldValueRequired is used to report required values that are not
|
2014-08-20 02:58:24 +00:00
|
|
|
// provided (e.g. empty strings, null values, or empty arrays).
|
2014-09-28 04:48:35 +00:00
|
|
|
CauseTypeFieldValueRequired CauseType = "FieldValueRequired"
|
2014-08-26 17:36:09 +00:00
|
|
|
// CauseTypeFieldValueDuplicate is used to report collisions of values that must be
|
2014-08-20 02:58:24 +00:00
|
|
|
// unique (e.g. unique IDs).
|
2014-09-28 04:48:35 +00:00
|
|
|
CauseTypeFieldValueDuplicate CauseType = "FieldValueDuplicate"
|
2014-08-26 17:36:09 +00:00
|
|
|
// CauseTypeFieldValueInvalid is used to report malformed values (e.g. failed regex
|
2014-08-20 02:58:24 +00:00
|
|
|
// match).
|
2014-09-28 04:48:35 +00:00
|
|
|
CauseTypeFieldValueInvalid CauseType = "FieldValueInvalid"
|
2014-08-26 17:36:09 +00:00
|
|
|
// CauseTypeFieldValueNotSupported is used to report valid (as per formatting rules)
|
2014-08-20 02:58:24 +00:00
|
|
|
// values that can not be handled (e.g. an enumerated string).
|
2014-09-28 04:48:35 +00:00
|
|
|
CauseTypeFieldValueNotSupported CauseType = "FieldValueNotSupported"
|
Evolve the api.Status object with Reason/Details
Contains breaking API change on api.Status#Details (type change)
Turn Details from string -> StatusDetails - a general
bucket for keyed error behavior. Define an open enumeration
ReasonType exposed as Reason on the status object to provide
machine readable subcategorization beyond HTTP Status Code. Define
a human readable field Message which is common convention (previously
this was joined into Details).
Precedence order: HTTP Status Code, Reason, Details. apiserver would
impose restraints on the ReasonTypes defined by the main apiobject,
and ensure their use is consistent.
There are four long term scenarios this change supports:
1. Allow a client access to a machine readable field that can be
easily switched on for improving or translating the generic
server Message.
2. Return a 404 when a composite operation on multiple resources
fails with enough data so that a client can distinguish which
item does not exist. E.g. resource Parent and resource Child,
POST /parents/1/children to create a new Child, but /parents/1
is deleted. POST returns 404, ReasonTypeNotFound, and
Details.ID = "1", Details.Kind = "parent"
3. Allow a client to receive validation data that is keyed by
attribute for building user facing UIs around field submission.
Validation is usually expressed as map[string][]string, but
that type is less appropriate for many other uses.
4. Allow specific API errors to return more granular failure status
for specific operations. An example might be a minion proxy,
where the operation that failed may be both proxying OR the
minion itself. In this case a reason may be defined "proxy_failed"
corresponding to 502, where the Details field may be extended
to contain a nested error object.
At this time only ID and Kind are exposed
2014-07-31 18:12:26 +00:00
|
|
|
)
|
|
|
|
|
2014-09-24 21:35:34 +00:00
|
|
|
// ObjectReference contains enough information to let you inspect or modify the referred object.
|
|
|
|
type ObjectReference struct {
|
2015-01-14 23:22:21 +00:00
|
|
|
Kind string `json:"kind,omitempty"`
|
|
|
|
Namespace string `json:"namespace,omitempty"`
|
|
|
|
Name string `json:"name,omitempty"`
|
|
|
|
UID types.UID `json:"uid,omitempty"`
|
|
|
|
APIVersion string `json:"apiVersion,omitempty"`
|
|
|
|
ResourceVersion string `json:"resourceVersion,omitempty"`
|
2014-09-24 21:35:34 +00:00
|
|
|
|
|
|
|
// Optional. If referring to a piece of an object instead of an entire object, this string
|
2014-12-30 01:10:38 +00:00
|
|
|
// should contain information to identify the sub-object. For example, if the object
|
|
|
|
// reference is to a container within a pod, this would take on a value like:
|
|
|
|
// "spec.containers{name}" (where "name" refers to the name of the container that triggered
|
|
|
|
// the event) or if no container name is specified "spec.containers[2]" (container with
|
|
|
|
// index 2 in this pod). This syntax is chosen only to have some well-defined way of
|
2014-09-24 21:35:34 +00:00
|
|
|
// referencing a part of an object.
|
|
|
|
// TODO: this design is not final and this field is subject to change in the future.
|
2014-12-01 05:31:52 +00:00
|
|
|
FieldPath string `json:"fieldPath,omitempty"`
|
2014-09-24 21:35:34 +00:00
|
|
|
}
|
|
|
|
|
2015-01-06 21:22:58 +00:00
|
|
|
type EventSource struct {
|
|
|
|
// Component from which the event is generated.
|
|
|
|
Component string `json:"component,omitempty"`
|
|
|
|
// Host name on which the event is generated.
|
|
|
|
Host string `json:"host,omitempty"`
|
|
|
|
}
|
|
|
|
|
2014-09-24 21:35:34 +00:00
|
|
|
// Event is a report of an event somewhere in the cluster.
|
|
|
|
// TODO: Decide whether to store these separately or with the object they apply to.
|
|
|
|
type Event struct {
|
2014-12-01 05:31:52 +00:00
|
|
|
TypeMeta `json:",inline"`
|
|
|
|
ObjectMeta `json:"metadata,omitempty"`
|
2014-09-24 21:35:34 +00:00
|
|
|
|
|
|
|
// Required. The object that this event is about.
|
2014-12-01 05:31:52 +00:00
|
|
|
InvolvedObject ObjectReference `json:"involvedObject,omitempty"`
|
2014-09-24 21:35:34 +00:00
|
|
|
|
|
|
|
// Optional; this should be a short, machine understandable string that gives the reason
|
2015-01-14 01:10:57 +00:00
|
|
|
// for this event being generated. For example, if the event is reporting that a container
|
|
|
|
// can't start, the Reason might be "ImageNotFound".
|
2014-09-24 21:35:34 +00:00
|
|
|
// TODO: provide exact specification for format.
|
2014-12-01 05:31:52 +00:00
|
|
|
Reason string `json:"reason,omitempty"`
|
2014-09-24 21:35:34 +00:00
|
|
|
|
|
|
|
// Optional. A human-readable description of the status of this operation.
|
|
|
|
// TODO: decide on maximum length.
|
2014-12-01 05:31:52 +00:00
|
|
|
Message string `json:"message,omitempty"`
|
2014-09-24 21:35:34 +00:00
|
|
|
|
|
|
|
// Optional. The component reporting this event. Should be a short machine understandable string.
|
2015-01-06 21:22:58 +00:00
|
|
|
Source EventSource `json:"source,omitempty"`
|
2014-10-22 05:28:12 +00:00
|
|
|
|
2015-02-06 02:21:01 +00:00
|
|
|
// The time at which the event was first recorded. (Time of server receipt is in TypeMeta.)
|
|
|
|
FirstTimestamp util.Time `json:"firstTimestamp,omitempty"`
|
|
|
|
|
|
|
|
// The time at which the most recent occurance of this event was recorded.
|
|
|
|
LastTimestamp util.Time `json:"lastTimestamp,omitempty"`
|
|
|
|
|
|
|
|
// The number of times this event has occurred.
|
|
|
|
Count int `json:"count,omitempty"`
|
2014-09-24 21:35:34 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
// EventList is a list of events.
|
|
|
|
type EventList struct {
|
2014-12-01 05:31:52 +00:00
|
|
|
TypeMeta `json:",inline"`
|
|
|
|
ListMeta `json:"metadata,omitempty"`
|
2014-10-22 15:08:38 +00:00
|
|
|
|
2014-12-01 05:31:52 +00:00
|
|
|
Items []Event `json:"items"`
|
2014-09-24 21:35:34 +00:00
|
|
|
}
|
|
|
|
|
2014-10-08 13:57:56 +00:00
|
|
|
// ContainerManifest corresponds to the Container Manifest format, documented at:
|
|
|
|
// https://developers.google.com/compute/docs/containers/container_vms#container_manifest
|
|
|
|
// This is used as the representation of Kubernetes workloads.
|
|
|
|
// DEPRECATED: Replaced with BoundPod
|
|
|
|
type ContainerManifest struct {
|
|
|
|
// Required: This must be a supported version string, such as "v1beta1".
|
2014-12-01 05:31:52 +00:00
|
|
|
Version string `json:"version"`
|
2014-10-08 13:57:56 +00:00
|
|
|
// Required: This must be a DNS_SUBDOMAIN.
|
|
|
|
// TODO: ID on Manifest is deprecated and will be removed in the future.
|
2014-12-01 05:31:52 +00:00
|
|
|
ID string `json:"id"`
|
2014-10-08 13:57:56 +00:00
|
|
|
// TODO: UUID on Manifest is deprecated in the future once we are done
|
|
|
|
// with the API refactoring. It is required for now to determine the instance
|
|
|
|
// of a Pod.
|
2015-01-14 23:22:21 +00:00
|
|
|
UUID types.UID `json:"uuid,omitempty"`
|
2014-12-01 05:31:52 +00:00
|
|
|
Volumes []Volume `json:"volumes"`
|
|
|
|
Containers []Container `json:"containers"`
|
|
|
|
RestartPolicy RestartPolicy `json:"restartPolicy,omitempty"`
|
2015-02-18 19:09:49 +00:00
|
|
|
// Required: Set DNS policy.
|
2014-11-12 05:21:40 +00:00
|
|
|
DNSPolicy DNSPolicy `json:"dnsPolicy"`
|
2014-10-08 13:57:56 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
// ContainerManifestList is used to communicate container manifests to kubelet.
|
|
|
|
// DEPRECATED: Replaced with BoundPods
|
|
|
|
type ContainerManifestList struct {
|
2014-12-01 05:31:52 +00:00
|
|
|
TypeMeta `json:",inline"`
|
|
|
|
ListMeta `json:"metadata,omitempty"`
|
2014-10-22 15:08:38 +00:00
|
|
|
|
2014-12-01 05:31:52 +00:00
|
|
|
Items []ContainerManifest `json:"items"`
|
2014-10-08 13:57:56 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
// BoundPod is a collection of containers that should be run on a host. A BoundPod
|
|
|
|
// defines how a Pod may change after a Binding is created. A Pod is a request to
|
|
|
|
// execute a pod, whereas a BoundPod is the specification that would be run on a server.
|
|
|
|
type BoundPod struct {
|
2014-12-01 05:31:52 +00:00
|
|
|
TypeMeta `json:",inline"`
|
|
|
|
ObjectMeta `json:"metadata,omitempty"`
|
2014-10-08 13:57:56 +00:00
|
|
|
|
|
|
|
// Spec defines the behavior of a pod.
|
2014-12-01 05:31:52 +00:00
|
|
|
Spec PodSpec `json:"spec,omitempty"`
|
2014-10-08 13:57:56 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
// BoundPods is a list of Pods bound to a common server. The resource version of
|
|
|
|
// the pod list is guaranteed to only change when the list of bound pods changes.
|
|
|
|
type BoundPods struct {
|
2014-12-01 05:31:52 +00:00
|
|
|
TypeMeta `json:",inline"`
|
|
|
|
ObjectMeta `json:"metadata,omitempty"`
|
2014-10-08 13:57:56 +00:00
|
|
|
|
|
|
|
// Host is the name of a node that these pods were bound to.
|
2014-12-01 05:31:52 +00:00
|
|
|
Host string `json:"host"`
|
2014-10-08 13:57:56 +00:00
|
|
|
|
|
|
|
// Items is the list of all pods bound to a given host.
|
2014-12-01 05:31:52 +00:00
|
|
|
Items []BoundPod `json:"items"`
|
2014-10-08 13:57:56 +00:00
|
|
|
}
|
2014-12-08 02:19:10 +00:00
|
|
|
|
|
|
|
// List holds a list of objects, which may not be known by the server.
|
|
|
|
type List struct {
|
|
|
|
TypeMeta `json:",inline"`
|
|
|
|
ListMeta `json:"metadata,omitempty"`
|
|
|
|
|
|
|
|
Items []runtime.Object `json:"items"`
|
|
|
|
}
|
2015-01-22 21:52:40 +00:00
|
|
|
|
2015-01-27 21:54:50 +00:00
|
|
|
// A type of object that is limited
|
|
|
|
type LimitType string
|
|
|
|
|
2015-01-23 03:21:13 +00:00
|
|
|
const (
|
|
|
|
// Limit that applies to all pods in a namespace
|
2015-01-27 21:54:50 +00:00
|
|
|
LimitTypePod LimitType = "Pod"
|
2015-01-23 03:21:13 +00:00
|
|
|
// Limit that applies to all containers in a namespace
|
2015-01-27 21:54:50 +00:00
|
|
|
LimitTypeContainer LimitType = "Container"
|
2015-01-23 03:21:13 +00:00
|
|
|
)
|
|
|
|
|
2015-01-22 21:52:40 +00:00
|
|
|
// LimitRangeItem defines a min/max usage limit for any resource that matches on kind
|
|
|
|
type LimitRangeItem struct {
|
2015-01-23 03:21:13 +00:00
|
|
|
// Type of resource that this limit applies to
|
2015-01-27 21:54:50 +00:00
|
|
|
Type LimitType `json:"type,omitempty"`
|
2015-01-22 21:52:40 +00:00
|
|
|
// Max usage constraints on this kind by resource name
|
|
|
|
Max ResourceList `json:"max,omitempty"`
|
|
|
|
// Min usage constraints on this kind by resource name
|
|
|
|
Min ResourceList `json:"min,omitempty"`
|
|
|
|
}
|
|
|
|
|
|
|
|
// LimitRangeSpec defines a min/max usage limit for resources that match on kind
|
|
|
|
type LimitRangeSpec struct {
|
|
|
|
// Limits is the list of LimitRangeItem objects that are enforced
|
|
|
|
Limits []LimitRangeItem `json:"limits"`
|
|
|
|
}
|
|
|
|
|
|
|
|
// LimitRange sets resource usage limits for each kind of resource in a Namespace
|
|
|
|
type LimitRange struct {
|
|
|
|
TypeMeta `json:",inline"`
|
|
|
|
ObjectMeta `json:"metadata,omitempty"`
|
|
|
|
|
|
|
|
// Spec defines the limits enforced
|
|
|
|
Spec LimitRangeSpec `json:"spec,omitempty"`
|
|
|
|
}
|
|
|
|
|
|
|
|
// LimitRangeList is a list of LimitRange items.
|
|
|
|
type LimitRangeList struct {
|
|
|
|
TypeMeta `json:",inline"`
|
|
|
|
ListMeta `json:"metadata,omitempty"`
|
|
|
|
|
|
|
|
// Items is a list of LimitRange objects
|
|
|
|
Items []LimitRange `json:"items"`
|
|
|
|
}
|
2015-01-23 17:38:30 +00:00
|
|
|
|
|
|
|
// The following identify resource constants for Kubernetes object types
|
|
|
|
const (
|
|
|
|
// Pods, number
|
|
|
|
ResourcePods ResourceName = "pods"
|
|
|
|
// Services, number
|
|
|
|
ResourceServices ResourceName = "services"
|
|
|
|
// ReplicationControllers, number
|
|
|
|
ResourceReplicationControllers ResourceName = "replicationcontrollers"
|
|
|
|
// ResourceQuotas, number
|
|
|
|
ResourceQuotas ResourceName = "resourcequotas"
|
|
|
|
)
|
|
|
|
|
|
|
|
// ResourceQuotaSpec defines the desired hard limits to enforce for Quota
|
|
|
|
type ResourceQuotaSpec struct {
|
|
|
|
// Hard is the set of desired hard limits for each named resource
|
|
|
|
Hard ResourceList `json:"hard,omitempty"`
|
|
|
|
}
|
|
|
|
|
|
|
|
// ResourceQuotaStatus defines the enforced hard limits and observed use
|
|
|
|
type ResourceQuotaStatus struct {
|
|
|
|
// Hard is the set of enforced hard limits for each named resource
|
|
|
|
Hard ResourceList `json:"hard,omitempty"`
|
|
|
|
// Used is the current observed total usage of the resource in the namespace
|
|
|
|
Used ResourceList `json:"used,omitempty"`
|
|
|
|
}
|
|
|
|
|
|
|
|
// ResourceQuota sets aggregate quota restrictions enforced per namespace
|
|
|
|
type ResourceQuota struct {
|
|
|
|
TypeMeta `json:",inline"`
|
|
|
|
ObjectMeta `json:"metadata,omitempty"`
|
|
|
|
|
|
|
|
// Spec defines the desired quota
|
|
|
|
Spec ResourceQuotaSpec `json:"spec,omitempty"`
|
|
|
|
|
|
|
|
// Status defines the actual enforced quota and its current usage
|
|
|
|
Status ResourceQuotaStatus `json:"status,omitempty"`
|
|
|
|
}
|
|
|
|
|
|
|
|
// ResourceQuotaUsage captures system observed quota status per namespace
|
|
|
|
// It is used to enforce atomic updates of a backing ResourceQuota.Status field in storage
|
|
|
|
type ResourceQuotaUsage struct {
|
|
|
|
TypeMeta `json:",inline"`
|
|
|
|
ObjectMeta `json:"metadata,omitempty"`
|
|
|
|
|
|
|
|
// Status defines the actual enforced quota and its current usage
|
|
|
|
Status ResourceQuotaStatus `json:"status,omitempty"`
|
|
|
|
}
|
|
|
|
|
|
|
|
// ResourceQuotaList is a list of ResourceQuota items
|
|
|
|
type ResourceQuotaList struct {
|
|
|
|
TypeMeta `json:",inline"`
|
|
|
|
ListMeta `json:"metadata,omitempty"`
|
|
|
|
|
|
|
|
// Items is a list of ResourceQuota objects
|
|
|
|
Items []ResourceQuota `json:"items"`
|
|
|
|
}
|
2015-02-18 01:24:50 +00:00
|
|
|
|
2015-02-18 01:26:41 +00:00
|
|
|
// Secret holds secret data of a certain type. The total bytes of the values in
|
|
|
|
// the Data field must be less than MaxSecretSize bytes.
|
2015-02-18 01:24:50 +00:00
|
|
|
type Secret struct {
|
|
|
|
TypeMeta `json:",inline"`
|
|
|
|
ObjectMeta `json:"metadata,omitempty"`
|
|
|
|
|
2015-02-18 01:26:41 +00:00
|
|
|
// Data contains the secret data. Each key must be a valid DNS_SUBDOMAIN.
|
|
|
|
// The serialized form of the secret data is a base64 encoded string.
|
2015-02-18 01:24:50 +00:00
|
|
|
Data map[string][]byte `json:"data,omitempty"`
|
2015-02-18 01:26:41 +00:00
|
|
|
|
|
|
|
// Used to facilitate programatic handling of secret data.
|
|
|
|
Type SecretType `json:"type,omitempty"`
|
2015-02-18 01:24:50 +00:00
|
|
|
}
|
|
|
|
|
2015-02-18 01:26:41 +00:00
|
|
|
const MaxSecretSize = 1 * 1024 * 1024
|
|
|
|
|
2015-02-18 01:24:50 +00:00
|
|
|
type SecretType string
|
|
|
|
|
|
|
|
const (
|
|
|
|
SecretTypeOpaque SecretType = "opaque" // Default; arbitrary user-defined data
|
|
|
|
)
|
|
|
|
|
|
|
|
type SecretList struct {
|
|
|
|
TypeMeta `json:",inline"`
|
|
|
|
ListMeta `json:"metadata,omitempty"`
|
|
|
|
|
|
|
|
Items []Secret `json:"items"`
|
|
|
|
}
|