diff --git a/api/docs/api/v1.PersistentVolume.adoc b/api/docs/api/v1.PersistentVolume.adoc index 317cab69d0eb..c5a348f5fed8 100644 --- a/api/docs/api/v1.PersistentVolume.adoc +++ b/api/docs/api/v1.PersistentVolume.adoc @@ -145,7 +145,7 @@ Populated by the system. Read-only. More info: http://kubernetes.io/docs/user-gu
apiVersion: batch/v1
is now available. You now do not need to specify the .spec.selector
field — a [unique selector is automatically generated ](http://kubernetes.io/docs/user-guide/jobs/#pod-selector)for you.
- * The previous version, apiVersion: extensions/v1beta1
, is still supported. Even if you roll back to 1.1, the objects created using
-the new apiVersion will still be accessible, using the old version. You can
-continue to use your existing JSON and YAML files until you are ready to switch
-to batch/v1
. We may remove support for Jobs with apiVersion: extensions/v1beta1
in 1.3 or 1.4.
- * HorizontalPodAutoscaler was Beta in 1.1 and is GA in 1.2 .
- * apiVersion: autoscaling/v1
is now available. Changes in this version are:
- * Field CPUUtilization which was a nested structure CPUTargetUtilization in
-HorizontalPodAutoscalerSpec was replaced by TargetCPUUtilizationPercentage
-which is an integer.
- * ScaleRef of type SubresourceReference in HorizontalPodAutoscalerSpec which
-referred to scale subresource of the resource being scaled was replaced by
-ScaleTargetRef which points just to the resource being scaled.
- * In extensions/v1beta1 if CPUUtilization in HorizontalPodAutoscalerSpec was not
-specified it was set to 80 by default while in autoscaling/v1 HPA object
-without TargetCPUUtilizationPercentage specified is a valid object. Pod
-autoscaler controller will apply a default scaling policy in this case which is
-equivalent to the previous one but may change in the future.
- * The previous version, apiVersion: extensions/v1beta1
, is still supported. Even if you roll back to 1.1, the objects created using
-the new apiVersions will still be accessible, using the old version. You can
-continue to use your existing JSON and YAML files until you are ready to switch
-to autoscaling/v1
. We may remove support for HorizontalPodAutoscalers with apiVersion: extensions/v1beta1
in 1.3 or 1.4.
- * Kube-Proxy now defaults to an iptables-based proxy. If the --proxy-mode flag is
-specified while starting kube-proxy (‘userspace’ or ‘iptables’), the flag value
-will be respected. If the flag value is not specified, the kube-proxy respects
-the Node object annotation: ‘net.beta.kubernetes.io/proxy-mode’. If the
-annotation is not specified, then ‘iptables’ mode is the default. If kube-proxy
-is unable to start in iptables mode because system requirements are not met
-(kernel or iptables versions are insufficient), the kube-proxy will fall-back
-to userspace mode. Kube-proxy is much more performant and less
-resource-intensive in ‘iptables’ mode.
- * Node stability can be improved by reserving [resources](https://github.com/kubernetes/kubernetes/blob/release-1.2/docs/proposals/node-allocatable.md) for the base operating system using --system-reserved and --kube-reserved Kubelet flags
- * Liveness and readiness probes now support more configuration parameters:
-periodSeconds, successThreshold, failureThreshold
- * The new ReplicaSet API (Beta) in the Extensions API group is similar to
-ReplicationController, but its [selector](http://kubernetes.io/docs/user-guide/labels/#label-selectors) is more general (supports set-based selector; whereas ReplicationController
-only supports equality-based selector).
- * Scale subresource support is now expanded to ReplicaSets along with
-ReplicationControllers and Deployments. Scale now supports two different types
-of selectors to accommodate both [equality-based selectors](http://kubernetes.io/docs/user-guide/labels/#equality-based-requirement) supported by ReplicationControllers and [set-based selectors](http://kubernetes.io/docs/user-guide/labels/#set-based-requirement) supported by Deployments and ReplicaSets.
- * “kubectl run” now produces Deployments (instead of ReplicationControllers) and
-Jobs (instead of Pods) by default.
- * Pods can now consume Secret data in environment variables and inject those
-environment variables into a container’s command-line args.
- * Stable version of Heapster which scales up to 1000 nodes: more metrics, reduced
-latency, reduced cpu/memory consumption (~4mb per monitored node).
- * Pods now have a security context which allows users to specify:
- * attributes which apply to the whole pod:
- * User ID
- * Whether all containers should be non-root
- * Supplemental Groups
- * FSGroup - a special supplemental group
- * SELinux options
- * If a pod defines an FSGroup, that Pod’s system (emptyDir, secret, configMap,
-etc) volumes and block-device volumes will be owned by the FSGroup, and each
-container in the pod will run with the FSGroup as a supplemental group
- * Volumes that support SELinux labelling are now automatically relabeled with the
-Pod’s SELinux context, if specified
- * A stable client library release\_1\_2 is added. The library is [here](pkg/client/clientset_generated/), and detailed doc is [here](docs/devel/generating-clientset.md#released-clientsets). We will keep the interface of this go client stable.
- * New Azure File Service Volume Plugin enables mounting Microsoft Azure File
-Volumes (SMB 2.1 and 3.0) into a Pod. See [example](https://github.com/kubernetes/kubernetes/blob/release-1.2/examples/azure_file/README.md) for details.
- * Logs usage and root filesystem usage of a container, volumes usage of a pod and node disk usage are exposed through Kubelet new metrics API.
-
-### Experimental Features
-
- * Dynamic Provisioning of PersistentVolumes: Kubernetes previously required all
-volumes to be manually provisioned by a cluster administrator before use. With
-this feature, volume plugins that support it (GCE PD, AWS EBS, and Cinder) can
-automatically provision a PersistentVolume to bind to an unfulfilled
-PersistentVolumeClaim.
- * Run multiple schedulers in parallel, e.g. one or more custom schedulers
-alongside the default Kubernetes scheduler, using pod annotations to select
-among the schedulers for each pod. Documentation is [here](http://kubernetes.io/docs/admin/multiple-schedulers.md), design doc is [here](docs/proposals/multiple-schedulers.md).
- * More expressive node affinity syntax, and support for “soft” node affinity.
-Node selectors (to constrain pods to schedule on a subset of nodes) now support
-the operators {In, NotIn, Exists, DoesNotExist, Gt, Lt
} instead of just conjunction of exact match on node label values. In
-addition, we’ve introduced a new “soft” kind of node selector that is just a
-hint to the scheduler; the scheduler will try to satisfy these requests but it
-does not guarantee they will be satisfied. Both the “hard” and “soft” variants
-of node affinity use the new syntax. Documentation is [here](http://kubernetes.io/docs/user-guide/node-selection/) (see section “Alpha feature in Kubernetes v1.2: Node Affinity“). Design doc is [here](https://github.com/kubernetes/kubernetes/blob/release-1.2/docs/design/nodeaffinity.md).
- * A pod can specify its own Hostname and Subdomain via annotations (pod.beta.kubernetes.io/hostname, pod.beta.kubernetes.io/subdomain)
. If the Subdomain matches the name of a [headless service](http://kubernetes.io/docs/user-guide/services/#headless-services) in the same namespace, a DNS A record is also created for the pod’s FQDN. More
-details can be found in the [DNS README](https://github.com/kubernetes/kubernetes/blob/release-1.2/cluster/saltbase/salt/kube-dns/README.md#a-records-and-hostname-based-on-pod-annotations---a-beta-feature-in-kubernetes-v12). Changes were introduced in PR [#20688](https://github.com/kubernetes/kubernetes/pull/20688).
- * New SchedulerExtender enables users to implement custom
-out-of-(the-scheduler)-process scheduling predicates and priority functions,
-for example to schedule pods based on resources that are not directly managed
-by Kubernetes. Changes were introduced in PR [#13580](https://github.com/kubernetes/kubernetes/pull/13580). Example configuration and documentation is available [here](docs/design/scheduler_extender.md). This is an alpha feature and may not be supported in its current form at beta
-or GA.
- * New Flex Volume Plugin enables users to use out-of-process volume plugins that
-are installed to “/usr/libexec/kubernetes/kubelet-plugins/volume/exec/” on
-every node, instead of being compiled into the Kubernetes binary. See [example](examples/volumes/flexvolume/README.md) for details.
- * vendor volumes into a pod. It expects vendor drivers are installed in the
-volume plugin path on each kubelet node. This is an alpha feature and may
-change in future.
- * Kubelet exposes a new Alpha metrics API - /stats/summary in a user friendly format with reduced system overhead. The measurement is done in PR [#22542](https://github.com/kubernetes/kubernetes/pull/22542).
-
-### Action required
-
- * Docker v1.9.1 is officially recommended. Docker v1.8.3 and Docker v1.10 are
-supported. If you are using an older release of Docker, please upgrade. Known
-issues with Docker 1.9.1 can be found below.
- * CPU hardcapping will be enabled by default for containers with CPU limit set,
-if supported by the kernel. You should either adjust your CPU limit, or set CPU
-request only, if you want to avoid hardcapping. If the kernel does not support
-CPU Quota, NodeStatus will contain a warning indicating that CPU Limits cannot
-be enforced.
- * The following applies only if you use the Go language client (/pkg/client/unversioned
) to create Job by defining Go variables of type "k8s.io/kubernetes/pkg/apis/extensions".Job
). We think this is not common, so if you are not sure what this means, you probably aren't doing this. If
-you do this, then, at the time you re-vendor the "k8s.io/kubernetes/"
code, you will need to set job.Spec.ManualSelector = true
, or else set job.Spec.Selector = nil.
Otherwise, the jobs you create may be rejected. See [Specifying your own pod selector](http://kubernetes.io/docs/user-guide/jobs/#specifying-your-own-pod-selector).
- * Deployment was Alpha in 1.1 (though it had apiVersion extensions/v1beta1) and
-was disabled by default. Due to some non-backward-compatible API changes, any
-Deployment objects you created in 1.1 won’t work with in the 1.2 release.
- * Before upgrading to 1.2, delete all Deployment alpha-version resources, including the Replication Controllers and Pods the Deployment manages. Then
-create Deployment Beta resources after upgrading to 1.2. Not deleting the
-Deployment objects may cause the deployment controller to mistakenly match
-other pods and delete them, due to the selector API change.
- * Client (kubectl) and server versions must match (both 1.1 or both 1.2) for any
-Deployment-related operations.
- * Behavior change:
- * Deployment creates ReplicaSets instead of ReplicationControllers.
- * Scale subresource now has a new targetSelector
field in its status. This field supports the new set-based selectors supported
-by Deployments, but in a serialized format.
- * Spec change:
- * Deployment’s [selector](http://kubernetes.io/docs/user-guide/labels/#label-selectors) is now more general (supports set-based selector; it only supported
-equality-based selector in 1.1).
- * .spec.uniqueLabelKey is removed -- users can’t customize unique label key --
-and its default value is changed from
-“deployment.kubernetes.io/podTemplateHash” to “pod-template-hash”.
- * .spec.strategy.rollingUpdate.minReadySeconds is moved to .spec.minReadySeconds
- * DaemonSet was Alpha in 1.1 (though it had apiVersion extensions/v1beta1) and
-was disabled by default. Due to some non-backward-compatible API changes, any
-DaemonSet objects you created in 1.1 won’t work with in the 1.2 release.
- * Before upgrading to 1.2, delete all DaemonSet alpha-version resources. If you do not want to disrupt the pods, use kubectl delete daemonset curl -H "Content-Type: application/json" -XPOST -d
-'{"apiVersion":"v1","kind":"Namespace","metadata":{"name":"kube-system"}}' "[http://127.0.0.1:8080/api/v1/namespaces](http://127.0.0.1:8080/api/v1/namespaces)"
- * The version of InfluxDB is bumped from 0.8 to 0.9 which means storage schema
-change. More details [here](https://docs.influxdata.com/influxdb/v0.9/administration/upgrading/).
- * We have renamed “minions” to “nodes”. If you were specifying NUM\_MINIONS or
-MINION\_SIZE to kube-up, you should now specify NUM\_NODES or NODE\_SIZE.
-
-### Known Issues
-
- * Paused deployments can't be resized and don't clean up old ReplicaSets.
- * Minimum memory limit is 4MB. This is a docker limitation
- * Minimum CPU limits is 10m. This is a Linux Kernel limitation
- * “kubectl rollout undo” (i.e. rollback) will hang on paused deployments, because
-paused deployments can’t be rolled back (this is expected), and the command
-waits for rollback events to return the result. Users should use “kubectl
-rollout resume” to resume a deployment before rolling back.
- * “kubectl edit FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin. This is an alpha feature and may change in future.
+FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin.
flexVolume |
-FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin. This is an alpha feature and may change in future. |
+FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin. |
false |
@@ -3804,7 +3804,7 @@ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
dnsPolicy |
-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. |
+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. |
false |
string |
@@ -3937,7 +3937,7 @@ | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
dnsConfig |
-Specifies the DNS parameters of a pod. Parameters specified here will be merged to the generated DNS configuration based on DNSPolicy. |
+Specifies the DNS parameters of a pod. Parameters specified here will be merged to the generated DNS configuration based on DNSPolicy. This is an alpha feature introduced in v1.9 and CustomPodDNS feature gate must be enabled to use it. |
false |
diff --git a/vendor/k8s.io/kubernetes/docs/api-reference/apps/v1beta1/definitions.html b/vendor/k8s.io/kubernetes/docs/api-reference/apps/v1beta1/definitions.html index f90176654d7f..8bf4a106ec9d 100755 --- a/vendor/k8s.io/kubernetes/docs/api-reference/apps/v1beta1/definitions.html +++ b/vendor/k8s.io/kubernetes/docs/api-reference/apps/v1beta1/definitions.html @@ -2726,7 +2726,7 @@ |
flexVolume |
-FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin. This is an alpha feature and may change in future. |
+FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin. |
false |
@@ -3857,7 +3857,7 @@ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
dnsPolicy |
-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. |
+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. |
false |
string |
@@ -3990,7 +3990,7 @@ | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
dnsConfig |
-Specifies the DNS parameters of a pod. Parameters specified here will be merged to the generated DNS configuration based on DNSPolicy. |
+Specifies the DNS parameters of a pod. Parameters specified here will be merged to the generated DNS configuration based on DNSPolicy. This is an alpha feature introduced in v1.9 and CustomPodDNS feature gate must be enabled to use it. |
false |
diff --git a/vendor/k8s.io/kubernetes/docs/api-reference/apps/v1beta2/definitions.html b/vendor/k8s.io/kubernetes/docs/api-reference/apps/v1beta2/definitions.html index 157fa46b3297..0eb7eae50bae 100755 --- a/vendor/k8s.io/kubernetes/docs/api-reference/apps/v1beta2/definitions.html +++ b/vendor/k8s.io/kubernetes/docs/api-reference/apps/v1beta2/definitions.html @@ -1013,7 +1013,7 @@ |
flexVolume |
-FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin. This is an alpha feature and may change in future. |
+FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin. |
false |
@@ -4473,7 +4473,7 @@ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
dnsPolicy |
-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. |
+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. |
false |
string |
@@ -4606,7 +4606,7 @@ | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
dnsConfig |
-Specifies the DNS parameters of a pod. Parameters specified here will be merged to the generated DNS configuration based on DNSPolicy. |
+Specifies the DNS parameters of a pod. Parameters specified here will be merged to the generated DNS configuration based on DNSPolicy. This is an alpha feature introduced in v1.9 and CustomPodDNS feature gate must be enabled to use it. |
false |
@@ -5207,7 +5207,7 @@ |
flexVolume |
-FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin. This is an alpha feature and may change in future. |
+FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin. |
false |
@@ -3137,7 +3137,7 @@ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
dnsPolicy |
-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. |
+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. |
false |
string |
@@ -3270,7 +3270,7 @@ | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
dnsConfig |
-Specifies the DNS parameters of a pod. Parameters specified here will be merged to the generated DNS configuration based on DNSPolicy. |
+Specifies the DNS parameters of a pod. Parameters specified here will be merged to the generated DNS configuration based on DNSPolicy. This is an alpha feature introduced in v1.9 and CustomPodDNS feature gate must be enabled to use it. |
false |
diff --git a/vendor/k8s.io/kubernetes/docs/api-reference/batch/v1beta1/definitions.html b/vendor/k8s.io/kubernetes/docs/api-reference/batch/v1beta1/definitions.html index 798d8d6b21ee..1e84af1e5ec5 100755 --- a/vendor/k8s.io/kubernetes/docs/api-reference/batch/v1beta1/definitions.html +++ b/vendor/k8s.io/kubernetes/docs/api-reference/batch/v1beta1/definitions.html @@ -2061,7 +2061,7 @@ |
flexVolume |
-FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin. This is an alpha feature and may change in future. |
+FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin. |
false |
@@ -3171,7 +3171,7 @@ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
dnsPolicy |
-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. |
+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. |
false |
string |
@@ -3304,7 +3304,7 @@ | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
dnsConfig |
-Specifies the DNS parameters of a pod. Parameters specified here will be merged to the generated DNS configuration based on DNSPolicy. |
+Specifies the DNS parameters of a pod. Parameters specified here will be merged to the generated DNS configuration based on DNSPolicy. This is an alpha feature introduced in v1.9 and CustomPodDNS feature gate must be enabled to use it. |
false |
diff --git a/vendor/k8s.io/kubernetes/docs/api-reference/batch/v2alpha1/definitions.html b/vendor/k8s.io/kubernetes/docs/api-reference/batch/v2alpha1/definitions.html index d319cb99dd05..12662acce979 100755 --- a/vendor/k8s.io/kubernetes/docs/api-reference/batch/v2alpha1/definitions.html +++ b/vendor/k8s.io/kubernetes/docs/api-reference/batch/v2alpha1/definitions.html @@ -2020,7 +2020,7 @@ |
flexVolume |
-FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin. This is an alpha feature and may change in future. |
+FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin. |
false |
@@ -3144,7 +3144,7 @@ | |||||||||||||||||||||||||||||||||||||||||||||||||
dnsPolicy |
-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. |
+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. |
false |
string |
@@ -3277,7 +3277,7 @@ | ||||||||||||||||||||||||||||||||||||||||||||||||
dnsConfig |
-Specifies the DNS parameters of a pod. Parameters specified here will be merged to the generated DNS configuration based on DNSPolicy. |
+Specifies the DNS parameters of a pod. Parameters specified here will be merged to the generated DNS configuration based on DNSPolicy. This is an alpha feature introduced in v1.9 and CustomPodDNS feature gate must be enabled to use it. |
false |
diff --git a/vendor/k8s.io/kubernetes/docs/api-reference/extensions/v1beta1/definitions.html b/vendor/k8s.io/kubernetes/docs/api-reference/extensions/v1beta1/definitions.html index 2776574ca6d1..bd302b0eb89f 100755 --- a/vendor/k8s.io/kubernetes/docs/api-reference/extensions/v1beta1/definitions.html +++ b/vendor/k8s.io/kubernetes/docs/api-reference/extensions/v1beta1/definitions.html @@ -1395,7 +1395,7 @@ |
flexVolume |
-FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin. This is an alpha feature and may change in future. |
+FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin. |
false |
@@ -4496,7 +4496,7 @@ | |||||||||||||||||||||||||||||||
dnsPolicy |
-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. |
+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. |
false |
string |
@@ -4629,7 +4629,7 @@ | ||||||||||||||||||||||||||||||
dnsConfig |
-Specifies the DNS parameters of a pod. Parameters specified here will be merged to the generated DNS configuration based on DNSPolicy. |
+Specifies the DNS parameters of a pod. Parameters specified here will be merged to the generated DNS configuration based on DNSPolicy. This is an alpha feature introduced in v1.9 and CustomPodDNS feature gate must be enabled to use it. |
false |
@@ -5329,7 +5329,7 @@ |
flexVolume |
-FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin. This is an alpha feature and may change in future. |
+FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin. |
false |
diff --git a/vendor/k8s.io/kubernetes/docs/api-reference/v1/definitions.html b/vendor/k8s.io/kubernetes/docs/api-reference/v1/definitions.html index 08c3b84c8ce2..b169977ecee7 100755 --- a/vendor/k8s.io/kubernetes/docs/api-reference/v1/definitions.html +++ b/vendor/k8s.io/kubernetes/docs/api-reference/v1/definitions.html @@ -2244,7 +2244,7 @@ |
flexVolume |
-FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin. This is an alpha feature and may change in future. |
+FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin. |
false |
@@ -8380,7 +8380,7 @@ | |
flexVolume |
-FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin. This is an alpha feature and may change in future. |
+FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin. |
false |
@@ -9082,7 +9082,7 @@ | |
dnsPolicy |
-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. |
+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. |
false |
string |
@@ -9215,7 +9215,7 @@ |
dnsConfig |
-Specifies the DNS parameters of a pod. Parameters specified here will be merged to the generated DNS configuration based on DNSPolicy. |
+Specifies the DNS parameters of a pod. Parameters specified here will be merged to the generated DNS configuration based on DNSPolicy. This is an alpha feature introduced in v1.9 and CustomPodDNS feature gate must be enabled to use it. |
false |
diff --git a/vendor/k8s.io/kubernetes/docs/man/man1/cloud-controller-manager.1 b/vendor/k8s.io/kubernetes/docs/man/man1/cloud-controller-manager.1 index dfecfb90c7a8..b6fd7a0f9896 100644 --- a/vendor/k8s.io/kubernetes/docs/man/man1/cloud-controller-manager.1 +++ b/vendor/k8s.io/kubernetes/docs/man/man1/cloud-controller-manager.1 @@ -1,193 +1,3 @@ -.TH "KUBERNETES" "1" " kubernetes User Manuals" "Eric Paris" "Jan 2015" "" - - -.SH NAME -.PP -cloud\-controller\-manager \- - - -.SH SYNOPSIS -.PP -\fBcloud\-controller\-manager\fP [OPTIONS] - - -.SH DESCRIPTION -.PP -The Cloud controller manager is a daemon that embeds -the cloud specific control loops shipped with Kubernetes. - - -.SH OPTIONS -.PP -\fB\-\-address\fP=0.0.0.0 - The IP address to serve on (set to 0.0.0.0 for all interfaces). - -.PP -\fB\-\-allocate\-node\-cidrs\fP=false - Should CIDRs for Pods be allocated and set on the cloud provider. - -.PP -\fB\-\-allow\-untagged\-cloud\fP=false - Allow the cluster to run without the cluster\-id on cloud instances. This is a legacy mode of operation and a cluster\-id will be required in the future. - -.PP -\fB\-\-azure\-container\-registry\-config\fP="" - Path to the file container Azure container registry configuration information. - -.PP -\fB\-\-cloud\-config\fP="" - The path to the cloud provider configuration file. Empty string for no configuration file. - -.PP -\fB\-\-cloud\-provider\fP="" - The provider of cloud services. Cannot be empty. - -.PP -\fB\-\-cluster\-cidr\fP="" - CIDR Range for Pods in cluster. - -.PP -\fB\-\-cluster\-name\fP="kubernetes" - The instance prefix for the cluster. - -.PP -\fB\-\-concurrent\-service\-syncs\fP=1 - The number of services that are allowed to sync concurrently. Larger number = more responsive service management, but more CPU (and network) load - -.PP -\fB\-\-configure\-cloud\-routes\fP=true - Should CIDRs allocated by allocate\-node\-cidrs be configured on the cloud provider. - -.PP -\fB\-\-contention\-profiling\fP=false - Enable lock contention profiling, if profiling is enabled. - -.PP -\fB\-\-controller\-start\-interval\fP=0s - Interval between starting controller managers. - -.PP -\fB\-\-feature\-gates\fP= - A set of key=value pairs that describe feature gates for alpha/experimental features. Options are: -APIListChunking=true|false (BETA \- default=true) -APIResponseCompression=true|false (ALPHA \- default=false) -Accelerators=true|false (ALPHA \- default=false) -AdvancedAuditing=true|false (BETA \- default=true) -AllAlpha=true|false (ALPHA \- default=false) -AllowExtTrafficLocalEndpoints=true|false (default=true) -AppArmor=true|false (BETA \- default=true) -BlockVolume=true|false (ALPHA \- default=false) -CPUManager=true|false (ALPHA \- default=false) -CSIPersistentVolume=true|false (ALPHA \- default=false) -CustomPodDNS=true|false (ALPHA \- default=false) -CustomResourceValidation=true|false (BETA \- default=true) -DebugContainers=true|false (ALPHA \- default=false) -DevicePlugins=true|false (ALPHA \- default=false) -DynamicKubeletConfig=true|false (ALPHA \- default=false) -EnableEquivalenceClassCache=true|false (ALPHA \- default=false) -ExpandPersistentVolumes=true|false (ALPHA \- default=false) -ExperimentalCriticalPodAnnotation=true|false (ALPHA \- default=false) -ExperimentalHostUserNamespaceDefaulting=true|false (BETA \- default=false) -HugePages=true|false (ALPHA \- default=false) -Initializers=true|false (ALPHA \- default=false) -KubeletConfigFile=true|false (ALPHA \- default=false) -LocalStorageCapacityIsolation=true|false (ALPHA \- default=false) -MountContainers=true|false (ALPHA \- default=false) -MountPropagation=true|false (ALPHA \- default=false) -PVCProtection=true|false (ALPHA \- default=false) -PersistentLocalVolumes=true|false (ALPHA \- default=false) -PodPriority=true|false (ALPHA \- default=false) -ResourceLimitsPriorityFunction=true|false (ALPHA \- default=false) -RotateKubeletClientCertificate=true|false (BETA \- default=true) -RotateKubeletServerCertificate=true|false (ALPHA \- default=false) -ServiceNodeExclusion=true|false (ALPHA \- default=false) -StreamingProxyRedirects=true|false (BETA \- default=true) -SupportIPVSProxyMode=true|false (ALPHA \- default=false) -TaintBasedEvictions=true|false (ALPHA \- default=false) -TaintNodesByCondition=true|false (ALPHA \- default=false) -VolumeScheduling=true|false (ALPHA \- default=false) - -.PP -\fB\-\-google\-json\-key\fP="" - The Google Cloud Platform Service Account JSON Key to use for authentication. - -.PP -\fB\-\-kube\-api\-burst\fP=30 - Burst to use while talking with kubernetes apiserver. - -.PP -\fB\-\-kube\-api\-content\-type\fP="application/vnd.kubernetes.protobuf" - Content type of requests sent to apiserver. - -.PP -\fB\-\-kube\-api\-qps\fP=20 - QPS to use while talking with kubernetes apiserver. - -.PP -\fB\-\-kubeconfig\fP="" - Path to kubeconfig file with authorization and master location information. - -.PP -\fB\-\-leader\-elect\fP=true - Start a leader election client and gain leadership before executing the main loop. Enable this when running replicated components for high availability. - -.PP -\fB\-\-leader\-elect\-lease\-duration\fP=15s - The duration that non\-leader candidates will wait after observing a leadership renewal until attempting to acquire leadership of a led but unrenewed leader slot. This is effectively the maximum duration that a leader can be stopped before it is replaced by another candidate. This is only applicable if leader election is enabled. - -.PP -\fB\-\-leader\-elect\-renew\-deadline\fP=10s - The interval between attempts by the acting master to renew a leadership slot before it stops leading. This must be less than or equal to the lease duration. This is only applicable if leader election is enabled. - -.PP -\fB\-\-leader\-elect\-resource\-lock\fP="endpoints" - The type of resource object that is used for locking during leader election. Supported options are \fB\fCendpoints\fR (default) and \fB\fCconfigmaps\fR. - -.PP -\fB\-\-leader\-elect\-retry\-period\fP=2s - The duration the clients should wait between attempting acquisition and renewal of a leadership. This is only applicable if leader election is enabled. - -.PP -\fB\-\-master\fP="" - The address of the Kubernetes API server (overrides any value in kubeconfig). - -.PP -\fB\-\-min\-resync\-period\fP=12h0m0s - The resync period in reflectors will be random between MinResyncPeriod and 2*MinResyncPeriod. - -.PP -\fB\-\-node\-monitor\-period\fP=5s - The period for syncing NodeStatus in NodeController. - -.PP -\fB\-\-node\-status\-update\-frequency\fP=5m0s - Specifies how often the controller updates nodes' status. - -.PP -\fB\-\-port\fP=10253 - The port that the cloud\-controller\-manager's http service runs on. - -.PP -\fB\-\-profiling\fP=true - Enable profiling via web interface host:port/debug/pprof/. - -.PP -\fB\-\-route\-reconciliation\-period\fP=10s - The period for reconciling routes created for Nodes by cloud provider. - -.PP -\fB\-\-service\-account\-private\-key\-file\fP="" - Filename containing a PEM\-encoded private RSA or ECDSA key used to sign service account tokens. - -.PP -\fB\-\-use\-service\-account\-credentials\fP=false - If true, use individual service account credentials for each controller. - -.PP -\fB\-\-version\fP=false - Print version information and quit - - -.SH HISTORY -.PP -January 2015, Originally compiled by Eric Paris (eparis at redhat dot com) based on the kubernetes source material, but hopefully they have been automatically generated since! +This file is autogenerated, but we've stopped checking such files into the +repository to reduce the need for rebases. Please run hack/generate-docs.sh to +populate this file. diff --git a/vendor/k8s.io/kubernetes/docs/man/man1/kube-apiserver.1 b/vendor/k8s.io/kubernetes/docs/man/man1/kube-apiserver.1 index 39dde5c796fc..b6fd7a0f9896 100644 --- a/vendor/k8s.io/kubernetes/docs/man/man1/kube-apiserver.1 +++ b/vendor/k8s.io/kubernetes/docs/man/man1/kube-apiserver.1 @@ -1,512 +1,3 @@ -.TH "KUBERNETES" "1" " kubernetes User Manuals" "Eric Paris" "Jan 2015" "" - - -.SH NAME -.PP -kube\-apiserver \- - - -.SH SYNOPSIS -.PP -\fBkube\-apiserver\fP [OPTIONS] - - -.SH DESCRIPTION -.PP -The Kubernetes API server validates and configures data -for the api objects which include pods, services, replicationcontrollers, and -others. The API Server services REST operations and provides the frontend to the -cluster's shared state through which all other components interact. - - -.SH OPTIONS -.PP -\fB\-\-address\fP=127.0.0.1 - DEPRECATED: see \-\-insecure\-bind\-address instead. - -.PP -\fB\-\-admission\-control\fP=[AlwaysAdmit] - Admission is divided into two phases. In the first phase, only mutating admission plugins run. In the second phase, only validating admission plugins run. The names in the below list may represent a validating plugin, a mutating plugin, or both. Within each phase, the plugins will run in the order in which they are passed to this flag. Comma\-delimited list of: AlwaysAdmit, AlwaysDeny, AlwaysPullImages, DefaultStorageClass, DefaultTolerationSeconds, DenyEscalatingExec, DenyExecOnPrivileged, EventRateLimit, ExtendedResourceToleration, ImagePolicyWebhook, InitialResources, Initializers, LimitPodHardAntiAffinityTopology, LimitRanger, MutatingAdmissionWebhook, NamespaceAutoProvision, NamespaceExists, NamespaceLifecycle, NodeRestriction, OwnerReferencesPermissionEnforcement, PVCProtection, PersistentVolumeClaimResize, PersistentVolumeLabel, PodNodeSelector, PodPreset, PodSecurityPolicy, PodTolerationRestriction, Priority, ResourceQuota, SecurityContextDeny, ServiceAccount, ValidatingAdmissionWebhook. - -.PP -\fB\-\-admission\-control\-config\-file\fP="" - File with admission control configuration. - -.PP -\fB\-\-advertise\-address\fP= |