diff --git a/docs/reference/generated/kubernetes-api/v1.9/index.html b/docs/reference/generated/kubernetes-api/v1.9/index.html index ee5ea737b1..1b33696eba 100644 --- a/docs/reference/generated/kubernetes-api/v1.9/index.html +++ b/docs/reference/generated/kubernetes-api/v1.9/index.html @@ -179,7 +179,7 @@ Appears In: ports
ContainerPort array
patch type: merge
patch merge key: containerPort -List of ports to expose from the container. Exposing a port here gives the system additional information about the network connections a container uses, but is primarily informational. Not specifying a port here DOES NOT prevent that port from being exposed. Any port which is listening on the default "0.0.0.0" address inside a container will be accessible from the network. Cannot be updated. +List of ports to expose from the container. Exposing a port here gives the system additional information about the network connections a container uses, but is primarily informational. Not specifying a port here DOES NOT prevent that port from being exposed. Any port which is listening on the default "0.0.0.0" address inside a container will be accessible from the network. Cannot be updated. readinessProbe
Probe @@ -245,7 +245,7 @@ Appears In: containerID
string -Container's ID in the format 'docker://'. +Container's ID in the format 'docker://<container_id>'. image
string @@ -354,7 +354,7 @@ Appears In: concurrencyPolicy
string -Specifies how to treat concurrent executions of a Job. Valid values are: - "Allow" (default): allows CronJobs to run concurrently; - "Forbid": forbids concurrent runs, skipping next run if previous run hasn't finished yet; - "Replace": cancels currently running job and replaces it with a new one +Specifies how to treat concurrent executions of a Job. Valid values are: - "Allow" (default): allows CronJobs to run concurrently; - "Forbid": forbids concurrent runs, skipping next run if previous run hasn't finished yet; - "Replace": cancels currently running job and replaces it with a new one failedJobsHistoryLimit
integer @@ -520,10 +520,6 @@ Appears In: -202
CronJob -Accepted - - 200
CronJob OK @@ -531,6 +527,10 @@ Appears In: 201
CronJob Created + +202
CronJob +Accepted +

Patch

@@ -712,13 +712,13 @@ Appears In: -201
CronJob -Created - - 200
CronJob OK + +201
CronJob +Created +

Delete

@@ -1774,13 +1774,13 @@ Appears In: -201
CronJob -Created - - 200
CronJob OK + +201
CronJob +Created +
@@ -2235,6 +2235,10 @@ spec: +202
DaemonSet +Accepted + + 200
DaemonSet OK @@ -2242,10 +2246,6 @@ spec: 201
DaemonSet Created - -202
DaemonSet -Accepted -

Patch

@@ -2427,13 +2427,13 @@ spec: -200
DaemonSet -OK - - 201
DaemonSet Created + +200
DaemonSet +OK +

Delete

@@ -3498,13 +3498,13 @@ $ curl -X GET http:// -200
DaemonSet -OK - - 201
DaemonSet Created + +200
DaemonSet +OK +
@@ -3763,7 +3763,7 @@ Appears In: type
string -Type of deployment. Can be "Recreate" or "RollingUpdate". Default is RollingUpdate. +Type of deployment. Can be "Recreate" or "RollingUpdate". Default is RollingUpdate. @@ -3785,7 +3785,7 @@ Appears In: maxSurge -The maximum number of pods that can be scheduled above the desired number of pods. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). This can not be 0 if MaxUnavailable is 0. Absolute number is calculated from percentage by rounding up. Defaults to 25%. Example: when this is set to 30%, the new RC can be scaled up immediately when the rolling update starts, such that the total number of old and new pods do not exceed 130% of desired pods. Once old pods have been killed, new RC can be scaled up further, ensuring that total number of pods running at any time during the update is at most 130% of desired pods. +The maximum number of pods that can be scheduled above the desired number of pods. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). This can not be 0 if MaxUnavailable is 0. Absolute number is calculated from percentage by rounding up. Defaults to 25%. Example: when this is set to 30%, the new RC can be scaled up immediately when the rolling update starts, such that the total number of old and new pods do not exceed 130% of desired pods. Once old pods have been killed, new RC can be scaled up further, ensuring that total number of pods running at any time during the update is atmost 130% of desired pods. maxUnavailable @@ -5979,13 +5979,13 @@ $ kubectl proxy -201
Deployment -Created - - 200
Deployment OK + +201
Deployment +Created +
@@ -8135,7 +8135,7 @@ Appears In: dnsPolicy
string -Set DNS policy for the pod. Defaults to "ClusterFirst". Valid values are 'ClusterFirstWithHostNet', 'ClusterFirst', 'Default' or 'None'. DNS parameters given in DNSConfig will be merged with the policy selected with DNSPolicy. To have DNS options set along with hostNetwork, you have to specify DNS policy explicitly to 'ClusterFirstWithHostNet'. Note that 'None' policy is an alpha feature introduced in v1.9 and CustomPodDNS feature gate must be enabled to use it. +Set DNS policy for the pod. Defaults to "ClusterFirst". Valid values are 'ClusterFirstWithHostNet', 'ClusterFirst', 'Default' or 'None'. DNS parameters given in DNSConfig will be merged with the policy selected with DNSPolicy. To have DNS options set along with hostNetwork, you have to specify DNS policy explicitly to 'ClusterFirstWithHostNet'. Note that 'None' policy is an alpha feature introduced in v1.9 and CustomPodDNS feature gate must be enabled to use it. hostAliases
HostAlias array
patch type: merge
patch merge key: ip @@ -8179,7 +8179,7 @@ Appears In: priorityClassName
string -If specified, indicates the pod's priority. "SYSTEM" is a special keyword which indicates the highest priority. Any other name must be defined by creating a PriorityClass object with that name. If not specified, the pod priority will be default or zero if there is no default. +If specified, indicates the pod's priority. "SYSTEM" is a special keyword which indicates the highest priority. Any other name must be defined by creating a PriorityClass object with that name. If not specified, the pod priority will be default or zero if there is no default. restartPolicy
string @@ -8203,7 +8203,7 @@ Appears In: subdomain
string -If specified, the fully qualified Pod hostname will be "...svc.". If not specified, the pod will not have a domainname at all. +If specified, the fully qualified Pod hostname will be "<hostname>.<subdomain>.<pod namespace>.svc.<cluster domain>". If not specified, the pod will not have a domainname at all. terminationGracePeriodSeconds
integer @@ -9643,13 +9643,13 @@ Appears In: -201
Pod -Created - - 200
Pod OK + +201
Pod +Created +

Proxy Operations

@@ -12765,13 +12765,13 @@ Appears In: -200
ReplicaSet -OK - - 201
ReplicaSet Created + +200
ReplicaSet +OK +
@@ -13068,6 +13068,10 @@ Appears In: +202
ReplicationController +Accepted + + 200
ReplicationController OK @@ -13075,10 +13079,6 @@ Appears In: 201
ReplicationController Created - -202
ReplicationController -Accepted -

Patch

@@ -14429,7 +14429,7 @@ Appears In: serviceName
string -serviceName is the name of the service that governs this StatefulSet. This service must exist before the StatefulSet, and is responsible for the network identity of the set. Pods get DNS/hostnames that follow the pattern: pod-specific-string.serviceName.default.svc.cluster.local where "pod-specific-string" is managed by the StatefulSet controller. +serviceName is the name of the service that governs this StatefulSet. This service must exist before the StatefulSet, and is responsible for the network identity of the set. Pods get DNS/hostnames that follow the pattern: pod-specific-string.serviceName.default.svc.cluster.local where "pod-specific-string" is managed by the StatefulSet controller. template
PodTemplateSpec @@ -14611,6 +14611,10 @@ Appears In: +200
StatefulSet +OK + + 201
StatefulSet Created @@ -14618,10 +14622,6 @@ Appears In: 202
StatefulSet Accepted - -200
StatefulSet -OK -

Patch

@@ -14803,13 +14803,13 @@ Appears In: -200
StatefulSet -OK - - 201
StatefulSet Created + +200
StatefulSet +OK +

Delete

@@ -15904,15 +15904,15 @@ Workloads can be accessed via proxy through the api master using the kubec

Endpoints is a collection of endpoints that implement the actual service. Example: - Name: "mysvc", + Name: "mysvc", Subsets: [ { - Addresses: [{"ip": "10.10.1.1"}, {"ip": "10.10.2.2"}], - Ports: [{"name": "a", "port": 8675}, {"name": "b", "port": 309}] + Addresses: [{"ip": "10.10.1.1"}, {"ip": "10.10.2.2"}], + Ports: [{"name": "a", "port": 8675}, {"name": "b", "port": 309}] }, { - Addresses: [{"ip": "10.10.3.3"}], - Ports: [{"name": "a", "port": 93}, {"name": "b", "port": 76}] + Addresses: [{"ip": "10.10.3.3"}], + Ports: [{"name": "a", "port": 93}, {"name": "b", "port": 76}] }, ]