From 9e6d670b12708fba04696f21a486f4507ec8b38b Mon Sep 17 00:00:00 2001 From: Mengqi Yu Date: Wed, 27 Sep 2017 12:02:55 -0700 Subject: [PATCH] update imported docs (#5656) --- _data/overrides.yml | 1 + docs/admin/cloud-controller-manager.md | 83 +++ docs/admin/federation-apiserver.md | 34 +- docs/admin/federation-controller-manager.md | 10 +- docs/admin/kube-apiserver.md | 41 +- docs/admin/kube-controller-manager.md | 31 +- docs/admin/kube-proxy.md | 39 +- docs/admin/kube-scheduler.md | 24 +- docs/admin/kubelet.md | 272 +++---- .../extensions/v1beta1/definitions.html | 359 +++++---- .../extensions/v1beta1/operations.html | 676 +++++++++++++---- .../federation/v1beta1/definitions.html | 65 +- .../federation/v1beta1/operations.html | 110 ++- docs/reference/federation/index.md | 8 +- docs/reference/federation/v1/definitions.html | 175 ++++- docs/reference/federation/v1/operations.html | 697 +++++++++++++++--- update-imported-docs.sh | 6 +- 17 files changed, 1969 insertions(+), 662 deletions(-) create mode 100644 docs/admin/cloud-controller-manager.md diff --git a/_data/overrides.yml b/_data/overrides.yml index bb4b91c707543..00eb2db179e6a 100644 --- a/_data/overrides.yml +++ b/_data/overrides.yml @@ -1,4 +1,5 @@ overrides: +- path: docs/admin/cloud-controller-manager.md - path: docs/admin/federation-apiserver.md - path: docs/admin/federation-controller-manager.md - path: docs/admin/kube-apiserver.md diff --git a/docs/admin/cloud-controller-manager.md b/docs/admin/cloud-controller-manager.md new file mode 100644 index 0000000000000..798c93977761b --- /dev/null +++ b/docs/admin/cloud-controller-manager.md @@ -0,0 +1,83 @@ +--- +title: cloud-controller-manager +notitle: true +--- +## cloud-controller-manager + + + +### Synopsis + + +The Cloud controller manager is a daemon that embeds +the cloud specific control loops shipped with Kubernetes. + +``` +cloud-controller-manager +``` + +### Options + +``` + --address ip The IP address to serve on (set to 0.0.0.0 for all interfaces). (default 0.0.0.0) + --allocate-node-cidrs Should CIDRs for Pods be allocated and set on the cloud provider. + --azure-container-registry-config string Path to the file container Azure container registry configuration information. + --cloud-config string The path to the cloud provider configuration file. Empty string for no configuration file. + --cloud-provider string The provider of cloud services. Cannot be empty. + --cluster-cidr string CIDR Range for Pods in cluster. + --cluster-name string The instance prefix for the cluster. (default "kubernetes") + --configure-cloud-routes Should CIDRs allocated by allocate-node-cidrs be configured on the cloud provider. (default true) + --contention-profiling Enable lock contention profiling, if profiling is enabled. + --controller-start-interval duration Interval between starting controller managers. + --feature-gates mapStringBool A set of key=value pairs that describe feature gates for alpha/experimental features. Options are: +APIListChunking=true|false (ALPHA - default=false) +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) +CPUManager=true|false (ALPHA - default=false) +CustomResourceValidation=true|false (ALPHA - default=false) +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) +MountPropagation=true|false (ALPHA - default=false) +PersistentLocalVolumes=true|false (ALPHA - default=false) +PodPriority=true|false (ALPHA - default=false) +RotateKubeletClientCertificate=true|false (BETA - default=true) +RotateKubeletServerCertificate=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) + --google-json-key string The Google Cloud Platform Service Account JSON Key to use for authentication. + --kube-api-burst int32 Burst to use while talking with kubernetes apiserver. (default 30) + --kube-api-content-type string Content type of requests sent to apiserver. (default "application/vnd.kubernetes.protobuf") + --kube-api-qps float32 QPS to use while talking with kubernetes apiserver. (default 20) + --kubeconfig string Path to kubeconfig file with authorization and master location information. + --leader-elect Start a leader election client and gain leadership before executing the main loop. Enable this when running replicated components for high availability. (default true) + --leader-elect-lease-duration duration 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. (default 15s) + --leader-elect-renew-deadline duration 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. (default 10s) + --leader-elect-resource-lock endpoints The type of resource object that is used for locking during leader election. Supported options are endpoints (default) and `configmap`. (default "endpoints") + --leader-elect-retry-period duration The duration the clients should wait between attempting acquisition and renewal of a leadership. This is only applicable if leader election is enabled. (default 2s) + --master string The address of the Kubernetes API server (overrides any value in kubeconfig). + --min-resync-period duration The resync period in reflectors will be random between MinResyncPeriod and 2*MinResyncPeriod. (default 12h0m0s) + --node-monitor-period duration The period for syncing NodeStatus in NodeController. (default 5s) + --node-status-update-frequency duration Specifies how often the controller updates nodes' status. (default 5m0s) + --port int32 The port that the cloud-controller-manager's http service runs on. (default 10253) + --profiling Enable profiling via web interface host:port/debug/pprof/. (default true) + --route-reconciliation-period duration The period for reconciling routes created for Nodes by cloud provider. + --use-service-account-credentials If true, use individual service account credentials for each controller. + --version version[=true] Print version information and quit +``` + +###### Auto generated by spf13/cobra on 27-Sep-2017 diff --git a/docs/admin/federation-apiserver.md b/docs/admin/federation-apiserver.md index e834005250e0e..bebb078768c60 100644 --- a/docs/admin/federation-apiserver.md +++ b/docs/admin/federation-apiserver.md @@ -25,6 +25,7 @@ federation-apiserver --admission-control-config-file string File with admission control configuration. --advertise-address ip The IP address on which to advertise the apiserver to members of the cluster. This address must be reachable by the rest of the cluster. If blank, the --bind-address will be used. If --bind-address is unspecified, the host's default interface will be used. --anonymous-auth Enables anonymous requests to the secure port of the API server. Requests that are not rejected by another authentication method are treated as anonymous requests. Anonymous requests have a username of system:anonymous, and a group name of system:unauthenticated. (default true) + --audit-log-format string Format of saved audits. "legacy" indicates 1-line text format for each event. "json" indicates structured json format. Requires the 'AdvancedAuditing' feature gate. Known formats are legacy,json. (default "json") --audit-log-maxage int The maximum number of days to retain old audit log files based on the timestamp encoded in their filename. --audit-log-maxbackup int The maximum number of old audit log files to retain. --audit-log-maxsize int The maximum size in megabytes of the audit log file before it gets rotated. @@ -47,8 +48,10 @@ federation-apiserver --cloud-provider string The provider for cloud services. Empty string for no provider. --contention-profiling Enable lock contention profiling, if profiling is enabled --cors-allowed-origins stringSlice List of allowed origins for CORS, comma separated. An allowed origin can be a regular expression to support subdomain matching. If this list is empty CORS will not be enabled. + --default-watch-cache-size int Default watch cache size. If zero, watch cache will be disabled for resources that do not have a default watch size set. (default 100) --delete-collection-workers int Number of workers spawned for DeleteCollection call. These are used to speed up namespace cleanup. (default 1) --deserialization-cache-size int Number of deserialized json objects to cache in memory. + --enable-bootstrap-token-auth Enable to allow secrets of type 'bootstrap.kubernetes.io/token' in the 'kube-system' namespace to be used for TLS bootstrapping authentication. --enable-garbage-collector Enables the generic garbage collector. MUST be synced with the corresponding flag of the kube-controller-manager. (default true) --enable-swagger-ui Enables swagger ui on the apiserver at /swagger-ui --etcd-cafile string SSL Certificate Authority file used to secure etcd communication. @@ -59,31 +62,43 @@ federation-apiserver --etcd-servers stringSlice List of etcd servers to connect with (scheme://ip:port), comma separated. --etcd-servers-overrides stringSlice Per-resource etcd servers overrides, comma separated. The individual override format: group/resource#servers, where servers are http://ip:port, semicolon separated. --event-ttl duration Amount of time to retain events. (default 1h0m0s) - --experimental-bootstrap-token-auth Enable to allow secrets of type 'bootstrap.kubernetes.io/token' in the 'kube-system' namespace to be used for TLS bootstrapping authentication. --experimental-encryption-provider-config string The file containing configuration for encryption providers to be used for storing secrets in etcd --experimental-keystone-ca-file string If set, the Keystone server's certificate will be verified by one of the authorities in the experimental-keystone-ca-file, otherwise the host's root CA set will be used. --experimental-keystone-url string If passed, activates the keystone authentication plugin. --external-hostname string The hostname to use when generating externalized URLs for this master (e.g. Swagger API Docs). --feature-gates mapStringBool A set of key=value pairs that describe feature gates for alpha/experimental features. Options are: +APIListChunking=true|false (ALPHA - default=false) +APIResponseCompression=true|false (ALPHA - default=false) Accelerators=true|false (ALPHA - default=false) -AdvancedAuditing=true|false (ALPHA - default=false) -AffinityInAnnotations=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) +CPUManager=true|false (ALPHA - default=false) +CustomResourceValidation=true|false (ALPHA - default=false) +DebugContainers=true|false (ALPHA - default=false) +DevicePlugins=true|false (ALPHA - default=false) DynamicKubeletConfig=true|false (ALPHA - default=false) -DynamicVolumeProvisioning=true|false (ALPHA - default=true) +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) +MountPropagation=true|false (ALPHA - default=false) PersistentLocalVolumes=true|false (ALPHA - default=false) -RotateKubeletClientCertificate=true|false (ALPHA - default=false) +PodPriority=true|false (ALPHA - default=false) +RotateKubeletClientCertificate=true|false (BETA - default=true) RotateKubeletServerCertificate=true|false (ALPHA - default=false) StreamingProxyRedirects=true|false (BETA - default=true) +SupportIPVSProxyMode=true|false (ALPHA - default=false) TaintBasedEvictions=true|false (ALPHA - default=false) - --insecure-allow-any-token username/group1,group2 If set, your server will be INSECURE. Any token will be allowed and user information will be parsed from the token as username/group1,group2 +TaintNodesByCondition=true|false (ALPHA - default=false) --insecure-bind-address ip The IP address on which to serve the --insecure-port (set to 0.0.0.0 for all interfaces). (default 127.0.0.1) --insecure-port int The port on which to serve unsecured, unauthenticated access. It is assumed that firewall rules are set up such that this port is not reachable from outside of the cluster and that port 443 on the cluster's public address is proxied to this port. This is performed by nginx in the default setup. (default 8080) + --log-flush-frequency duration Maximum number of seconds between log flushes (default 5s) --master-service-namespace string DEPRECATED: the namespace from which the kubernetes master services should be injected into pods. (default "default") --max-mutating-requests-inflight int The maximum number of mutating requests in flight at a given time. When the server exceeds this, it rejects requests. Zero for no limit. (default 200) --max-requests-inflight int The maximum number of non-mutating requests in flight at a given time. When the server exceeds this, it rejects requests. Zero for no limit. (default 400) @@ -91,9 +106,12 @@ TaintBasedEvictions=true|false (ALPHA - default=false) --oidc-ca-file string If set, the OpenID server's certificate will be verified by one of the authorities in the oidc-ca-file, otherwise the host's root CA set will be used. --oidc-client-id string The client ID for the OpenID Connect client, must be set if oidc-issuer-url is set. --oidc-groups-claim string If provided, the name of a custom OpenID Connect claim for specifying user groups. The claim value is expected to be a string or array of strings. This flag is experimental, please see the authentication documentation for further details. + --oidc-groups-prefix string If provided, all groups will be prefixed with this value to prevent conflicts with other authentication strategies. --oidc-issuer-url string The URL of the OpenID issuer, only HTTPS scheme will be accepted. If set, it will be used to verify the OIDC JSON Web Token (JWT). --oidc-username-claim string The OpenID claim to use as the user name. Note that claims other than the default ('sub') is not guaranteed to be unique and immutable. This flag is experimental, please see the authentication documentation for further details. (default "sub") + --oidc-username-prefix string If provided, all usernames will be prefixed with this value. If not provided, username claims other than 'email' are prefixed by the issuer URL to avoid clashes. To skip any prefixing, provide the value '-'. --profiling Enable profiling via web interface host:port/debug/pprof/ (default true) + --request-timeout duration An optional field indicating the duration a handler must keep a request open before timing it out. This is the default request timeout for requests but may be overridden by flags such as --min-request-timeout for specific types of requests. (default 1m0s) --requestheader-allowed-names stringSlice List of client certificate common names to allow to provide usernames in headers specified by --requestheader-username-headers. If empty, any client certificate validated by the authorities in --requestheader-client-ca-file is allowed. --requestheader-client-ca-file string Root certificate bundle to use to verify client certificates on incoming requests before trusting usernames in headers specified by --requestheader-username-headers --requestheader-extra-headers-prefix stringSlice List of request header prefixes to inspect. X-Remote-Extra- is suggested. @@ -105,7 +123,7 @@ TaintBasedEvictions=true|false (ALPHA - default=false) --service-account-lookup If true, validate ServiceAccount tokens exist in etcd as part of authentication. (default true) --storage-backend string The storage backend for persistence. Options: 'etcd3' (default), 'etcd2'. --storage-media-type string The media type to use to store objects in storage. Some resources or storage backends may only support a specific media type and will ignore this setting. (default "application/vnd.kubernetes.protobuf") - --storage-versions string The per-group version to store resources in. Specified in the format "group1/version1,group2/version2,...". In the case where objects are moved from one group to the other, you may specify the format "group1=group2/v1beta1,group3/v1beta1,...". You only need to pass the groups you wish to change from the defaults. It defaults to a list of preferred versions of all registered groups, which is derived from the KUBE_API_VERSIONS environment variable. (default "admissionregistration.k8s.io/v1alpha1,apps/v1beta1,authentication.k8s.io/v1,authorization.k8s.io/v1,autoscaling/v1,batch/v1,certificates.k8s.io/v1beta1,componentconfig/v1alpha1,extensions/v1beta1,federation/v1beta1,networking.k8s.io/v1,policy/v1beta1,rbac.authorization.k8s.io/v1beta1,settings.k8s.io/v1alpha1,storage.k8s.io/v1,v1") + --storage-versions string The per-group version to store resources in. Specified in the format "group1/version1,group2/version2,...". In the case where objects are moved from one group to the other, you may specify the format "group1=group2/v1beta1,group3/v1beta1,...". You only need to pass the groups you wish to change from the defaults. It defaults to a list of preferred versions of all registered groups, which is derived from the KUBE_API_VERSIONS environment variable. (default "admissionregistration.k8s.io/v1alpha1,apps/v1beta1,authentication.k8s.io/v1,authorization.k8s.io/v1,autoscaling/v1,batch/v1,certificates.k8s.io/v1beta1,componentconfig/v1alpha1,extensions/v1beta1,federation/v1beta1,networking.k8s.io/v1,policy/v1beta1,rbac.authorization.k8s.io/v1beta1,scheduling.k8s.io/v1alpha1,settings.k8s.io/v1alpha1,storage.k8s.io/v1,v1") --target-ram-mb int Memory limit for apiserver in MB (used to configure sizes of caches, etc.) --tls-ca-file string If set, this certificate authority will used for secure access from Admission Controllers. This must be a valid PEM-encoded CA bundle. Altneratively, the certificate authority can be appended to the certificate provided by --tls-cert-file. --tls-cert-file string File containing the default x509 Certificate for HTTPS. (CA cert, if any, concatenated after server cert). If HTTPS serving is enabled, and --tls-cert-file and --tls-private-key-file are not provided, a self-signed certificate and key are generated for the public address and saved to /var/run/kubernetes. @@ -116,4 +134,4 @@ TaintBasedEvictions=true|false (ALPHA - default=false) --watch-cache-sizes stringSlice List of watch cache sizes for every resource (pods, nodes, etc.), comma separated. The individual override format: resource#size, where size is a number. It takes effect when watch-cache is enabled. ``` -###### Auto generated by spf13/cobra on 11-Jul-2017 +###### Auto generated by spf13/cobra on 27-Sep-2017 diff --git a/docs/admin/federation-controller-manager.md b/docs/admin/federation-controller-manager.md index 53e578661f6fe..41750c11c8050 100644 --- a/docs/admin/federation-controller-manager.md +++ b/docs/admin/federation-controller-manager.md @@ -26,22 +26,26 @@ federation-controller-manager ``` --address ip The IP address to serve on (set to 0.0.0.0 for all interfaces) (default 0.0.0.0) --cluster-monitor-period duration The period for syncing ClusterStatus in ClusterController. (default 40s) + --concurrent-job-syncs int The number of Jobs syncing operations that will be done concurrently. Larger number = faster endpoint updating, but more CPU (and network) load (default 10) --concurrent-replicaset-syncs int The number of ReplicaSets syncing operations that will be done concurrently. Larger number = faster endpoint updating, but more CPU (and network) load (default 10) --concurrent-service-syncs int The number of service syncing operations that will be done concurrently. Larger number = faster endpoint updating, but more CPU (and network) load (default 10) --contention-profiling Enable lock contention profiling, if profiling is enabled --controllers mapStringString A set of key=value pairs that describe controller configuration to enable/disable specific controllers. Key should be the resource name (like services) and value should be true or false. For example: services=false,ingresses=false - --dns-provider string DNS provider. Valid values are: ["aws-route53" "coredns" "google-clouddns"] + --dns-provider string DNS provider. Valid values are: ["google-clouddns" "aws-route53" "coredns"] --dns-provider-config string Path to config file for configuring DNS provider. --federated-api-burst int Burst to use while talking with federation apiserver (default 30) --federated-api-qps float32 QPS to use while talking with federation apiserver (default 20) --federation-name string Federation name. + --federation-only-namespace string Name of the namespace that would be created only in federation control plane. (default "federation-only") + --hpa-scale-forbidden-window duration The time window wrt cluster local hpa lastscale time, during which federated hpa would not move the hpa max/min replicas around (default 2m0s) --kube-api-content-type string ContentType of requests sent to apiserver. Passing application/vnd.kubernetes.protobuf is an experimental feature now. --kubeconfig string Path to kubeconfig file with authorization and master location information. --leader-elect Start a leader election client and gain leadership before executing the main loop. Enable this when running replicated components for high availability. --leader-elect-lease-duration duration 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. (default 15s) --leader-elect-renew-deadline duration 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. (default 10s) - --leader-elect-resource-lock endpoints The type of resource resource object that is used for locking duringleader election. Supported options are endpoints (default) and `configmap`. (default "endpoints") + --leader-elect-resource-lock endpoints The type of resource object that is used for locking during leader election. Supported options are endpoints (default) and `configmap`. (default "endpoints") --leader-elect-retry-period duration The duration the clients should wait between attempting acquisition and renewal of a leadership. This is only applicable if leader election is enabled. (default 2s) + --log-flush-frequency duration Maximum number of seconds between log flushes (default 5s) --master string The address of the federation API server (overrides any value in kubeconfig) --port int The port that the controller-manager's http service runs on (default 10253) --profiling Enable profiling via web interface host:port/debug/pprof/ (default true) @@ -50,4 +54,4 @@ federation-controller-manager --zone-name string Zone name, like example.com. ``` -###### Auto generated by spf13/cobra on 11-Jul-2017 +###### Auto generated by spf13/cobra on 27-Sep-2017 diff --git a/docs/admin/kube-apiserver.md b/docs/admin/kube-apiserver.md index abed8eec9581e..1d658eb5ec26f 100644 --- a/docs/admin/kube-apiserver.md +++ b/docs/admin/kube-apiserver.md @@ -21,12 +21,13 @@ kube-apiserver ### Options ``` - --admission-control stringSlice Ordered list of plug-ins to do admission control of resources into cluster. Comma-delimited list of: NamespaceLifecycle. (default [AlwaysAdmit]) + --admission-control stringSlice Ordered list of plug-ins to do admission control of resources into cluster. Comma-delimited list of: AlwaysAdmit, AlwaysDeny, AlwaysPullImages, DefaultStorageClass, DefaultTolerationSeconds, DenyEscalatingExec, DenyExecOnPrivileged, EventRateLimit, GenericAdmissionWebhook, ImagePolicyWebhook, InitialResources, Initializers, LimitPodHardAntiAffinityTopology, LimitRanger, NamespaceAutoProvision, NamespaceExists, NamespaceLifecycle, NodeRestriction, OwnerReferencesPermissionEnforcement, PersistentVolumeClaimResize, PersistentVolumeLabel, PodNodeSelector, PodPreset, PodSecurityPolicy, PodTolerationRestriction, Priority, ResourceQuota, SecurityContextDeny, ServiceAccount. (default [AlwaysAdmit]) --admission-control-config-file string File with admission control configuration. --advertise-address ip The IP address on which to advertise the apiserver to members of the cluster. This address must be reachable by the rest of the cluster. If blank, the --bind-address will be used. If --bind-address is unspecified, the host's default interface will be used. - --allow-privileged If true, allow privileged containers. + --allow-privileged If true, allow privileged containers. [default=false] --anonymous-auth Enables anonymous requests to the secure port of the API server. Requests that are not rejected by another authentication method are treated as anonymous requests. Anonymous requests have a username of system:anonymous, and a group name of system:unauthenticated. (default true) --apiserver-count int The number of apiservers running in the cluster, must be a positive number. (default 1) + --audit-log-format string Format of saved audits. "legacy" indicates 1-line text format for each event. "json" indicates structured json format. Requires the 'AdvancedAuditing' feature gate. Known formats are legacy,json. (default "json") --audit-log-maxage int The maximum number of days to retain old audit log files based on the timestamp encoded in their filename. --audit-log-maxbackup int The maximum number of old audit log files to retain. --audit-log-maxsize int The maximum size in megabytes of the audit log file before it gets rotated. @@ -50,9 +51,11 @@ kube-apiserver --cloud-provider string The provider for cloud services. Empty string for no provider. --contention-profiling Enable lock contention profiling, if profiling is enabled --cors-allowed-origins stringSlice List of allowed origins for CORS, comma separated. An allowed origin can be a regular expression to support subdomain matching. If this list is empty CORS will not be enabled. + --default-watch-cache-size int Default watch cache size. If zero, watch cache will be disabled for resources that do not have a default watch size set. (default 100) --delete-collection-workers int Number of workers spawned for DeleteCollection call. These are used to speed up namespace cleanup. (default 1) --deserialization-cache-size int Number of deserialized json objects to cache in memory. --enable-aggregator-routing Turns on aggregator routing requests to endoints IP rather than cluster IP. + --enable-bootstrap-token-auth Enable to allow secrets of type 'bootstrap.kubernetes.io/token' in the 'kube-system' namespace to be used for TLS bootstrapping authentication. --enable-garbage-collector Enables the generic garbage collector. MUST be synced with the corresponding flag of the kube-controller-manager. (default true) --enable-logs-handler If true, install a /logs handler for the apiserver logs. (default true) --enable-swagger-ui Enables swagger ui on the apiserver at /swagger-ui @@ -64,30 +67,41 @@ kube-apiserver --etcd-servers stringSlice List of etcd servers to connect with (scheme://ip:port), comma separated. --etcd-servers-overrides stringSlice Per-resource etcd servers overrides, comma separated. The individual override format: group/resource#servers, where servers are http://ip:port, semicolon separated. --event-ttl duration Amount of time to retain events. (default 1h0m0s) - --experimental-bootstrap-token-auth Enable to allow secrets of type 'bootstrap.kubernetes.io/token' in the 'kube-system' namespace to be used for TLS bootstrapping authentication. --experimental-encryption-provider-config string The file containing configuration for encryption providers to be used for storing secrets in etcd --experimental-keystone-ca-file string If set, the Keystone server's certificate will be verified by one of the authorities in the experimental-keystone-ca-file, otherwise the host's root CA set will be used. --experimental-keystone-url string If passed, activates the keystone authentication plugin. --external-hostname string The hostname to use when generating externalized URLs for this master (e.g. Swagger API Docs). --feature-gates mapStringBool A set of key=value pairs that describe feature gates for alpha/experimental features. Options are: +APIListChunking=true|false (ALPHA - default=false) +APIResponseCompression=true|false (ALPHA - default=false) Accelerators=true|false (ALPHA - default=false) -AdvancedAuditing=true|false (ALPHA - default=false) -AffinityInAnnotations=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) +CPUManager=true|false (ALPHA - default=false) +CustomResourceValidation=true|false (ALPHA - default=false) +DebugContainers=true|false (ALPHA - default=false) +DevicePlugins=true|false (ALPHA - default=false) DynamicKubeletConfig=true|false (ALPHA - default=false) -DynamicVolumeProvisioning=true|false (ALPHA - default=true) +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) +MountPropagation=true|false (ALPHA - default=false) PersistentLocalVolumes=true|false (ALPHA - default=false) -RotateKubeletClientCertificate=true|false (ALPHA - default=false) +PodPriority=true|false (ALPHA - default=false) +RotateKubeletClientCertificate=true|false (BETA - default=true) RotateKubeletServerCertificate=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) --google-json-key string The Google Cloud Platform Service Account JSON Key to use for authentication. - --insecure-allow-any-token username/group1,group2 If set, your server will be INSECURE. Any token will be allowed and user information will be parsed from the token as username/group1,group2 --insecure-bind-address ip The IP address on which to serve the --insecure-port (set to 0.0.0.0 for all interfaces). (default 127.0.0.1) --insecure-port int The port on which to serve unsecured, unauthenticated access. It is assumed that firewall rules are set up such that this port is not reachable from outside of the cluster and that port 443 on the cluster's public address is proxied to this port. This is performed by nginx in the default setup. (default 8080) --kubelet-certificate-authority string Path to a cert file for the certificate authority. @@ -106,12 +120,15 @@ TaintBasedEvictions=true|false (ALPHA - default=false) --oidc-ca-file string If set, the OpenID server's certificate will be verified by one of the authorities in the oidc-ca-file, otherwise the host's root CA set will be used. --oidc-client-id string The client ID for the OpenID Connect client, must be set if oidc-issuer-url is set. --oidc-groups-claim string If provided, the name of a custom OpenID Connect claim for specifying user groups. The claim value is expected to be a string or array of strings. This flag is experimental, please see the authentication documentation for further details. + --oidc-groups-prefix string If provided, all groups will be prefixed with this value to prevent conflicts with other authentication strategies. --oidc-issuer-url string The URL of the OpenID issuer, only HTTPS scheme will be accepted. If set, it will be used to verify the OIDC JSON Web Token (JWT). --oidc-username-claim string The OpenID claim to use as the user name. Note that claims other than the default ('sub') is not guaranteed to be unique and immutable. This flag is experimental, please see the authentication documentation for further details. (default "sub") + --oidc-username-prefix string If provided, all usernames will be prefixed with this value. If not provided, username claims other than 'email' are prefixed by the issuer URL to avoid clashes. To skip any prefixing, provide the value '-'. --profiling Enable profiling via web interface host:port/debug/pprof/ (default true) - --proxy-client-cert-file string Client certificate used to prove the identity of the aggregator or kube-apiserver when it must call out during a request. This includes proxying requests to a user api-server and calling out to webhook admission plugins. It is expected that this cert includes a signature from the CA in the --requestheader-client-ca-file flag. That CA is published in the 'extension-apiserver-authentication' configmap in the kube-system namespace. Components receiving calls from kube-aggregator should use that CA to perform their half of the mutual TLS verification. + --proxy-client-cert-file string Client certificate used to prove the identity of the aggregator or kube-apiserver when it must call out during a request. This includes proxying requests to a user api-server and calling out to webhook admission plugins. It is expected that this cert includes a signature from the CA in the --requestheader-client-ca-file flag. That CA is published in the 'extension-apiserver-authentication' configmap in the kube-system namespace. Components recieving calls from kube-aggregator should use that CA to perform their half of the mutual TLS verification. --proxy-client-key-file string Private key for the client certificate used to prove the identity of the aggregator or kube-apiserver when it must call out during a request. This includes proxying requests to a user api-server and calling out to webhook admission plugins. --repair-malformed-updates If true, server will do its best to fix the update request to pass the validation, e.g., setting empty UID in update request to its existing value. This flag can be turned off after we fix all the clients that send malformed updates. (default true) + --request-timeout duration An optional field indicating the duration a handler must keep a request open before timing it out. This is the default request timeout for requests but may be overridden by flags such as --min-request-timeout for specific types of requests. (default 1m0s) --requestheader-allowed-names stringSlice List of client certificate common names to allow to provide usernames in headers specified by --requestheader-username-headers. If empty, any client certificate validated by the authorities in --requestheader-client-ca-file is allowed. --requestheader-client-ca-file string Root certificate bundle to use to verify client certificates on incoming requests before trusting usernames in headers specified by --requestheader-username-headers --requestheader-extra-headers-prefix stringSlice List of request header prefixes to inspect. X-Remote-Extra- is suggested. @@ -127,9 +144,9 @@ TaintBasedEvictions=true|false (ALPHA - default=false) --ssh-user string If non-empty, use secure SSH proxy to the nodes, using this user name --storage-backend string The storage backend for persistence. Options: 'etcd3' (default), 'etcd2'. --storage-media-type string The media type to use to store objects in storage. Some resources or storage backends may only support a specific media type and will ignore this setting. (default "application/vnd.kubernetes.protobuf") - --storage-versions string The per-group version to store resources in. Specified in the format "group1/version1,group2/version2,...". In the case where objects are moved from one group to the other, you may specify the format "group1=group2/v1beta1,group3/v1beta1,...". You only need to pass the groups you wish to change from the defaults. It defaults to a list of preferred versions of all registered groups, which is derived from the KUBE_API_VERSIONS environment variable. (default "admission.k8s.io/v1alpha1,admissionregistration.k8s.io/v1alpha1,apps/v1beta1,authentication.k8s.io/v1,authorization.k8s.io/v1,autoscaling/v1,batch/v1,certificates.k8s.io/v1beta1,componentconfig/v1alpha1,extensions/v1beta1,federation/v1beta1,imagepolicy.k8s.io/v1alpha1,networking.k8s.io/v1,policy/v1beta1,rbac.authorization.k8s.io/v1beta1,settings.k8s.io/v1alpha1,storage.k8s.io/v1,v1") + --storage-versions string The per-group version to store resources in. Specified in the format "group1/version1,group2/version2,...". In the case where objects are moved from one group to the other, you may specify the format "group1=group2/v1beta1,group3/v1beta1,...". You only need to pass the groups you wish to change from the defaults. It defaults to a list of preferred versions of all registered groups, which is derived from the KUBE_API_VERSIONS environment variable. (default "admission.k8s.io/v1alpha1,admissionregistration.k8s.io/v1alpha1,apps/v1beta1,authentication.k8s.io/v1,authorization.k8s.io/v1,autoscaling/v1,batch/v1,certificates.k8s.io/v1beta1,componentconfig/v1alpha1,extensions/v1beta1,federation/v1beta1,imagepolicy.k8s.io/v1alpha1,networking.k8s.io/v1,policy/v1beta1,rbac.authorization.k8s.io/v1beta1,scheduling.k8s.io/v1alpha1,settings.k8s.io/v1alpha1,storage.k8s.io/v1,v1") --target-ram-mb int Memory limit for apiserver in MB (used to configure sizes of caches, etc.) - --tls-ca-file string If set, this certificate authority will used for secure access from Admission Controllers. This must be a valid PEM-encoded CA bundle. Alternatively, the certificate authority can be appended to the certificate provided by --tls-cert-file. + --tls-ca-file string If set, this certificate authority will used for secure access from Admission Controllers. This must be a valid PEM-encoded CA bundle. Altneratively, the certificate authority can be appended to the certificate provided by --tls-cert-file. --tls-cert-file string File containing the default x509 Certificate for HTTPS. (CA cert, if any, concatenated after server cert). If HTTPS serving is enabled, and --tls-cert-file and --tls-private-key-file are not provided, a self-signed certificate and key are generated for the public address and saved to /var/run/kubernetes. --tls-private-key-file string File containing the default x509 private key matching --tls-cert-file. --tls-sni-cert-key namedCertKey A pair of x509 certificate and private key file paths, optionally suffixed with a list of domain patterns which are fully qualified domain names, possibly with prefixed wildcard segments. If no domain patterns are provided, the names of the certificate are extracted. Non-wildcard matches trump over wildcard matches, explicit domain patterns trump over extracted names. For multiple key/certificate pairs, use the --tls-sni-cert-key multiple times. Examples: "example.crt,example.key" or "foo.crt,foo.key:*.foo.com,foo.com". (default []) @@ -139,4 +156,4 @@ TaintBasedEvictions=true|false (ALPHA - default=false) --watch-cache-sizes stringSlice List of watch cache sizes for every resource (pods, nodes, etc.), comma separated. The individual override format: resource#size, where size is a number. It takes effect when watch-cache is enabled. ``` -###### Auto generated by spf13/cobra on 11-Jul-2017 +###### Auto generated by spf13/cobra on 27-Sep-2017 diff --git a/docs/admin/kube-controller-manager.md b/docs/admin/kube-controller-manager.md index 5d8b9eae99172..57f973ba96c13 100644 --- a/docs/admin/kube-controller-manager.md +++ b/docs/admin/kube-controller-manager.md @@ -45,11 +45,11 @@ kube-controller-manager --concurrent-service-syncs int32 The number of services that are allowed to sync concurrently. Larger number = more responsive service management, but more CPU (and network) load (default 1) --concurrent-serviceaccount-token-syncs int32 The number of service account token objects that are allowed to sync concurrently. Larger number = more responsive token generation, but more CPU (and network) load (default 5) --concurrent_rc_syncs int32 The number of replication controllers that are allowed to sync concurrently. Larger number = more responsive replica management, but more CPU (and network) load (default 5) - --configure-cloud-routes Should CIDRs allocated by allocate-node-cidrs be configured on the cloud provider. If using a network overlay which will handle routing independent of the cloud provider, set this to false. (default true) + --configure-cloud-routes Should CIDRs allocated by allocate-node-cidrs be configured on the cloud provider. (default true) --contention-profiling Enable lock contention profiling, if profiling is enabled --controller-start-interval duration Interval between starting controller managers. --controllers stringSlice A list of controllers to enable. '*' enables all on-by-default controllers, 'foo' enables the controller named 'foo', '-foo' disables the controller named 'foo'. -All controllers: attachdetach, bootstrapsigner, cronjob, csrapproving, csrsigning, daemonset, deployment, disruption, endpoint, garbagecollector, horizontalpodautoscaling, job, namespace, node, persistentvolume-binder, podgc, replicaset, replicationcontroller, resourcequota, route, service, serviceaccount, serviceaccount-token, statefulset, tokencleaner, ttl +All controllers: attachdetach, bootstrapsigner, cronjob, csrapproving, csrsigning, daemonset, deployment, disruption, endpoint, garbagecollector, horizontalpodautoscaling, job, namespace, node, persistentvolume-binder, persistentvolume-expander, podgc, replicaset, replicationcontroller, resourcequota, route, service, serviceaccount, serviceaccount-token, statefulset, tokencleaner, ttl Disabled-by-default controllers: bootstrapsigner, tokencleaner (default [*]) --deployment-controller-sync-period duration Period for syncing the deployments. (default 30s) --disable-attach-detach-reconcile-sync Disable volume attach detach reconciler sync. Disabling this may cause volumes to be mismatched with pods. Use wisely. @@ -59,28 +59,41 @@ Disabled-by-default controllers: bootstrapsigner, tokencleaner (default [*]) --enable-taint-manager WARNING: Beta feature. If set to true enables NoExecute Taints and will evict all not-tolerating Pod running on Nodes tainted with this kind of Taints. (default true) --experimental-cluster-signing-duration duration The length of duration signed certificates will be given. (default 8760h0m0s) --feature-gates mapStringBool A set of key=value pairs that describe feature gates for alpha/experimental features. Options are: +APIListChunking=true|false (ALPHA - default=false) +APIResponseCompression=true|false (ALPHA - default=false) Accelerators=true|false (ALPHA - default=false) -AdvancedAuditing=true|false (ALPHA - default=false) -AffinityInAnnotations=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) +CPUManager=true|false (ALPHA - default=false) +CustomResourceValidation=true|false (ALPHA - default=false) +DebugContainers=true|false (ALPHA - default=false) +DevicePlugins=true|false (ALPHA - default=false) DynamicKubeletConfig=true|false (ALPHA - default=false) -DynamicVolumeProvisioning=true|false (ALPHA - default=true) +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) +MountPropagation=true|false (ALPHA - default=false) PersistentLocalVolumes=true|false (ALPHA - default=false) -RotateKubeletClientCertificate=true|false (ALPHA - default=false) +PodPriority=true|false (ALPHA - default=false) +RotateKubeletClientCertificate=true|false (BETA - default=true) RotateKubeletServerCertificate=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) --flex-volume-plugin-dir string Full path of the directory in which the flex volume plugin should search for additional third party volume plugins. (default "/usr/libexec/kubernetes/kubelet-plugins/volume/exec/") --google-json-key string The Google Cloud Platform Service Account JSON Key to use for authentication. --horizontal-pod-autoscaler-downscale-delay duration The period since last downscale, before another downscale can be performed in horizontal pod autoscaler. (default 5m0s) --horizontal-pod-autoscaler-sync-period duration The period for syncing the number of pods in horizontal pod autoscaler. (default 30s) --horizontal-pod-autoscaler-upscale-delay duration The period since last upscale, before another upscale can be performed in horizontal pod autoscaler. (default 3m0s) - --horizontal-pod-autoscaler-use-rest-clients WARNING: alpha feature. If set to true, causes the horizontal pod autoscaler controller to use REST clients through the kube-aggregator, instead of using the legacy metrics client through the API server proxy. This is required for custom metrics support in the horizonal pod autoscaler. + --horizontal-pod-autoscaler-use-rest-clients WARNING: alpha feature. If set to true, causes the horizontal pod autoscaler controller to use REST clients through the kube-aggregator, instead of using the legacy metrics client through the API server proxy. This is required for custom metrics support in the horizontal pod autoscaler. --insecure-experimental-approve-all-kubelet-csrs-for-group string This flag does nothing. --kube-api-burst int32 Burst to use while talking with kubernetes apiserver (default 30) --kube-api-content-type string Content type of requests sent to apiserver. (default "application/vnd.kubernetes.protobuf") @@ -90,7 +103,7 @@ TaintBasedEvictions=true|false (ALPHA - default=false) --leader-elect Start a leader election client and gain leadership before executing the main loop. Enable this when running replicated components for high availability. (default true) --leader-elect-lease-duration duration 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. (default 15s) --leader-elect-renew-deadline duration 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. (default 10s) - --leader-elect-resource-lock endpoints The type of resource resource object that is used for locking duringleader election. Supported options are endpoints (default) and `configmap`. (default "endpoints") + --leader-elect-resource-lock endpoints The type of resource object that is used for locking during leader election. Supported options are endpoints (default) and `configmap`. (default "endpoints") --leader-elect-retry-period duration The duration the clients should wait between attempting acquisition and renewal of a leadership. This is only applicable if leader election is enabled. (default 2s) --master string The address of the Kubernetes API server (overrides any value in kubeconfig) --min-resync-period duration The resync period in reflectors will be random between MinResyncPeriod and 2*MinResyncPeriod (default 12h0m0s) @@ -123,4 +136,4 @@ TaintBasedEvictions=true|false (ALPHA - default=false) --version version[=true] Print version information and quit ``` -###### Auto generated by spf13/cobra on 11-Jul-2017 +###### Auto generated by spf13/cobra on 27-Sep-2017 diff --git a/docs/admin/kube-proxy.md b/docs/admin/kube-proxy.md index 6e6551af65926..0e2083593da65 100644 --- a/docs/admin/kube-proxy.md +++ b/docs/admin/kube-proxy.md @@ -11,8 +11,8 @@ notitle: true The Kubernetes network proxy runs on each node. This reflects services as defined in the Kubernetes API on each node and can do simple -TCP, UDP stream forwarding or round robin TCP, UDP forwarding across a set of backends. -Service cluster IPs and ports are currently found through Docker-links-compatible +TCP,UDP stream forwarding or round robin TCP,UDP forwarding across a set of backends. +Service cluster ips and ports are currently found through Docker-links-compatible environment variables specifying ports opened by the service proxy. There is an optional addon that provides cluster DNS for these cluster IPs. The user must create a service with the apiserver API to configure the proxy. @@ -26,8 +26,8 @@ kube-proxy ``` --azure-container-registry-config string Path to the file container Azure container registry configuration information. --bind-address ip The IP address for the proxy server to serve on (set to 0.0.0.0 for all interfaces) (default 0.0.0.0) - --cleanup-iptables If true cleanup iptables rules and exit. - --cluster-cidr string The CIDR range of pods in the cluster. It is used to bridge traffic coming from outside of the cluster. If not provided, no off-cluster bridging will be performed. + --cleanup If true cleanup iptables and ipvs rules and exit. + --cluster-cidr string The CIDR range of pods in the cluster. When configured, traffic sent to a Service cluster IP from outside this range will be masqueraded and traffic sent from pods to an external LoadBalancer IP will be directed to the respective cluster IP instead --config string The path to the configuration file. --config-sync-period duration How often configuration from the apiserver is refreshed. Must be greater than 0. (default 15m0s) --conntrack-max-per-core int32 Maximum number of NAT connections to track per CPU core (0 to leave the limit as-is and ignore conntrack-min). (default 32768) @@ -35,22 +35,35 @@ kube-proxy --conntrack-tcp-timeout-close-wait duration NAT timeout for TCP connections in the CLOSE_WAIT state (default 1h0m0s) --conntrack-tcp-timeout-established duration Idle timeout for established TCP connections (0 to leave as-is) (default 24h0m0s) --feature-gates mapStringBool A set of key=value pairs that describe feature gates for alpha/experimental features. Options are: +APIListChunking=true|false (ALPHA - default=false) +APIResponseCompression=true|false (ALPHA - default=false) Accelerators=true|false (ALPHA - default=false) -AdvancedAuditing=true|false (ALPHA - default=false) -AffinityInAnnotations=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) +CPUManager=true|false (ALPHA - default=false) +CustomResourceValidation=true|false (ALPHA - default=false) +DebugContainers=true|false (ALPHA - default=false) +DevicePlugins=true|false (ALPHA - default=false) DynamicKubeletConfig=true|false (ALPHA - default=false) -DynamicVolumeProvisioning=true|false (ALPHA - default=true) +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) +MountPropagation=true|false (ALPHA - default=false) PersistentLocalVolumes=true|false (ALPHA - default=false) -RotateKubeletClientCertificate=true|false (ALPHA - default=false) +PodPriority=true|false (ALPHA - default=false) +RotateKubeletClientCertificate=true|false (BETA - default=true) RotateKubeletServerCertificate=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) --google-json-key string The Google Cloud Platform Service Account JSON Key to use for authentication. --healthz-bind-address ip The IP address and port for the health check server to serve on (set to 0.0.0.0 for all interfaces) (default 0.0.0.0:10256) --healthz-port int32 The port to bind the health check server. Use 0 to disable. (default 10256) @@ -58,19 +71,23 @@ TaintBasedEvictions=true|false (ALPHA - default=false) --iptables-masquerade-bit int32 If using the pure iptables proxy, the bit of the fwmark space to mark packets requiring SNAT with. Must be within the range [0, 31]. (default 14) --iptables-min-sync-period duration The minimum interval of how often the iptables rules can be refreshed as endpoints and services change (e.g. '5s', '1m', '2h22m'). --iptables-sync-period duration The maximum interval of how often iptables rules are refreshed (e.g. '5s', '1m', '2h22m'). Must be greater than 0. (default 30s) + --ipvs-min-sync-period duration The minimum interval of how often the ipvs rules can be refreshed as endpoints and services change (e.g. '5s', '1m', '2h22m'). + --ipvs-scheduler string The ipvs scheduler type when proxy mode is ipvs + --ipvs-sync-period duration The maximum interval of how often ipvs rules are refreshed (e.g. '5s', '1m', '2h22m'). Must be greater than 0. --kube-api-burst int Burst to use while talking with kubernetes apiserver (default 10) --kube-api-content-type string Content type of requests sent to apiserver. (default "application/vnd.kubernetes.protobuf") --kube-api-qps float32 QPS to use while talking with kubernetes apiserver (default 5) --kubeconfig string Path to kubeconfig file with authorization information (the master location is set by the master flag). - --masquerade-all If using the pure iptables proxy, SNAT everything (this not commonly needed) + --masquerade-all If using the pure iptables proxy, SNAT all traffic sent via Service cluster IPs (this not commonly needed) --master string The address of the Kubernetes API server (overrides any value in kubeconfig) + --metrics-bind-address ip The IP address and port for the metrics server to serve on (set to 0.0.0.0 for all interfaces) (default 127.0.0.1:10249) --oom-score-adj int32 The oom-score-adj value for kube-proxy process. Values must be within the range [-1000, 1000] (default -999) --profiling If true enables profiling via web interface on /debug/pprof handler. - --proxy-mode ProxyMode Which proxy mode to use: 'userspace' (older) or 'iptables' (faster). If blank, use the best-available proxy (currently iptables). If the iptables proxy is selected, regardless of how, but the system's kernel or iptables versions are insufficient, this always falls back to the userspace proxy. + --proxy-mode ProxyMode Which proxy mode to use: 'userspace' (older) or 'iptables' (faster) or 'ipvs'(experimental)'. If blank, use the best-available proxy (currently iptables). If the iptables proxy is selected, regardless of how, but the system's kernel or iptables versions are insufficient, this always falls back to the userspace proxy. --proxy-port-range port-range Range of host ports (beginPort-endPort, inclusive) that may be consumed in order to proxy service traffic. If unspecified (0-0) then ports will be randomly chosen. --udp-timeout duration How long an idle UDP connection will be kept open (e.g. '250ms', '2s'). Must be greater than 0. Only applicable for proxy-mode=userspace (default 250ms) --version version[=true] Print version information and quit --write-config-to string If set, write the default configuration values to this file and exit. ``` -###### Auto generated by spf13/cobra on 11-Jul-2017 +###### Auto generated by spf13/cobra on 27-Sep-2017 diff --git a/docs/admin/kube-scheduler.md b/docs/admin/kube-scheduler.md index 8c32f9e12c24f..d8ef6a5e1cf82 100644 --- a/docs/admin/kube-scheduler.md +++ b/docs/admin/kube-scheduler.md @@ -2,7 +2,6 @@ title: kube-scheduler notitle: true --- - ## kube-scheduler @@ -30,22 +29,35 @@ kube-scheduler --azure-container-registry-config string Path to the file container Azure container registry configuration information. --contention-profiling Enable lock contention profiling, if profiling is enabled --feature-gates mapStringBool A set of key=value pairs that describe feature gates for alpha/experimental features. Options are: +APIListChunking=true|false (ALPHA - default=false) +APIResponseCompression=true|false (ALPHA - default=false) Accelerators=true|false (ALPHA - default=false) -AdvancedAuditing=true|false (ALPHA - default=false) -AffinityInAnnotations=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) +CPUManager=true|false (ALPHA - default=false) +CustomResourceValidation=true|false (ALPHA - default=false) +DebugContainers=true|false (ALPHA - default=false) +DevicePlugins=true|false (ALPHA - default=false) DynamicKubeletConfig=true|false (ALPHA - default=false) -DynamicVolumeProvisioning=true|false (ALPHA - default=true) +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) +MountPropagation=true|false (ALPHA - default=false) PersistentLocalVolumes=true|false (ALPHA - default=false) -RotateKubeletClientCertificate=true|false (ALPHA - default=false) +PodPriority=true|false (ALPHA - default=false) +RotateKubeletClientCertificate=true|false (BETA - default=true) RotateKubeletServerCertificate=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) --google-json-key string The Google Cloud Platform Service Account JSON Key to use for authentication. --kube-api-burst int32 Burst to use while talking with kubernetes apiserver (default 100) --kube-api-content-type string Content type of requests sent to apiserver. (default "application/vnd.kubernetes.protobuf") @@ -69,4 +81,4 @@ TaintBasedEvictions=true|false (ALPHA - default=false) --version version[=true] Print version information and quit ``` -###### Auto generated by spf13/cobra on 11-Jul-2017 +###### Auto generated by spf13/cobra on 27-Sep-2017 diff --git a/docs/admin/kubelet.md b/docs/admin/kubelet.md index 77b1b0caf4977..51e609566ea21 100644 --- a/docs/admin/kubelet.md +++ b/docs/admin/kubelet.md @@ -36,145 +36,161 @@ kubelet ### Options ``` - --address ip The IP address for the Kubelet to serve on (set to 0.0.0.0 for all interfaces) (default 0.0.0.0) - --allow-privileged If true, allow containers to request privileged mode. - --anonymous-auth Enables anonymous requests to the Kubelet server. Requests that are not rejected by another authentication method are treated as anonymous requests. Anonymous requests have a username of system:anonymous, and a group name of system:unauthenticated. (default true) - --authentication-token-webhook Use the TokenReview API to determine authentication for bearer tokens. - --authentication-token-webhook-cache-ttl duration The duration to cache responses from the webhook token authenticator. (default 2m0s) - --authorization-mode string Authorization mode for Kubelet server. Valid options are AlwaysAllow or Webhook. Webhook mode uses the SubjectAccessReview API to determine authorization. (default "AlwaysAllow") - --authorization-webhook-cache-authorized-ttl duration The duration to cache 'authorized' responses from the webhook authorizer. (default 5m0s) - --authorization-webhook-cache-unauthorized-ttl duration The duration to cache 'unauthorized' responses from the webhook authorizer. (default 30s) - --azure-container-registry-config string Path to the file container Azure container registry configuration information. - --bootstrap-kubeconfig string Path to a kubeconfig file that will be used to get client certificate for kubelet. If the file specified by --kubeconfig does not exist, the bootstrap kubeconfig is used to request a client certificate from the API server. On success, a kubeconfig file referencing the generated client certificate and key is written to the path specified by --kubeconfig. The client certificate and key file will be stored in the directory pointed by --cert-dir. - --cadvisor-port int32 The port of the localhost cAdvisor endpoint (default 4194) - --cert-dir string The directory where the TLS certs are located. If --tls-cert-file and --tls-private-key-file are provided, this flag will be ignored. (default "/var/run/kubernetes") - --cgroup-driver string Driver that the kubelet uses to manipulate cgroups on the host. Possible values: 'cgroupfs', 'systemd' (default "cgroupfs") - --cgroup-root string Optional root cgroup to use for pods. This is handled by the container runtime on a best effort basis. Default: '', which means use the container runtime default. - --cgroups-per-qos Enable creation of QoS cgroup hierarchy, if true top level QoS and pod cgroups are created. (default true) - --chaos-chance float If > 0.0, introduce random client errors and latency. Intended for testing. - --client-ca-file string If set, any request presenting a client certificate signed by one of the authorities in the client-ca-file is authenticated with an identity corresponding to the CommonName of the client certificate. - --cloud-config string The path to the cloud provider configuration file. Empty string for no configuration file. - --cloud-provider string The provider for cloud services. By default, kubelet will attempt to auto-detect the cloud provider. Specify empty string for running with no cloud provider. (default "auto-detect") - --cluster-dns stringSlice Comma-separated list of DNS server IP address. This value is used for containers DNS server in case of Pods with "dnsPolicy=ClusterFirst". Note: all DNS servers appearing in the list MUST serve the same set of records otherwise name resolution within the cluster may not work correctly. There is no guarantee as to which DNS server may be contacted for name resolution. - --cluster-domain string Domain for this cluster. If set, kubelet will configure all containers to search this domain in addition to the host's search domains - --cni-bin-dir string The full path of the directory in which to search for CNI plugin binaries. Default: /opt/cni/bin - --cni-conf-dir string The full path of the directory in which to search for CNI config files. Default: /etc/cni/net.d - --container-runtime string The container runtime to use. Possible values: 'docker', 'rkt'. (default "docker") - --container-runtime-endpoint string [Experimental] The endpoint of remote runtime service. Currently unix socket is supported on Linux, and tcp is supported on windows. Examples:'unix:///var/run/dockershim.sock', 'tcp://localhost:3735' (default "unix:///var/run/dockershim.sock") - --containerized Experimental support for running kubelet in a container. Intended for testing. - --contention-profiling Enable lock contention profiling, if profiling is enabled - --cpu-cfs-quota Enable CPU CFS quota enforcement for containers that specify CPU limits (default true) - --docker-disable-shared-pid The Container Runtime Interface (CRI) defaults to using a shared PID namespace for containers in a pod when running with Docker 1.13.1 or higher. Setting this flag reverts to the previous behavior of isolated PID namespaces. This ability will be removed in a future Kubernetes release. - --docker-endpoint string Use this for the docker endpoint to communicate with (default "unix:///var/run/docker.sock") - --enable-controller-attach-detach Enables the Attach/Detach controller to manage attachment/detachment of volumes scheduled to this node, and disables kubelet from executing any attach/detach operations (default true) - --enable-custom-metrics Support for gathering custom metrics. - --enable-debugging-handlers Enables server endpoints for log collection and local running of containers and commands (default true) - --enable-server Enable the Kubelet's server (default true) - --enforce-node-allocatable stringSlice A comma separated list of levels of node allocatable enforcement to be enforced by kubelet. Acceptable options are 'pods', 'system-reserved' & 'kube-reserved'. If the latter two options are specified, '--system-reserved-cgroup' & '--kube-reserved-cgroup' must also be set respectively. See https://git.k8s.io/community/contributors/design-proposals/node/node-allocatable.md for more details. (default [pods]) - --event-burst int32 Maximum size of a bursty event records, temporarily allows event records to burst to this number, while still not exceeding event-qps. Only used if --event-qps > 0 (default 10) - --event-qps int32 If > 0, limit event creations per second to this value. If 0, unlimited. (default 5) - --eviction-hard string A set of eviction thresholds (e.g. memory.available<1Gi) that if met would trigger a pod eviction. (default "memory.available<100Mi,nodefs.available<10%,nodefs.inodesFree<5%") - --eviction-max-pod-grace-period int32 Maximum allowed grace period (in seconds) to use when terminating pods in response to a soft eviction threshold being met. If negative, defer to pod specified value. - --eviction-minimum-reclaim string A set of minimum reclaims (e.g. imagefs.available=2Gi) that describes the minimum amount of resource the kubelet will reclaim when performing a pod eviction if that resource is under pressure. - --eviction-pressure-transition-period duration Duration for which the kubelet has to wait before transitioning out of an eviction pressure condition. (default 5m0s) - --eviction-soft string A set of eviction thresholds (e.g. memory.available<1.5Gi) that if met over a corresponding grace period would trigger a pod eviction. - --eviction-soft-grace-period string A set of eviction grace periods (e.g. memory.available=1m30s) that correspond to how long a soft eviction threshold must hold before triggering a pod eviction. - --exit-on-lock-contention Whether kubelet should exit upon lock-file contention. - --experimental-allocatable-ignore-eviction When set to 'true', Hard Eviction Thresholds will be ignored while calculating Node Allocatable. See https://git.k8s.io/community/contributors/design-proposals/node/node-allocatable.md for more details. [default=false] - --experimental-allowed-unsafe-sysctls stringSlice Comma-separated whitelist of unsafe sysctls or unsafe sysctl patterns (ending in *). Use these at your own risk. - --experimental-bootstrap-kubeconfig string deprecated: use --bootstrap-kubeconfig - --experimental-check-node-capabilities-before-mount [Experimental] if set true, the kubelet will check the underlying node for required componenets (binaries, etc.) before performing the mount - --experimental-fail-swap-on Makes the Kubelet fail to start if swap is enabled on the node. This is a temporary opton to maintain legacy behavior, failing due to swap enabled will happen by default in v1.6. - --experimental-kernel-memcg-notification If enabled, the kubelet will integrate with the kernel memcg notification to determine if memory eviction thresholds are crossed rather than polling. - --experimental-mounter-path string [Experimental] Path of mounter binary. Leave empty to use the default mount. - --experimental-qos-reserved mapStringString A set of ResourceName=Percentage (e.g. memory=50%) pairs that describe how pod resource requests are reserved at the QoS level. Currently only memory is supported. [default=none] - --feature-gates string A set of key=value pairs that describe feature gates for alpha/experimental features. Options are: + --address ip The IP address for the Kubelet to serve on (set to 0.0.0.0 for all interfaces) (default 0.0.0.0) + --allow-privileged If true, allow containers to request privileged mode. + --anonymous-auth Enables anonymous requests to the Kubelet server. Requests that are not rejected by another authentication method are treated as anonymous requests. Anonymous requests have a username of system:anonymous, and a group name of system:unauthenticated. (default true) + --authentication-token-webhook Use the TokenReview API to determine authentication for bearer tokens. + --authentication-token-webhook-cache-ttl duration The duration to cache responses from the webhook token authenticator. (default 2m0s) + --authorization-mode string Authorization mode for Kubelet server. Valid options are AlwaysAllow or Webhook. Webhook mode uses the SubjectAccessReview API to determine authorization. (default "AlwaysAllow") + --authorization-webhook-cache-authorized-ttl duration The duration to cache 'authorized' responses from the webhook authorizer. (default 5m0s) + --authorization-webhook-cache-unauthorized-ttl duration The duration to cache 'unauthorized' responses from the webhook authorizer. (default 30s) + --azure-container-registry-config string Path to the file container Azure container registry configuration information. + --bootstrap-kubeconfig string Path to a kubeconfig file that will be used to get client certificate for kubelet. If the file specified by --kubeconfig does not exist, the bootstrap kubeconfig is used to request a client certificate from the API server. On success, a kubeconfig file referencing the generated client certificate and key is written to the path specified by --kubeconfig. The client certificate and key file will be stored in the directory pointed by --cert-dir. + --cadvisor-port int32 The port of the localhost cAdvisor endpoint (set to 0 to disable) (default 4194) + --cert-dir string The directory where the TLS certs are located. If --tls-cert-file and --tls-private-key-file are provided, this flag will be ignored. (default "/var/run/kubernetes") + --cgroup-driver string Driver that the kubelet uses to manipulate cgroups on the host. Possible values: 'cgroupfs', 'systemd' (default "cgroupfs") + --cgroup-root string Optional root cgroup to use for pods. This is handled by the container runtime on a best effort basis. Default: '', which means use the container runtime default. + --cgroups-per-qos Enable creation of QoS cgroup hierarchy, if true top level QoS and pod cgroups are created. (default true) + --chaos-chance float If > 0.0, introduce random client errors and latency. Intended for testing. + --client-ca-file string If set, any request presenting a client certificate signed by one of the authorities in the client-ca-file is authenticated with an identity corresponding to the CommonName of the client certificate. + --cloud-config string The path to the cloud provider configuration file. Empty string for no configuration file. + --cloud-provider string The provider for cloud services. By default, kubelet will attempt to auto-detect the cloud provider (deprecated). Specify empty string for running with no cloud provider, this will be the default in upcoming releases. (default "auto-detect") + --cluster-dns stringSlice Comma-separated list of DNS server IP address. This value is used for containers DNS server in case of Pods with "dnsPolicy=ClusterFirst". Note: all DNS servers appearing in the list MUST serve the same set of records otherwise name resolution within the cluster may not work correctly. There is no guarantee as to which DNS server may be contacted for name resolution. + --cluster-domain string Domain for this cluster. If set, kubelet will configure all containers to search this domain in addition to the host's search domains + --cni-bin-dir string The full path of the directory in which to search for CNI plugin binaries. Default: /opt/cni/bin + --cni-conf-dir string The full path of the directory in which to search for CNI config files. Default: /etc/cni/net.d + --container-runtime string The container runtime to use. Possible values: 'docker', 'rkt'. (default "docker") + --container-runtime-endpoint string [Experimental] The endpoint of remote runtime service. Currently unix socket is supported on Linux, and tcp is supported on windows. Examples:'unix:///var/run/dockershim.sock', 'tcp://localhost:3735' (default "unix:///var/run/dockershim.sock") + --containerized Experimental support for running kubelet in a container. Intended for testing. + --contention-profiling Enable lock contention profiling, if profiling is enabled + --cpu-cfs-quota Enable CPU CFS quota enforcement for containers that specify CPU limits (default true) + --cpu-manager-policy string CPU Manager policy to use. Possible values: 'none', 'static'. Default: 'none' (default "none") + --cpu-manager-reconcile-period NodeStatusUpdateFrequency CPU Manager reconciliation period. Examples: '10s', or '1m'. If not supplied, defaults to NodeStatusUpdateFrequency (default 10s) + --docker-disable-shared-pid The Container Runtime Interface (CRI) defaults to using a shared PID namespace for containers in a pod when running with Docker 1.13.1 or higher. Setting this flag reverts to the previous behavior of isolated PID namespaces. This ability will be removed in a future Kubernetes release. (default true) + --docker-endpoint string Use this for the docker endpoint to communicate with (default "unix:///var/run/docker.sock") + --dynamic-config-dir string The Kubelet will use this directory for checkpointing downloaded configurations and tracking configuration health. The Kubelet will create this directory if it does not already exist. The path may be absolute or relative; relative paths start at the Kubelet's current working directory. Providing this flag enables dynamic Kubelet configuration. Presently, you must also enable the DynamicKubeletConfig feature gate to pass this flag. + --enable-controller-attach-detach Enables the Attach/Detach controller to manage attachment/detachment of volumes scheduled to this node, and disables kubelet from executing any attach/detach operations (default true) + --enable-custom-metrics Support for gathering custom metrics. + --enable-debugging-handlers Enables server endpoints for log collection and local running of containers and commands (default true) + --enable-server Enable the Kubelet's server (default true) + --enforce-node-allocatable stringSlice A comma separated list of levels of node allocatable enforcement to be enforced by kubelet. Acceptible options are 'pods', 'system-reserved' & 'kube-reserved'. If the latter two options are specified, '--system-reserved-cgroup' & '--kube-reserved-cgroup' must also be set respectively. See https://git.k8s.io/community/contributors/design-proposals/node-allocatable.md for more details. (default [pods]) + --event-burst int32 Maximum size of a bursty event records, temporarily allows event records to burst to this number, while still not exceeding event-qps. Only used if --event-qps > 0 (default 10) + --event-qps int32 If > 0, limit event creations per second to this value. If 0, unlimited. (default 5) + --eviction-hard string A set of eviction thresholds (e.g. memory.available<1Gi) that if met would trigger a pod eviction. (default "memory.available<100Mi,nodefs.available<10%,nodefs.inodesFree<5%") + --eviction-max-pod-grace-period int32 Maximum allowed grace period (in seconds) to use when terminating pods in response to a soft eviction threshold being met. If negative, defer to pod specified value. + --eviction-minimum-reclaim string A set of minimum reclaims (e.g. imagefs.available=2Gi) that describes the minimum amount of resource the kubelet will reclaim when performing a pod eviction if that resource is under pressure. + --eviction-pressure-transition-period duration Duration for which the kubelet has to wait before transitioning out of an eviction pressure condition. (default 5m0s) + --eviction-soft string A set of eviction thresholds (e.g. memory.available<1.5Gi) that if met over a corresponding grace period would trigger a pod eviction. + --eviction-soft-grace-period string A set of eviction grace periods (e.g. memory.available=1m30s) that correspond to how long a soft eviction threshold must hold before triggering a pod eviction. + --exit-on-lock-contention Whether kubelet should exit upon lock-file contention. + --experimental-allocatable-ignore-eviction When set to 'true', Hard Eviction Thresholds will be ignored while calculating Node Allocatable. See https://git.k8s.io/community/contributors/design-proposals/node-allocatable.md for more details. [default=false] + --experimental-allowed-unsafe-sysctls stringSlice Comma-separated whitelist of unsafe sysctls or unsafe sysctl patterns (ending in *). Use these at your own risk. + --experimental-bootstrap-kubeconfig string deprecated: use --bootstrap-kubeconfig + --experimental-check-node-capabilities-before-mount [Experimental] if set true, the kubelet will check the underlying node for required componenets (binaries, etc.) before performing the mount + --experimental-kernel-memcg-notification If enabled, the kubelet will integrate with the kernel memcg notification to determine if memory eviction thresholds are crossed rather than polling. + --experimental-mounter-path string [Experimental] Path of mounter binary. Leave empty to use the default mount. + --experimental-qos-reserved mapStringString A set of ResourceName=Percentage (e.g. memory=50%) pairs that describe how pod resource requests are reserved at the QoS level. Currently only memory is supported. [default=none] + --fail-swap-on Makes the Kubelet fail to start if swap is enabled on the node. (default true) + --feature-gates string A set of key=value pairs that describe feature gates for alpha/experimental features. Options are: +APIListChunking=true|false (ALPHA - default=false) +APIResponseCompression=true|false (ALPHA - default=false) Accelerators=true|false (ALPHA - default=false) -AdvancedAuditing=true|false (ALPHA - default=false) -AffinityInAnnotations=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) +CPUManager=true|false (ALPHA - default=false) +CustomResourceValidation=true|false (ALPHA - default=false) +DebugContainers=true|false (ALPHA - default=false) +DevicePlugins=true|false (ALPHA - default=false) DynamicKubeletConfig=true|false (ALPHA - default=false) -DynamicVolumeProvisioning=true|false (ALPHA - default=true) +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) +MountPropagation=true|false (ALPHA - default=false) PersistentLocalVolumes=true|false (ALPHA - default=false) -RotateKubeletClientCertificate=true|false (ALPHA - default=false) +PodPriority=true|false (ALPHA - default=false) +RotateKubeletClientCertificate=true|false (BETA - default=true) RotateKubeletServerCertificate=true|false (ALPHA - default=false) StreamingProxyRedirects=true|false (BETA - default=true) +SupportIPVSProxyMode=true|false (ALPHA - default=false) TaintBasedEvictions=true|false (ALPHA - default=false) - --file-check-frequency duration Duration between checking config files for new data (default 20s) - --google-json-key string The Google Cloud Platform Service Account JSON Key to use for authentication. - --hairpin-mode string How should the kubelet setup hairpin NAT. This allows endpoints of a Service to loadbalance back to themselves if they should try to access their own Service. Valid values are "promiscuous-bridge", "hairpin-veth" and "none". (default "promiscuous-bridge") - --healthz-bind-address ip The IP address for the healthz server to serve on. (set to 0.0.0.0 for all interfaces) (default 127.0.0.1) - --healthz-port int32 The port of the localhost healthz endpoint (default 10248) - --host-ipc-sources stringSlice Comma-separated list of sources from which the Kubelet allows pods to use the host ipc namespace. (default [*]) - --host-network-sources stringSlice Comma-separated list of sources from which the Kubelet allows pods to use of host network. (default [*]) - --host-pid-sources stringSlice Comma-separated list of sources from which the Kubelet allows pods to use the host pid namespace. (default [*]) - --hostname-override string If non-empty, will use this string as identification instead of the actual hostname. - --http-check-frequency duration Duration between checking http for new data (default 20s) - --image-gc-high-threshold int32 The percent of disk usage after which image garbage collection is always run. (default 85) - --image-gc-low-threshold int32 The percent of disk usage before which image garbage collection is never run. Lowest disk usage to garbage collect to. (default 80) - --image-pull-progress-deadline duration If no pulling progress is made before this deadline, the image pulling will be cancelled. (default 1m0s) - --image-service-endpoint string [Experimental] The endpoint of remote image service. If not specified, it will be the same with container-runtime-endpoint by default. Currently unix socket is supported on Linux, and tcp is supported on windows. Examples:'unix:///var/run/dockershim.sock', 'tcp://localhost:3735' - --iptables-drop-bit int32 The bit of the fwmark space to mark packets for dropping. Must be within the range [0, 31]. (default 15) - --iptables-masquerade-bit int32 The bit of the fwmark space to mark packets for SNAT. Must be within the range [0, 31]. Please match this parameter with corresponding parameter in kube-proxy. (default 14) - --keep-terminated-pod-volumes Keep terminated pod volumes mounted to the node after the pod terminates. Can be useful for debugging volume related issues. - --kube-api-burst int32 Burst to use while talking with kubernetes apiserver (default 10) - --kube-api-content-type string Content type of requests sent to apiserver. (default "application/vnd.kubernetes.protobuf") - --kube-api-qps int32 QPS to use while talking with kubernetes apiserver (default 5) - --kube-reserved mapStringString A set of ResourceName=ResourceQuantity (e.g. cpu=200m,memory=500Mi, storage=1Gi) pairs that describe resources reserved for kubernetes system components. Currently cpu, memory and local storage for root file system are supported. See http://kubernetes.io/docs/user-guide/compute-resources for more detail. [default=none] - --kube-reserved-cgroup string Absolute name of the top level cgroup that is used to manage kubernetes components for which compute resources were reserved via '--kube-reserved' flag. Ex. '/kube-reserved'. [default=''] - --kubeconfig string Path to a kubeconfig file, specifying how to connect to the API server. --api-servers will be used for the location unless --require-kubeconfig is set. (default "/var/lib/kubelet/kubeconfig") - --kubelet-cgroups string Optional absolute name of cgroups to create and run the Kubelet in. - --lock-file string The path to file for kubelet to use as a lock file. - --make-iptables-util-chains If true, kubelet will ensure iptables utility rules are present on host. (default true) - --manifest-url string URL for accessing the container manifest - --manifest-url-header string HTTP header to use when accessing the manifest URL, with the key separated from the value with a ':', as in 'key:value' - --max-open-files int Number of files that can be opened by Kubelet process. (default 1000000) - --max-pods int32 Number of Pods that can run on this Kubelet. (default 110) - --minimum-image-ttl-duration duration Minimum age for an unused image before it is garbage collected. Examples: '300ms', '10s' or '2h45m'. (default 2m0s) - --network-plugin string The name of the network plugin to be invoked for various events in kubelet/pod lifecycle - --network-plugin-mtu int32 The MTU to be passed to the network plugin, to override the default. Set to 0 to use the default 1460 MTU. - --node-ip string IP address of the node. If set, kubelet will use this IP address for the node - --node-labels mapStringString Labels to add when registering the node in the cluster. Labels must be key=value pairs separated by ','. - --node-status-update-frequency duration Specifies how often kubelet posts node status to master. Note: be cautious when changing the constant, it must work with nodeMonitorGracePeriod in nodecontroller. (default 10s) - --oom-score-adj int32 The oom-score-adj value for kubelet process. Values must be within the range [-1000, 1000] (default -999) - --pod-cidr string The CIDR to use for pod IP addresses, only used in standalone mode. In cluster mode, this is obtained from the master. - --pod-infra-container-image string The image whose network/ipc namespaces containers in each pod will use. (default "gcr.io/google_containers/pause-amd64:3.0") - --pod-manifest-path string Path to to the directory containing pod manifest files to run, or the path to a single pod manifest file. Files starting with dots will be ignored. - --pods-per-core int32 Number of Pods per core that can run on this Kubelet. The total number of Pods on this Kubelet cannot exceed max-pods, so max-pods will be used if this calculation results in a larger number of Pods allowed on the Kubelet. A value of 0 disables this limit. - --port int32 The port for the Kubelet to serve on. (default 10250) - --protect-kernel-defaults Default kubelet behaviour for kernel tuning. If set, kubelet errors if any of kernel tunables is different than kubelet defaults. - --provider-id string Unique identifier for identifying the node in a machine database, i.e cloudprovider - --read-only-port int32 The read-only port for the Kubelet to serve on with no authentication/authorization (set to 0 to disable) (default 10255) - --really-crash-for-testing If true, when panics occur crash. Intended for testing. - --register-node Register the node with the apiserver (defaults to true if --api-servers is set) (default true) - --register-with-taints []api.Taint Register the node with the given list of taints (comma separated "=:"). No-op if register-node is false. - --registry-burst int32 Maximum size of a bursty pulls, temporarily allows pulls to burst to this number, while still not exceeding registry-qps. Only used if --registry-qps > 0 (default 10) - --registry-qps int32 If > 0, limit registry pull QPS to this value. If 0, unlimited. (default 5) - --require-kubeconfig If true the Kubelet will exit if there are configuration errors, and will ignore the value of --api-servers in favor of the server defined in the kubeconfig file. - --resolv-conf string Resolver configuration file used as the basis for the container DNS resolution configuration. (default "/etc/resolv.conf") - --rkt-api-endpoint string The endpoint of the rkt API service to communicate with. Only used if --container-runtime='rkt'. (default "localhost:15441") - --rkt-path string Path of rkt binary. Leave empty to use the first rkt in $PATH. Only used if --container-runtime='rkt'. - --root-dir string Directory path for managing kubelet files (volume mounts,etc). (default "/var/lib/kubelet") - --runonce If true, exit after spawning pods from local manifests or remote urls. Exclusive with --api-servers, and --enable-server - --runtime-cgroups string Optional absolute name of cgroups to create and run the runtime in. - --runtime-request-timeout duration Timeout of all runtime requests except long running request - pull, logs, exec and attach. When timeout exceeded, kubelet will cancel the request, throw out an error and retry later. (default 2m0s) - --seccomp-profile-root string Directory path for seccomp profiles. (default "/var/lib/kubelet/seccomp") - --serialize-image-pulls Pull images one at a time. We recommend *not* changing the default value on nodes that run docker daemon with version < 1.9 or an Aufs storage backend. Issue #10959 has more details. (default true) - --streaming-connection-idle-timeout duration Maximum time a streaming connection can be idle before the connection is automatically closed. 0 indicates no timeout. Example: '5m' (default 4h0m0s) - --sync-frequency duration Max period between synchronizing running containers and config (default 1m0s) - --system-cgroups / Optional absolute name of cgroups in which to place all non-kernel processes that are not already inside a cgroup under /. Empty for no container. Rolling back the flag requires a reboot. - --system-reserved mapStringString A set of ResourceName=ResourceQuantity (e.g. cpu=200m,memory=500Mi) pairs that describe resources reserved for non-kubernetes components. Currently only cpu and memory are supported. See http://kubernetes.io/docs/user-guide/compute-resources for more detail. [default=none] - --system-reserved-cgroup string Absolute name of the top level cgroup that is used to manage non-kubernetes components for which compute resources were reserved via '--system-reserved' flag. Ex. '/system-reserved'. [default=''] - --tls-cert-file string File containing x509 Certificate used for serving HTTPS (with intermediate certs, if any, concatenated after server cert). If --tls-cert-file and --tls-private-key-file are not provided, a self-signed certificate and key are generated for the public address and saved to the directory passed to --cert-dir. - --tls-private-key-file string File containing x509 private key matching --tls-cert-file. - --version version[=true] Print version information and quit - --volume-plugin-dir string The full path of the directory in which to search for additional third party volume plugins (default "/usr/libexec/kubernetes/kubelet-plugins/volume/exec/") - --volume-stats-agg-period duration Specifies interval for kubelet to calculate and cache the volume disk usage for all pods and volumes. To disable volume calculations, set to 0. (default 1m0s) +TaintNodesByCondition=true|false (ALPHA - default=false) + --file-check-frequency duration Duration between checking config files for new data (default 20s) + --google-json-key string The Google Cloud Platform Service Account JSON Key to use for authentication. + --hairpin-mode string How should the kubelet setup hairpin NAT. This allows endpoints of a Service to loadbalance back to themselves if they should try to access their own Service. Valid values are "promiscuous-bridge", "hairpin-veth" and "none". (default "promiscuous-bridge") + --healthz-bind-address ip The IP address for the healthz server to serve on. (set to 0.0.0.0 for all interfaces) (default 127.0.0.1) + --healthz-port int32 The port of the localhost healthz endpoint (set to 0 to disable) (default 10248) + --host-ipc-sources stringSlice Comma-separated list of sources from which the Kubelet allows pods to use the host ipc namespace. (default [*]) + --host-network-sources stringSlice Comma-separated list of sources from which the Kubelet allows pods to use of host network. (default [*]) + --host-pid-sources stringSlice Comma-separated list of sources from which the Kubelet allows pods to use the host pid namespace. (default [*]) + --hostname-override string If non-empty, will use this string as identification instead of the actual hostname. + --http-check-frequency duration Duration between checking http for new data (default 20s) + --image-gc-high-threshold int32 The percent of disk usage after which image garbage collection is always run. (default 85) + --image-gc-low-threshold int32 The percent of disk usage before which image garbage collection is never run. Lowest disk usage to garbage collect to. (default 80) + --image-pull-progress-deadline duration If no pulling progress is made before this deadline, the image pulling will be cancelled. (default 1m0s) + --image-service-endpoint string [Experimental] The endpoint of remote image service. If not specified, it will be the same with container-runtime-endpoint by default. Currently unix socket is supported on Linux, and tcp is supported on windows. Examples:'unix:///var/run/dockershim.sock', 'tcp://localhost:3735' + --init-config-dir string The Kubelet will look in this directory for the init configuration. The path may be absolute or relative; relative paths start at the Kubelet's current working directory. Omit this argument to use the built-in default configuration values. Presently, you must also enable the DynamicKubeletConfig feature gate to pass this flag. + --iptables-drop-bit int32 The bit of the fwmark space to mark packets for dropping. Must be within the range [0, 31]. (default 15) + --iptables-masquerade-bit int32 The bit of the fwmark space to mark packets for SNAT. Must be within the range [0, 31]. Please match this parameter with corresponding parameter in kube-proxy. (default 14) + --kube-api-burst int32 Burst to use while talking with kubernetes apiserver (default 10) + --kube-api-content-type string Content type of requests sent to apiserver. (default "application/vnd.kubernetes.protobuf") + --kube-api-qps int32 QPS to use while talking with kubernetes apiserver (default 5) + --kube-reserved mapStringString A set of ResourceName=ResourceQuantity (e.g. cpu=200m,memory=500Mi, storage=1Gi) pairs that describe resources reserved for kubernetes system components. Currently cpu, memory and local storage for root file system are supported. See http://kubernetes.io/docs/user-guide/compute-resources for more detail. [default=none] + --kube-reserved-cgroup string Absolute name of the top level cgroup that is used to manage kubernetes components for which compute resources were reserved via '--kube-reserved' flag. Ex. '/kube-reserved'. [default=''] + --kubeconfig string Path to a kubeconfig file, specifying how to connect to the API server. (default "/var/lib/kubelet/kubeconfig") + --kubelet-cgroups string Optional absolute name of cgroups to create and run the Kubelet in. + --lock-file string The path to file for kubelet to use as a lock file. + --make-iptables-util-chains If true, kubelet will ensure iptables utility rules are present on host. (default true) + --manifest-url string URL for accessing the container manifest + --manifest-url-header string HTTP header to use when accessing the manifest URL, with the key separated from the value with a ':', as in 'key:value' + --max-open-files int Number of files that can be opened by Kubelet process. (default 1000000) + --max-pods int32 Number of Pods that can run on this Kubelet. (default 110) + --minimum-image-ttl-duration duration Minimum age for an unused image before it is garbage collected. Examples: '300ms', '10s' or '2h45m'. (default 2m0s) + --network-plugin string The name of the network plugin to be invoked for various events in kubelet/pod lifecycle + --network-plugin-mtu int32 The MTU to be passed to the network plugin, to override the default. Set to 0 to use the default 1460 MTU. + --node-ip string IP address of the node. If set, kubelet will use this IP address for the node + --node-labels mapStringString Labels to add when registering the node in the cluster. Labels must be key=value pairs separated by ','. + --node-status-update-frequency duration Specifies how often kubelet posts node status to master. Note: be cautious when changing the constant, it must work with nodeMonitorGracePeriod in nodecontroller. (default 10s) + --oom-score-adj int32 The oom-score-adj value for kubelet process. Values must be within the range [-1000, 1000] (default -999) + --pod-cidr string The CIDR to use for pod IP addresses, only used in standalone mode. In cluster mode, this is obtained from the master. + --pod-infra-container-image string The image whose network/ipc namespaces containers in each pod will use. (default "gcr.io/google_containers/pause-amd64:3.0") + --pod-manifest-path string Path to to the directory containing pod manifest files to run, or the path to a single pod manifest file. Files starting with dots will be ignored. + --pods-per-core int32 Number of Pods per core that can run on this Kubelet. The total number of Pods on this Kubelet cannot exceed max-pods, so max-pods will be used if this calculation results in a larger number of Pods allowed on the Kubelet. A value of 0 disables this limit. + --port int32 The port for the Kubelet to serve on. (default 10250) + --protect-kernel-defaults Default kubelet behaviour for kernel tuning. If set, kubelet errors if any of kernel tunables is different than kubelet defaults. + --provider-id string Unique identifier for identifying the node in a machine database, i.e cloudprovider + --read-only-port int32 The read-only port for the Kubelet to serve on with no authentication/authorization (set to 0 to disable) (default 10255) + --really-crash-for-testing If true, when panics occur crash. Intended for testing. + --register-node Register the node with the apiserver. If --kubeconfig is not provided, this flag is irrelevant, as the Kubelet won't have an apiserver to register with. Default=true. (default true) + --register-with-taints []api.Taint Register the node with the given list of taints (comma separated "=:"). No-op if register-node is false. + --registry-burst int32 Maximum size of a bursty pulls, temporarily allows pulls to burst to this number, while still not exceeding registry-qps. Only used if --registry-qps > 0 (default 10) + --registry-qps int32 If > 0, limit registry pull QPS to this value. If 0, unlimited. (default 5) + --resolv-conf string Resolver configuration file used as the basis for the container DNS resolution configuration. (default "/etc/resolv.conf") + --rkt-api-endpoint string The endpoint of the rkt API service to communicate with. Only used if --container-runtime='rkt'. (default "localhost:15441") + --rkt-path string Path of rkt binary. Leave empty to use the first rkt in $PATH. Only used if --container-runtime='rkt'. + --root-dir string Directory path for managing kubelet files (volume mounts,etc). (default "/var/lib/kubelet") + --rotate-certificates Auto rotate the kubelet client certificates by requesting new certificates from the kube-apiserver when the certificate expiration approaches. + --runonce If true, exit after spawning pods from local manifests or remote urls. Exclusive with --enable-server + --runtime-cgroups string Optional absolute name of cgroups to create and run the runtime in. + --runtime-request-timeout duration Timeout of all runtime requests except long running request - pull, logs, exec and attach. When timeout exceeded, kubelet will cancel the request, throw out an error and retry later. (default 2m0s) + --seccomp-profile-root string Directory path for seccomp profiles. (default "/var/lib/kubelet/seccomp") + --serialize-image-pulls Pull images one at a time. We recommend *not* changing the default value on nodes that run docker daemon with version < 1.9 or an Aufs storage backend. Issue #10959 has more details. (default true) + --streaming-connection-idle-timeout duration Maximum time a streaming connection can be idle before the connection is automatically closed. 0 indicates no timeout. Example: '5m' (default 4h0m0s) + --sync-frequency duration Max period between synchronizing running containers and config (default 1m0s) + --system-cgroups / Optional absolute name of cgroups in which to place all non-kernel processes that are not already inside a cgroup under /. Empty for no container. Rolling back the flag requires a reboot. + --system-reserved mapStringString A set of ResourceName=ResourceQuantity (e.g. cpu=200m,memory=500Mi) pairs that describe resources reserved for non-kubernetes components. Currently only cpu and memory are supported. See http://kubernetes.io/docs/user-guide/compute-resources for more detail. [default=none] + --system-reserved-cgroup string Absolute name of the top level cgroup that is used to manage non-kubernetes components for which compute resources were reserved via '--system-reserved' flag. Ex. '/system-reserved'. [default=''] + --tls-cert-file string File containing x509 Certificate used for serving HTTPS (with intermediate certs, if any, concatenated after server cert). If --tls-cert-file and --tls-private-key-file are not provided, a self-signed certificate and key are generated for the public address and saved to the directory passed to --cert-dir. + --tls-private-key-file string File containing x509 private key matching --tls-cert-file. + --version version[=true] Print version information and quit + --volume-plugin-dir string The full path of the directory in which to search for additional third party volume plugins (default "/usr/libexec/kubernetes/kubelet-plugins/volume/exec/") + --volume-stats-agg-period duration Specifies interval for kubelet to calculate and cache the volume disk usage for all pods and volumes. To disable volume calculations, set to 0. (default 1m0s) ``` -###### Auto generated by spf13/cobra on 11-Jul-2017 +###### Auto generated by spf13/cobra on 27-Sep-2017 diff --git a/docs/reference/federation/extensions/v1beta1/definitions.html b/docs/reference/federation/extensions/v1beta1/definitions.html index 24da7f55d8d05..e91d3c54f6efb 100755 --- a/docs/reference/federation/extensions/v1beta1/definitions.html +++ b/docs/reference/federation/extensions/v1beta1/definitions.html @@ -421,7 +421,7 @@

v1beta1.DeploymentStatus

- + @@ -470,7 +470,7 @@

v1beta1.DeploymentStatus

unavailableReplicas

-

Total number of unavailable pods targeted by this deployment.

+

Total number of unavailable pods targeted by this deployment. This is the total number of pods that are still required for the deployment to have 100% available capacity. They may either be pods that are running but not yet available or pods that still have not been created.

false

integer (int32)

@@ -486,7 +486,7 @@

v1beta1.DeploymentStatus

collisionCount

Count of hash collisions for the Deployment. The Deployment controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ReplicaSet.

false

-

integer (int64)

+

integer (int32)

@@ -504,7 +504,7 @@

v1.APIResourceList

- + @@ -559,7 +559,7 @@

v1.Affinity

- + @@ -607,7 +607,7 @@

v1beta1.DaemonSetStatus

- + @@ -679,7 +679,7 @@

v1beta1.DaemonSetStatus

collisionCount

Count of hash collisions for the DaemonSet. The DaemonSet controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ControllerRevision.

false

-

integer (int64)

+

integer (int32)

@@ -697,7 +697,7 @@

v1.NodeSelectorTerm

- + @@ -731,7 +731,7 @@

v1.Preconditions

- + @@ -765,7 +765,7 @@

v1.ObjectFieldSelector

- + @@ -806,7 +806,7 @@

v1.SELinuxOptions

- + @@ -861,7 +861,7 @@

v1beta1.IngressSpec

- + @@ -909,7 +909,7 @@

v1.VolumeMount

- + @@ -949,9 +949,20 @@

v1.VolumeMount

string

+ +

mountPropagation

+

mountPropagation determines how mounts are propagated from the host to container and the other way around. When not set, MountPropagationHostToContainer is used. This field is alpha in 1.8 and can be reworked or removed in a future release.

+

false

+

v1.MountPropagationMode

+ + + +
+

v1.MountPropagationMode

+

v1.DownwardAPIProjection

@@ -964,7 +975,7 @@

v1.DownwardAPIProjection

- + @@ -998,7 +1009,7 @@

v1.LabelSelector

- + @@ -1039,7 +1050,7 @@

v1beta1.IngressBackend

- + @@ -1080,7 +1091,7 @@

v1beta1.ReplicaSetList

- + @@ -1135,7 +1146,7 @@

v1.CephFSVolumeSource

- + @@ -1204,7 +1215,7 @@

v1beta1.IngressStatus

- + @@ -1238,7 +1249,7 @@

v1.DownwardAPIVolumeSource

- + @@ -1279,7 +1290,7 @@

v1beta1.ReplicaSetCondition

- + @@ -1344,7 +1355,7 @@

v1.GCEPersistentDiskVolumeSource

- + @@ -1399,7 +1410,7 @@

v1beta1.RollingUpdateDeployment

- + @@ -1440,7 +1451,7 @@

v1beta1.HTTPIngressRuleValue

- + @@ -1477,7 +1488,7 @@

v1.ConfigMapVolumeSource

- + @@ -1532,7 +1543,7 @@

v1.GitRepoVolumeSource

- + @@ -1583,7 +1594,7 @@

v1.SecretEnvSource

- + @@ -1624,7 +1635,7 @@

v1.PortworxVolumeSource

- + @@ -1672,7 +1683,7 @@

v1.Capabilities

- + @@ -1713,7 +1724,7 @@

v1.Initializer

- + @@ -1747,7 +1758,7 @@

v1.LocalObjectReference

- + @@ -1781,7 +1792,7 @@

v1.ProjectedVolumeSource

- + @@ -1822,7 +1833,7 @@

v1.ExecAction

- + @@ -1856,7 +1867,7 @@

v1beta1.RollingUpdateDaemonSet

- + @@ -1890,7 +1901,7 @@

v1.ObjectMeta

- + @@ -2045,7 +2056,7 @@

v1beta1.ReplicaSetSpec

- + @@ -2092,7 +2103,7 @@

v1beta1.ReplicaSetSpec

v1beta1.Deployment

-

Deployment enables declarative updates for Pods and ReplicaSets.

+

DEPRECATED - This group version of Deployment is deprecated by apps/v1beta2/Deployment. See the release notes for more information. Deployment enables declarative updates for Pods and ReplicaSets.

@@ -2100,7 +2111,7 @@

v1beta1.Deployment

-+ @@ -2162,7 +2173,7 @@

v1beta1.DaemonSetSpec

-+ @@ -2235,7 +2246,7 @@

v1.AzureFileVolumeSource

-+ @@ -2283,7 +2294,7 @@

v1.ISCSIVolumeSource

-+ @@ -2365,6 +2376,13 @@

v1.ISCSIVolumeSource

+ + + + + + +

v1.LocalObjectReference

initiatorName

Custom iSCSI initiator name. If initiatorName is specified with iscsiInterface simultaneously, new iSCSI interface <target portal>:<volume name> will be created for the connection.

false

string

@@ -2380,7 +2398,7 @@

v1beta1.IngressList

- + @@ -2435,7 +2453,7 @@

v1.EmptyDirVolumeSource

- + @@ -2476,7 +2494,7 @@

v1beta1.ScaleSpec

- + @@ -2510,7 +2528,7 @@

v1.PodAffinityTerm

- + @@ -2558,7 +2576,7 @@

v1.EnvFromSource

- + @@ -2606,7 +2624,7 @@

v1.PodAffinity

- + @@ -2620,7 +2638,7 @@

v1.PodAffinity

requiredDuringSchedulingIgnoredDuringExecution

-

NOT YET IMPLEMENTED. TODO: Uncomment field once it is implemented. If the affinity requirements specified by this field are not met at scheduling time, the pod will not be scheduled onto the node. If the affinity requirements specified by this field cease to be met at some point during pod execution (e.g. due to a pod label update), the system will try to eventually evict the pod from its node. When there are multiple elements, the lists of nodes corresponding to each podAffinityTerm are intersected, i.e. all terms must be satisfied. RequiredDuringSchedulingRequiredDuringExecution []PodAffinityTerm json:"requiredDuringSchedulingRequiredDuringExecution,omitempty" If the affinity requirements specified by this field are not met at scheduling time, the pod will not be scheduled onto the node. If the affinity requirements specified by this field cease to be met at some point during pod execution (e.g. due to a pod label update), the system may or may not try to eventually evict the pod from its node. When there are multiple elements, the lists of nodes corresponding to each podAffinityTerm are intersected, i.e. all terms must be satisfied.

+

If the affinity requirements specified by this field are not met at scheduling time, the pod will not be scheduled onto the node. If the affinity requirements specified by this field cease to be met at some point during pod execution (e.g. due to a pod label update), the system may or may not try to eventually evict the pod from its node. When there are multiple elements, the lists of nodes corresponding to each podAffinityTerm are intersected, i.e. all terms must be satisfied.

false

v1.PodAffinityTerm array

@@ -2647,7 +2665,7 @@

v1.FlockerVolumeSource

- + @@ -2688,7 +2706,7 @@

v1.PersistentVolumeClaimVolumeSou - + @@ -2729,7 +2747,7 @@

v1.ListMeta

- + @@ -2743,7 +2761,7 @@

v1.ListMeta

selfLink

-

SelfLink is a URL representing this object. Populated by the system. Read-only.

+

selfLink is a URL representing this object. Populated by the system. Read-only.

false

string

@@ -2755,19 +2773,29 @@

v1.ListMeta

string

+ +

continue

+

continue may be set if the user set a limit on the number of items returned, and indicates that the server has more data available. The value is opaque and may be used to issue another request to the endpoint that served this list to retrieve the next set of available objects. Continuing a list may not be possible if the server configuration has changed or more than a few minutes have passed. The resourceVersion field returned when using this continue value will be identical to the value in the first response.

+

false

+

string

+ +

v1beta1.RollbackConfig

+
+

DEPRECATED.

+
-+ @@ -2804,7 +2832,7 @@

v1.SecretVolumeSource

-+ @@ -2859,7 +2887,7 @@

v1.FlexVolumeSource

-+ @@ -2921,7 +2949,7 @@

v1.EnvVarSource

-+ @@ -2942,7 +2970,7 @@

v1.EnvVarSource

- + @@ -2976,7 +3004,7 @@

v1.LoadBalancerIngress

-+ @@ -3017,7 +3045,7 @@

v1.AzureDiskVolumeSource

-+ @@ -3086,7 +3114,7 @@

v1.KeyToPath

-+ @@ -3131,7 +3159,7 @@

v1beta1.DaemonSetUpdateStrategy

-+ @@ -3172,7 +3200,7 @@

v1.VsphereVirtualDiskVolumeSource

-+ @@ -3227,7 +3255,7 @@

v1.DeleteOptions

-+ @@ -3296,7 +3324,7 @@

v1beta1.DaemonSetList

-+ @@ -3351,7 +3379,7 @@

v1.Volume

-+ @@ -3574,7 +3602,7 @@

v1.ResourceFieldSelector

-+ @@ -3622,7 +3650,7 @@

v1.VolumeProjection

-+ @@ -3670,7 +3698,7 @@

v1.Probe

-+ @@ -3753,7 +3781,7 @@

v1.WeightedPodAffinityTerm

-+ @@ -3794,7 +3822,7 @@

v1beta1.DeploymentSpec

-+ @@ -3857,14 +3885,14 @@

v1beta1.DeploymentSpec

- + - + @@ -3884,7 +3912,7 @@

v1.SecretKeySelector

-+ @@ -3936,7 +3964,7 @@

v1.DownwardAPIVolumeFile

-+ @@ -3991,7 +4019,7 @@

v1.PodSpec

-+ @@ -4152,7 +4180,7 @@

v1.PodSpec

- + @@ -4193,7 +4221,7 @@

v1.ContainerPort

-+ @@ -4255,7 +4283,7 @@

v1.Lifecycle

-+ @@ -4296,7 +4324,7 @@

v1.GlusterfsVolumeSource

-+ @@ -4344,7 +4372,7 @@

v1.Handler

-+ @@ -4392,7 +4420,7 @@

v1.Toleration

-+ @@ -4454,7 +4482,7 @@

v1beta1.IngressTLS

-+ @@ -4495,7 +4523,7 @@

v1.StatusCause

-+ @@ -4547,7 +4575,7 @@

v1beta1.Scale

-+ @@ -4609,7 +4637,7 @@

v1.RBDVolumeSource

-+ @@ -4695,7 +4723,7 @@

v1.ConfigMapProjection

-+ @@ -4743,7 +4771,7 @@

v1.PhotonPersistentDiskVolumeSourc

-+ @@ -4784,7 +4812,7 @@

v1.ScaleIOVolumeSource

-+ @@ -4869,6 +4897,10 @@

v1.ScaleIOVolumeSource

resourceFieldRef

Selects a resource of the container: only resources limits and requests (limits.cpu, limits.memory, requests.cpu and requests.memory) are currently supported.

Selects a resource of the container: only resources limits and requests (limits.cpu, limits.memory, limits.ephemeral-storage, requests.cpu, requests.memory and requests.ephemeral-storage) are currently supported.

false

v1.ResourceFieldSelector

rollbackTo

The config this deployment is rolling back to. Will be cleared after rollback is done.

DEPRECATED. The config this deployment is rolling back to. Will be cleared after rollback is done.

false

v1beta1.RollbackConfig

progressDeadlineSeconds

The maximum time in seconds for a deployment to make progress before it is considered to be failed. The deployment controller will continue to process failed deployments and a condition with a ProgressDeadlineExceeded reason will be surfaced in the deployment status. Once autoRollback is implemented, the deployment controller will automatically rollback failed deployments. Note that progress will not be estimated during the time a deployment is paused. This is not set by default.

The maximum time in seconds for a deployment to make progress before it is considered to be failed. The deployment controller will continue to process failed deployments and a condition with a ProgressDeadlineExceeded reason will be surfaced in the deployment status. Note that progress will not be estimated during the time a deployment is paused. This is not set by default.

false

integer (int32)

tolerations

If specified, the pod’s tolerations. More info: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/

If specified, the pod’s tolerations.

false

v1.Toleration array
+
+
+

v1.HostPathType

+

v1.Initializers

@@ -4881,7 +4913,7 @@

v1.Initializers

- + @@ -4922,7 +4954,7 @@

v1.Status

- + @@ -5005,7 +5037,7 @@

v1beta1.ScaleStatus

- + @@ -5053,7 +5085,7 @@

v1.NFSVolumeSource

- + @@ -5101,7 +5133,7 @@

v1beta1.DeploymentList

- + @@ -5148,7 +5180,7 @@

v1beta1.DeploymentList

v1beta1.DeploymentRollback

-

DeploymentRollback stores the information required to rollback a deployment.

+

DEPRECATED. DeploymentRollback stores the information required to rollback a deployment.

@@ -5156,7 +5188,7 @@

v1beta1.DeploymentRollback

-+ @@ -5218,7 +5250,7 @@

v1.HTTPHeader

-+ @@ -5259,7 +5291,7 @@

v1.FCVolumeSource

-+ @@ -5273,15 +5305,15 @@

v1.FCVolumeSource

- - + + - - + + @@ -5299,6 +5331,13 @@

v1.FCVolumeSource

+ + + + + + +

targetWWNs

Required: FC target worldwide names (WWNs)

true

Optional: FC target worldwide names (WWNs)

false

string array

lun

Required: FC target lun number

true

Optional: FC target lun number

false

integer (int32)

boolean

false

wwids

Optional: FC volume world wide identifiers (wwids) Either wwids or combination of targetWWNs and lun must be set, but not both simultaneously.

false

string array
@@ -5314,7 +5353,7 @@

v1.PodAntiAffinity

- + @@ -5328,7 +5367,7 @@

v1.PodAntiAffinity

requiredDuringSchedulingIgnoredDuringExecution

-

NOT YET IMPLEMENTED. TODO: Uncomment field once it is implemented. If the anti-affinity requirements specified by this field are not met at scheduling time, the pod will not be scheduled onto the node. If the anti-affinity requirements specified by this field cease to be met at some point during pod execution (e.g. due to a pod label update), the system will try to eventually evict the pod from its node. When there are multiple elements, the lists of nodes corresponding to each podAffinityTerm are intersected, i.e. all terms must be satisfied. RequiredDuringSchedulingRequiredDuringExecution []PodAffinityTerm json:"requiredDuringSchedulingRequiredDuringExecution,omitempty" If the anti-affinity requirements specified by this field are not met at scheduling time, the pod will not be scheduled onto the node. If the anti-affinity requirements specified by this field cease to be met at some point during pod execution (e.g. due to a pod label update), the system may or may not try to eventually evict the pod from its node. When there are multiple elements, the lists of nodes corresponding to each podAffinityTerm are intersected, i.e. all terms must be satisfied.

+

If the anti-affinity requirements specified by this field are not met at scheduling time, the pod will not be scheduled onto the node. If the anti-affinity requirements specified by this field cease to be met at some point during pod execution (e.g. due to a pod label update), the system may or may not try to eventually evict the pod from its node. When there are multiple elements, the lists of nodes corresponding to each podAffinityTerm are intersected, i.e. all terms must be satisfied.

false

v1.PodAffinityTerm array

@@ -5359,7 +5398,7 @@

v1beta1.DeploymentStrategy

- + @@ -5400,7 +5439,7 @@

v1.TCPSocketAction

- + @@ -5441,7 +5480,7 @@

v1beta1.IngressRule

- + @@ -5487,7 +5526,7 @@

v1.HTTPGetAction

- + @@ -5549,7 +5588,7 @@

v1.StatusDetails

- + @@ -5598,7 +5637,7 @@

v1.StatusDetails

retryAfterSeconds

-

If specified, the time in seconds before the operation should be retried.

+

If specified, the time in seconds before the operation should be retried. Some errors may indicate the client must take an alternate action - for those errors this field may indicate how long to wait before taking the alternate action.

false

integer (int32)

@@ -5618,7 +5657,7 @@

v1.LoadBalancerStatus

- + @@ -5652,7 +5691,7 @@

v1.Container

- + @@ -5673,8 +5712,8 @@

v1.Container

image

-

Docker image name. More info: https://kubernetes.io/docs/concepts/containers/images

-

true

+

Docker image name. More info: https://kubernetes.io/docs/concepts/containers/images This field is optional to allow higher level config management to default or override container images in workload controllers like Deployments and StatefulSets.

+

false

string

@@ -5778,7 +5817,7 @@

v1.Container

securityContext

-

Security options the pod should run with. More info: https://kubernetes.io/docs/concepts/policy/security-context/ More info: https://git.k8s.io/community/contributors/design-proposals/auth/security_context.md

+

Security options the pod should run with. More info: https://kubernetes.io/docs/concepts/policy/security-context/ More info: https://git.k8s.io/community/contributors/design-proposals/security_context.md

false

v1.SecurityContext

@@ -5819,7 +5858,7 @@

v1.PodSecurityContext

- + @@ -5883,7 +5922,7 @@

v1.OwnerReference

- + @@ -5952,7 +5991,7 @@

v1beta1.ReplicaSetStatus

- + @@ -6021,7 +6060,7 @@

v1.APIResource

- + @@ -6055,6 +6094,20 @@

v1.APIResource

false

+

group

+

group is the preferred group of the resource. Empty implies the group of the containing resource list. For subresources, this may have a different value, for example: Scale".

+

false

+

string

+ + + +

version

+

version is the preferred version of the resource. Empty implies the version of the containing resource list For subresources, this may have a different value, for example: v1 (while inside a v1beta1 version of the core resource’s group)".

+

false

+

string

+ + +

kind

kind is the kind for the resource (e.g. Foo is the kind for a resource foo)

true

@@ -6097,7 +6150,7 @@

v1.NodeSelectorRequirement

- + @@ -6137,7 +6190,7 @@

v1.NodeSelectorRequirement

v1beta1.ReplicaSet

-

ReplicaSet represents the configuration of a ReplicaSet.

+

DEPRECATED - This group version of ReplicaSet is deprecated by apps/v1beta2/ReplicaSet. See the release notes for more information. ReplicaSet represents the configuration of a ReplicaSet.

@@ -6145,7 +6198,7 @@

v1beta1.ReplicaSet

-+ @@ -6207,7 +6260,7 @@

v1.HostPathVolumeSource

-+ @@ -6221,11 +6274,18 @@

v1.HostPathVolumeSource

- + + + + + + + +

path

Path of the directory on the host. More info: https://kubernetes.io/docs/concepts/storage/volumes#hostpath

Path of the directory on the host. If the path is a symlink, it will follow the link to the real path. More info: https://kubernetes.io/docs/concepts/storage/volumes#hostpath

true

string

type

Type for HostPath Volume Defaults to "" More info: https://kubernetes.io/docs/concepts/storage/volumes#hostpath

false

v1.HostPathType
@@ -6244,7 +6304,7 @@

v1.SecretProjection

- + @@ -6284,7 +6344,7 @@

v1.SecretProjection

v1beta1.DaemonSet

-

DaemonSet represents the configuration of a daemon set.

+

DEPRECATED - This group version of DaemonSet is deprecated by apps/v1beta2/DaemonSet. See the release notes for more information. DaemonSet represents the configuration of a daemon set.

@@ -6292,7 +6352,7 @@

v1beta1.DaemonSet

-+ @@ -6354,7 +6414,7 @@

v1.CinderVolumeSource

-+ @@ -6402,7 +6462,7 @@

v1.SecurityContext

-+ @@ -6456,6 +6516,13 @@

v1.SecurityContext

+ + + + + + +

boolean

false

allowPrivilegeEscalation

AllowPrivilegeEscalation controls whether a process can gain more privileges than its parent process. This bool directly controls if the no_new_privs flag will be set on the container process. AllowPrivilegeEscalation is true always when the container is: 1) run as Privileged 2) has CAP_SYS_ADMIN

false

boolean

false

@@ -6474,7 +6541,7 @@

v1.AWSElasticBlockStoreVolumeSourc - + @@ -6529,7 +6596,7 @@

v1.QuobyteVolumeSource

- + @@ -6588,7 +6655,7 @@

v1.WatchEvent

- + @@ -6629,7 +6696,7 @@

v1.LabelSelectorRequirement

- + @@ -6650,7 +6717,7 @@

v1.LabelSelectorRequirement

operator

-

operator represents a key’s relationship to a set of values. Valid operators ard In, NotIn, Exists and DoesNotExist.

+

operator represents a key’s relationship to a set of values. Valid operators are In, NotIn, Exists and DoesNotExist.

true

string

@@ -6677,7 +6744,7 @@

v1.EnvVar

- + @@ -6725,7 +6792,7 @@

v1.ResourceRequirements

- + @@ -6766,7 +6833,7 @@

v1.HostAlias

- + @@ -6807,7 +6874,7 @@

v1.PodTemplateSpec

- + @@ -6848,7 +6915,7 @@

v1.NodeSelector

- + @@ -6888,7 +6955,7 @@

v1beta1.DeploymentCondition

- + @@ -6960,7 +7027,7 @@

v1.ConfigMapEnvSource

- + @@ -7001,7 +7068,7 @@

v1.StorageOSVolumeSource

- + @@ -7063,7 +7130,7 @@

v1.NodeAffinity

- + @@ -7108,7 +7175,7 @@

v1.PreferredSchedulingTerm

- + @@ -7149,7 +7216,7 @@

v1.ConfigMapKeySelector

- + @@ -7197,7 +7264,7 @@

v1beta1.HTTPIngressPath

- + @@ -7238,7 +7305,7 @@

v1beta1.Ingress

- + diff --git a/docs/reference/federation/extensions/v1beta1/operations.html b/docs/reference/federation/extensions/v1beta1/operations.html index 7d24e9285f2e2..7a68f805edea7 100755 --- a/docs/reference/federation/extensions/v1beta1/operations.html +++ b/docs/reference/federation/extensions/v1beta1/operations.html @@ -384,7 +384,7 @@

Responses

- + @@ -462,7 +462,7 @@

Parameters

- + @@ -531,6 +531,23 @@

Parameters

integer (int32)

+ +

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + @@ -541,7 +558,7 @@

Responses

- + @@ -619,7 +636,7 @@

Parameters

- + @@ -688,6 +705,23 @@

Parameters

integer (int32)

+ +

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + @@ -698,7 +732,7 @@

Responses

- + @@ -776,7 +810,7 @@

Parameters

- + @@ -845,6 +879,23 @@

Parameters

integer (int32)

+ +

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + @@ -855,7 +906,7 @@

Responses

- + @@ -933,7 +984,7 @@

Parameters

- + @@ -1003,6 +1054,23 @@

Parameters

+

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + +

PathParameter

namespace

object name and auth scope, such as for teams and projects

@@ -1020,7 +1088,7 @@

Responses

- + @@ -1098,7 +1166,7 @@

Parameters

- + @@ -1168,6 +1236,23 @@

Parameters

+

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + +

PathParameter

namespace

object name and auth scope, such as for teams and projects

@@ -1185,7 +1270,7 @@

Responses

- + @@ -1257,7 +1342,7 @@

Parameters

- + @@ -1304,7 +1389,7 @@

Responses

- + @@ -1376,7 +1461,7 @@

Parameters

- + @@ -1439,7 +1524,7 @@

Responses

- + @@ -1511,7 +1596,7 @@

Parameters

- + @@ -1566,7 +1651,7 @@

Responses

- + @@ -1638,7 +1723,7 @@

Parameters

- + @@ -1717,7 +1802,7 @@

Responses

- + @@ -1789,7 +1874,7 @@

Parameters

- + @@ -1844,7 +1929,7 @@

Responses

- + @@ -1922,7 +2007,7 @@

Parameters

- + @@ -1969,7 +2054,7 @@

Responses

- + @@ -2041,7 +2126,7 @@

Parameters

- + @@ -2096,7 +2181,7 @@

Responses

- + @@ -2168,7 +2253,7 @@

Parameters

- + @@ -2223,7 +2308,7 @@

Responses

- + @@ -2301,7 +2386,7 @@

Parameters

- + @@ -2371,6 +2456,23 @@

Parameters

+

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + +

PathParameter

namespace

object name and auth scope, such as for teams and projects

@@ -2388,7 +2490,7 @@

Responses

- + @@ -2466,7 +2568,7 @@

Parameters

- + @@ -2536,6 +2638,23 @@

Parameters

+

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + +

PathParameter

namespace

object name and auth scope, such as for teams and projects

@@ -2553,7 +2672,7 @@

Responses

- + @@ -2625,7 +2744,7 @@

Parameters

- + @@ -2672,7 +2791,7 @@

Responses

- + @@ -2744,7 +2863,7 @@

Parameters

- + @@ -2807,7 +2926,7 @@

Responses

- + @@ -2879,7 +2998,7 @@

Parameters

- + @@ -2934,7 +3053,7 @@

Responses

- + @@ -3006,7 +3125,7 @@

Parameters

- + @@ -3085,7 +3204,7 @@

Responses

- + @@ -3157,7 +3276,7 @@

Parameters

- + @@ -3212,7 +3331,7 @@

Responses

- + @@ -3275,7 +3394,7 @@

Tags

-

create rollback of a DeploymentRollback

+

create rollback of a Deployment

POST /apis/extensions/v1beta1/namespaces/{namespace}/deployments/{name}/rollback
@@ -3290,7 +3409,7 @@

Parameters

- + @@ -3345,7 +3464,7 @@

Responses

- + @@ -3402,7 +3521,7 @@

Tags

-

read scale of the specified Scale

+

read scale of the specified Deployment

GET /apis/extensions/v1beta1/namespaces/{namespace}/deployments/{name}/scale
@@ -3417,7 +3536,7 @@

Parameters

- + @@ -3464,7 +3583,7 @@

Responses

- + @@ -3521,7 +3640,7 @@

Tags

-

replace scale of the specified Scale

+

replace scale of the specified Deployment

PUT /apis/extensions/v1beta1/namespaces/{namespace}/deployments/{name}/scale
@@ -3536,7 +3655,7 @@

Parameters

- + @@ -3591,7 +3710,7 @@

Responses

- + @@ -3648,7 +3767,7 @@

Tags

-

partially update scale of the specified Scale

+

partially update scale of the specified Deployment

PATCH /apis/extensions/v1beta1/namespaces/{namespace}/deployments/{name}/scale
@@ -3663,7 +3782,7 @@

Parameters

- + @@ -3718,7 +3837,7 @@

Responses

- + @@ -3796,7 +3915,7 @@

Parameters

- + @@ -3843,7 +3962,7 @@

Responses

- + @@ -3915,7 +4034,7 @@

Parameters

- + @@ -3970,7 +4089,7 @@

Responses

- + @@ -4042,7 +4161,7 @@

Parameters

- + @@ -4097,7 +4216,7 @@

Responses

- + @@ -4175,7 +4294,7 @@

Parameters

- + @@ -4245,6 +4364,23 @@

Parameters

+

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + +

PathParameter

namespace

object name and auth scope, such as for teams and projects

@@ -4262,7 +4398,7 @@

Responses

- + @@ -4340,7 +4476,7 @@

Parameters

- + @@ -4410,6 +4546,23 @@

Parameters

+

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + +

PathParameter

namespace

object name and auth scope, such as for teams and projects

@@ -4427,7 +4580,7 @@

Responses

- + @@ -4499,7 +4652,7 @@

Parameters

- + @@ -4546,7 +4699,7 @@

Responses

- + @@ -4618,7 +4771,7 @@

Parameters

- + @@ -4681,7 +4834,7 @@

Responses

- + @@ -4753,7 +4906,7 @@

Parameters

- + @@ -4808,7 +4961,7 @@

Responses

- + @@ -4880,7 +5033,7 @@

Parameters

- + @@ -4959,7 +5112,7 @@

Responses

- + @@ -5031,7 +5184,7 @@

Parameters

- + @@ -5086,7 +5239,7 @@

Responses

- + @@ -5164,7 +5317,7 @@

Parameters

- + @@ -5211,7 +5364,7 @@

Responses

- + @@ -5283,7 +5436,7 @@

Parameters

- + @@ -5338,7 +5491,7 @@

Responses

- + @@ -5410,7 +5563,7 @@

Parameters

- + @@ -5465,7 +5618,7 @@

Responses

- + @@ -5543,7 +5696,7 @@

Parameters

- + @@ -5613,6 +5766,23 @@

Parameters

+

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + +

PathParameter

namespace

object name and auth scope, such as for teams and projects

@@ -5630,7 +5800,7 @@

Responses

- + @@ -5708,7 +5878,7 @@

Parameters

- + @@ -5778,6 +5948,23 @@

Parameters

+

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + +

PathParameter

namespace

object name and auth scope, such as for teams and projects

@@ -5795,7 +5982,7 @@

Responses

- + @@ -5867,7 +6054,7 @@

Parameters

- + @@ -5914,7 +6101,7 @@

Responses

- + @@ -5986,7 +6173,7 @@

Parameters

- + @@ -6049,7 +6236,7 @@

Responses

- + @@ -6121,7 +6308,7 @@

Parameters

- + @@ -6176,7 +6363,7 @@

Responses

- + @@ -6248,7 +6435,7 @@

Parameters

- + @@ -6327,7 +6514,7 @@

Responses

- + @@ -6399,7 +6586,7 @@

Parameters

- + @@ -6454,7 +6641,7 @@

Responses

- + @@ -6517,7 +6704,7 @@

Tags

-

read scale of the specified Scale

+

read scale of the specified ReplicaSet

GET /apis/extensions/v1beta1/namespaces/{namespace}/replicasets/{name}/scale
@@ -6532,7 +6719,7 @@

Parameters

- + @@ -6579,7 +6766,7 @@

Responses

- + @@ -6636,7 +6823,7 @@

Tags

-

replace scale of the specified Scale

+

replace scale of the specified ReplicaSet

PUT /apis/extensions/v1beta1/namespaces/{namespace}/replicasets/{name}/scale
@@ -6651,7 +6838,7 @@

Parameters

- + @@ -6706,7 +6893,7 @@

Responses

- + @@ -6763,7 +6950,7 @@

Tags

-

partially update scale of the specified Scale

+

partially update scale of the specified ReplicaSet

PATCH /apis/extensions/v1beta1/namespaces/{namespace}/replicasets/{name}/scale
@@ -6778,7 +6965,7 @@

Parameters

- + @@ -6833,7 +7020,7 @@

Responses

- + @@ -6911,7 +7098,7 @@

Parameters

- + @@ -6958,7 +7145,7 @@

Responses

- + @@ -7030,7 +7217,7 @@

Parameters

- + @@ -7085,7 +7272,7 @@

Responses

- + @@ -7157,7 +7344,7 @@

Parameters

- + @@ -7212,7 +7399,7 @@

Responses

- + @@ -7290,7 +7477,7 @@

Parameters

- + @@ -7359,6 +7546,23 @@

Parameters

integer (int32)

+ +

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + @@ -7369,7 +7573,7 @@

Responses

- + @@ -7447,7 +7651,7 @@

Parameters

- + @@ -7516,6 +7720,23 @@

Parameters

integer (int32)

+ +

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + @@ -7526,7 +7747,7 @@

Responses

- + @@ -7604,7 +7825,7 @@

Parameters

- + @@ -7673,6 +7894,23 @@

Parameters

integer (int32)

+ +

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + @@ -7683,7 +7921,7 @@

Responses

- + @@ -7761,7 +7999,7 @@

Parameters

- + @@ -7830,6 +8068,23 @@

Parameters

integer (int32)

+ +

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + @@ -7840,7 +8095,7 @@

Responses

- + @@ -7918,7 +8173,7 @@

Parameters

- + @@ -7988,6 +8243,23 @@

Parameters

+

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + +

PathParameter

namespace

object name and auth scope, such as for teams and projects

@@ -8005,7 +8277,7 @@

Responses

- + @@ -8083,7 +8355,7 @@

Parameters

- + @@ -8153,6 +8425,23 @@

Parameters

+

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + +

PathParameter

namespace

object name and auth scope, such as for teams and projects

@@ -8178,7 +8467,7 @@

Responses

- + @@ -8256,7 +8545,7 @@

Parameters

- + @@ -8326,6 +8615,23 @@

Parameters

+

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + +

PathParameter

namespace

object name and auth scope, such as for teams and projects

@@ -8343,7 +8649,7 @@

Responses

- + @@ -8421,7 +8727,7 @@

Parameters

- + @@ -8491,6 +8797,23 @@

Parameters

+

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + +

PathParameter

namespace

object name and auth scope, such as for teams and projects

@@ -8516,7 +8839,7 @@

Responses

- + @@ -8594,7 +8917,7 @@

Parameters

- + @@ -8664,6 +8987,23 @@

Parameters

+

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + +

PathParameter

namespace

object name and auth scope, such as for teams and projects

@@ -8681,7 +9021,7 @@

Responses

- + @@ -8759,7 +9099,7 @@

Parameters

- + @@ -8829,6 +9169,23 @@

Parameters

+

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + +

PathParameter

namespace

object name and auth scope, such as for teams and projects

@@ -8854,7 +9211,7 @@

Responses

- + @@ -8932,7 +9289,7 @@

Parameters

- + @@ -9002,6 +9359,23 @@

Parameters

+

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + +

PathParameter

namespace

object name and auth scope, such as for teams and projects

@@ -9019,7 +9393,7 @@

Responses

- + @@ -9097,7 +9471,7 @@

Parameters

- + @@ -9167,6 +9541,23 @@

Parameters

+

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + +

PathParameter

namespace

object name and auth scope, such as for teams and projects

@@ -9192,7 +9583,7 @@

Responses

- + @@ -9270,7 +9661,7 @@

Parameters

- + @@ -9339,6 +9730,23 @@

Parameters

integer (int32)

+ +

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + @@ -9349,7 +9757,7 @@

Responses

- + diff --git a/docs/reference/federation/federation/v1beta1/definitions.html b/docs/reference/federation/federation/v1beta1/definitions.html index 3e88e4c94f2ae..6c1e9bc11f490 100755 --- a/docs/reference/federation/federation/v1beta1/definitions.html +++ b/docs/reference/federation/federation/v1beta1/definitions.html @@ -397,7 +397,7 @@

v1.APIResourceList

- + @@ -458,7 +458,7 @@

v1.DeleteOptions

- + @@ -527,7 +527,7 @@

v1beta1.ServerAddressByClientCIDR - + @@ -568,7 +568,7 @@

v1beta1.ClusterList

- + @@ -623,7 +623,7 @@

v1.ListMeta

- + @@ -637,7 +637,7 @@

v1.ListMeta

selfLink

-

SelfLink is a URL representing this object. Populated by the system. Read-only.

+

selfLink is a URL representing this object. Populated by the system. Read-only.

false

string

@@ -649,6 +649,13 @@

v1.ListMeta

string

+ +

continue

+

continue may be set if the user set a limit on the number of items returned, and indicates that the server has more data available. The value is opaque and may be used to issue another request to the endpoint that served this list to retrieve the next set of available objects. Continuing a list may not be possible if the server configuration has changed or more than a few minutes have passed. The resourceVersion field returned when using this continue value will be identical to the value in the first response.

+

false

+

string

+ + @@ -664,7 +671,7 @@

v1.StatusDetails

- + @@ -713,7 +720,7 @@

v1.StatusDetails

retryAfterSeconds

-

If specified, the time in seconds before the operation should be retried.

+

If specified, the time in seconds before the operation should be retried. Some errors may indicate the client must take an alternate action - for those errors this field may indicate how long to wait before taking the alternate action.

false

integer (int32)

@@ -733,7 +740,7 @@

v1beta1.ClusterStatus

- + @@ -781,7 +788,7 @@

v1.Preconditions

- + @@ -815,7 +822,7 @@

v1.Initializers

- + @@ -856,7 +863,7 @@

v1.Initializer

- + @@ -890,7 +897,7 @@

v1.LocalObjectReference

- + @@ -924,7 +931,7 @@

v1.Status

- + @@ -1007,7 +1014,7 @@

v1beta1.ClusterSpec

- + @@ -1045,7 +1052,7 @@

v1.WatchEvent

- + @@ -1086,7 +1093,7 @@

v1beta1.ClusterCondition

- + @@ -1155,7 +1162,7 @@

v1.ObjectMeta

- + @@ -1310,7 +1317,7 @@

v1.OwnerReference

- + @@ -1379,7 +1386,7 @@

v1.APIResource

- + @@ -1413,6 +1420,20 @@

v1.APIResource

false

+

group

+

group is the preferred group of the resource. Empty implies the group of the containing resource list. For subresources, this may have a different value, for example: Scale".

+

false

+

string

+ + + +

version

+

version is the preferred version of the resource. Empty implies the version of the containing resource list For subresources, this may have a different value, for example: v1 (while inside a v1beta1 version of the core resource’s group)".

+

false

+

string

+ + +

kind

kind is the kind for the resource (e.g. Foo is the kind for a resource foo)

true

@@ -1459,7 +1480,7 @@

v1.StatusCause

- + @@ -1515,7 +1536,7 @@

v1beta1.Cluster

- + diff --git a/docs/reference/federation/federation/v1beta1/operations.html b/docs/reference/federation/federation/v1beta1/operations.html index 6dd2e9efaad41..6017273a212be 100755 --- a/docs/reference/federation/federation/v1beta1/operations.html +++ b/docs/reference/federation/federation/v1beta1/operations.html @@ -384,7 +384,7 @@

Responses

- + @@ -462,7 +462,7 @@

Parameters

- + @@ -531,6 +531,23 @@

Parameters

integer (int32)

+ +

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + @@ -541,7 +558,7 @@

Responses

- + @@ -619,7 +636,7 @@

Parameters

- + @@ -688,6 +705,23 @@

Parameters

integer (int32)

+ +

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + @@ -698,7 +732,7 @@

Responses

- + @@ -770,7 +804,7 @@

Parameters

- + @@ -809,7 +843,7 @@

Responses

- + @@ -881,7 +915,7 @@

Parameters

- + @@ -936,7 +970,7 @@

Responses

- + @@ -1008,7 +1042,7 @@

Parameters

- + @@ -1055,7 +1089,7 @@

Responses

- + @@ -1127,7 +1161,7 @@

Parameters

- + @@ -1198,7 +1232,7 @@

Responses

- + @@ -1270,7 +1304,7 @@

Parameters

- + @@ -1317,7 +1351,7 @@

Responses

- + @@ -1395,7 +1429,7 @@

Parameters

- + @@ -1442,7 +1476,7 @@

Responses

- + @@ -1514,7 +1548,7 @@

Parameters

- + @@ -1583,6 +1617,23 @@

Parameters

integer (int32)

+ +

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + @@ -1593,7 +1644,7 @@

Responses

- + @@ -1671,7 +1722,7 @@

Parameters

- + @@ -1741,6 +1792,23 @@

Parameters

+

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + +

PathParameter

name

name of the Cluster

@@ -1758,7 +1826,7 @@

Responses

- + diff --git a/docs/reference/federation/index.md b/docs/reference/federation/index.md index 81ace6743a573..30dbfe3070232 100644 --- a/docs/reference/federation/index.md +++ b/docs/reference/federation/index.md @@ -5,11 +5,11 @@ title: Federation API Reference Federation API server supports the following group versions: -* federation/v1beta1: [operations](https://htmlpreview.github.io/?https://github.com/kubernetes/kubernetes/blob/HEAD/federation/docs/api-reference/federation/v1beta1/operations.html), [model definitions](https://htmlpreview.github.io/?https://github.com/kubernetes/kubernetes/blob/HEAD/federation/docs/api-reference/federation/v1beta1/definitions.html) -* v1: [operations](https://htmlpreview.github.io/?https://github.com/kubernetes/kubernetes/blob/HEAD/federation/docs/api-reference/v1/operations.html), [model definitions](https://htmlpreview.github.io/?https://github.com/kubernetes/kubernetes/blob/HEAD/federation/docs/api-reference/v1/definitions.html) -* extensions/v1beta1: [operations](https://htmlpreview.github.io/?https://github.com/kubernetes/kubernetes/blob/HEAD/federation/docs/api-reference/extensions/v1beta1/operations.html), [model definitions](https://htmlpreview.github.io/?https://github.com/kubernetes/kubernetes/blob/HEAD/federation/docs/api-reference/extensions/v1beta1/definitions.html) +* federation/v1beta1: [operations](/docs/federation/api-reference/federation/v1beta1/operations.html), [model definitions](/docs/federation/api-reference/federation/v1beta1/definitions.html) +* v1: [operations](/docs/federation/api-reference/v1/operations.html), [model definitions](/docs/federation/api-reference/v1/definitions.html) +* extensions/v1beta1: [operations](/docs/federation/api-reference/extensions/v1beta1/operations.html), [model definitions](/docs/federation/api-reference/extensions/v1beta1/definitions.html) -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/federation/docs/api-reference/README.md?pixel)]() +[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/federation/api-reference/README.md?pixel)]() diff --git a/docs/reference/federation/v1/definitions.html b/docs/reference/federation/v1/definitions.html index 688adf2d2c38b..0870585fadfc7 100755 --- a/docs/reference/federation/v1/definitions.html +++ b/docs/reference/federation/v1/definitions.html @@ -421,7 +421,7 @@

v1.APIResourceList

- + @@ -476,7 +476,7 @@

v1.NamespaceList

- + @@ -531,7 +531,7 @@

v1.ListMeta

- + @@ -545,7 +545,7 @@

v1.ListMeta

selfLink

-

SelfLink is a URL representing this object. Populated by the system. Read-only.

+

selfLink is a URL representing this object. Populated by the system. Read-only.

false

string

@@ -557,6 +557,13 @@

v1.ListMeta

string

+ +

continue

+

continue may be set if the user set a limit on the number of items returned, and indicates that the server has more data available. The value is opaque and may be used to issue another request to the endpoint that served this list to retrieve the next set of available objects. Continuing a list may not be possible if the server configuration has changed or more than a few minutes have passed. The resourceVersion field returned when using this continue value will be identical to the value in the first response.

+

false

+

string

+ + @@ -572,7 +579,7 @@

v1.Namespace

- + @@ -634,7 +641,7 @@

v1.Initializers

- + @@ -675,7 +682,7 @@

v1.Preconditions

- + @@ -709,7 +716,7 @@

v1.Status

- + @@ -792,7 +799,7 @@

v1.ServiceStatus

- + @@ -826,7 +833,7 @@

v1.Secret

- + @@ -892,7 +899,7 @@

v1.WatchEvent

- + @@ -933,7 +940,7 @@

v1.Event

- + @@ -1037,7 +1044,7 @@

v1.LoadBalancerIngress

- + @@ -1082,7 +1089,7 @@

v1.NamespaceStatus

- + @@ -1096,7 +1103,7 @@

v1.NamespaceStatus

phase

-

Phase is the current lifecycle phase of the namespace. More info: https://git.k8s.io/community/contributors/design-proposals/architecture/namespaces.md#phases

+

Phase is the current lifecycle phase of the namespace. More info: https://git.k8s.io/community/contributors/design-proposals/namespaces.md#phases

false

string

@@ -1116,7 +1123,7 @@

v1.ServiceList

- + @@ -1171,7 +1178,7 @@

v1.NamespaceSpec

- + @@ -1185,7 +1192,7 @@

v1.NamespaceSpec

finalizers

-

Finalizers is an opaque list of values that must be empty to permanently remove object from storage. More info: https://git.k8s.io/community/contributors/design-proposals/architecture/namespaces.md#finalizers

+

Finalizers is an opaque list of values that must be empty to permanently remove object from storage. More info: https://git.k8s.io/community/contributors/design-proposals/namespaces.md#finalizers

false

v1.FinalizerName array

@@ -1205,7 +1212,7 @@

v1.Service

- + @@ -1273,7 +1280,7 @@

v1.ConfigMapList

- + @@ -1328,7 +1335,7 @@

v1.DeleteOptions

- + @@ -1397,7 +1404,7 @@

v1.StatusDetails

- + @@ -1446,7 +1453,7 @@

v1.StatusDetails

retryAfterSeconds

-

If specified, the time in seconds before the operation should be retried.

+

If specified, the time in seconds before the operation should be retried. Some errors may indicate the client must take an alternate action - for those errors this field may indicate how long to wait before taking the alternate action.

false

integer (int32)

@@ -1466,7 +1473,7 @@

v1.ConfigMap

- + @@ -1521,7 +1528,7 @@

v1.Initializer

- + @@ -1555,7 +1562,7 @@

v1.ObjectReference

- + @@ -1631,7 +1638,7 @@

v1.LoadBalancerStatus

- + @@ -1665,7 +1672,7 @@

v1.SecretList

- + @@ -1724,7 +1731,7 @@

v1.ServicePort

- + @@ -1786,7 +1793,7 @@

v1.OwnerReference

- + @@ -1855,7 +1862,7 @@

v1.ObjectMeta

- + @@ -2010,7 +2017,7 @@

v1.EventList

- + @@ -2053,6 +2060,40 @@

v1.EventList

+
+
+

v1.ClientIPConfig

+
+

ClientIPConfig represents the configurations of Client IP based session affinity.

+
+ +++++++ + + + + + + + + + + + + + + + + + + +
NameDescriptionRequiredSchemaDefault

timeoutSeconds

timeoutSeconds specifies the seconds of ClientIP type session sticky time. The value must be >0 && ⇐86400(for 1 day) if ServiceAffinity == "ClientIP". Default value is 10800(for 3 hours).

false

integer (int32)

+

v1.APIResource

@@ -2065,7 +2106,7 @@

v1.APIResource

- + @@ -2099,6 +2140,20 @@

v1.APIResource

false

+

group

+

group is the preferred group of the resource. Empty implies the group of the containing resource list. For subresources, this may have a different value, for example: Scale".

+

false

+

string

+ + + +

version

+

version is the preferred version of the resource. Empty implies the version of the containing resource list For subresources, this may have a different value, for example: v1 (while inside a v1beta1 version of the core resource’s group)".

+

false

+

string

+ + +

kind

kind is the kind for the resource (e.g. Foo is the kind for a resource foo)

true

@@ -2141,7 +2196,7 @@

v1.ServiceSpec

- + @@ -2230,6 +2285,20 @@

v1.ServiceSpec

integer (int32)

+ +

publishNotReadyAddresses

+

publishNotReadyAddresses, when set to true, indicates that DNS implementations must publish the notReadyAddresses of subsets for the Endpoints associated with the Service. The default value is false. The primary use case for setting this field is to use a StatefulSet’s Headless Service to propagate SRV records for its Pods without respect to their readiness for purpose of peer discovery. This field will replace the service.alpha.kubernetes.io/tolerate-unready-endpoints when that annotation is deprecated and all clients have been converted to use this field.

+

false

+

boolean

+

false

+ + +

sessionAffinityConfig

+

sessionAffinityConfig contains the configurations of session affinity.

+

false

+

v1.SessionAffinityConfig

+ + @@ -2245,7 +2314,7 @@

v1.EventSource

- + @@ -2290,7 +2359,7 @@

v1.StatusCause

- + @@ -2330,6 +2399,40 @@

v1.StatusCause

+
+
+

v1.SessionAffinityConfig

+
+

SessionAffinityConfig represents the configurations of session affinity.

+
+ +++++++ + + + + + + + + + + + + + + + + + + +
NameDescriptionRequiredSchemaDefault

clientIP

clientIP contains the configurations of Client IP based session affinity.

false

v1.ClientIPConfig

+

any

diff --git a/docs/reference/federation/v1/operations.html b/docs/reference/federation/v1/operations.html index bd587020eb445..a24105e0b2ab2 100755 --- a/docs/reference/federation/v1/operations.html +++ b/docs/reference/federation/v1/operations.html @@ -384,7 +384,7 @@

Responses

- + @@ -462,7 +462,7 @@

Parameters

- + @@ -531,6 +531,23 @@

Parameters

integer (int32)

+ +

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + @@ -541,7 +558,7 @@

Responses

- + @@ -619,7 +636,7 @@

Parameters

- + @@ -688,6 +705,23 @@

Parameters

integer (int32)

+ +

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + @@ -698,7 +732,7 @@

Responses

- + @@ -776,7 +810,7 @@

Parameters

- + @@ -845,6 +879,23 @@

Parameters

integer (int32)

+ +

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + @@ -855,7 +906,7 @@

Responses

- + @@ -933,7 +984,7 @@

Parameters

- + @@ -972,7 +1023,7 @@

Responses

- + @@ -1044,7 +1095,7 @@

Parameters

- + @@ -1114,6 +1165,23 @@

Parameters

+

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + +

PathParameter

namespace

object name and auth scope, such as for teams and projects

@@ -1131,7 +1199,7 @@

Responses

- + @@ -1209,7 +1277,7 @@

Parameters

- + @@ -1279,6 +1347,23 @@

Parameters

+

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + +

PathParameter

namespace

object name and auth scope, such as for teams and projects

@@ -1296,7 +1381,7 @@

Responses

- + @@ -1368,7 +1453,7 @@

Parameters

- + @@ -1415,7 +1500,7 @@

Responses

- + @@ -1487,7 +1572,7 @@

Parameters

- + @@ -1550,7 +1635,7 @@

Responses

- + @@ -1622,7 +1707,7 @@

Parameters

- + @@ -1677,7 +1762,7 @@

Responses

- + @@ -1749,7 +1834,7 @@

Parameters

- + @@ -1828,7 +1913,7 @@

Responses

- + @@ -1900,7 +1985,7 @@

Parameters

- + @@ -1955,7 +2040,7 @@

Responses

- + @@ -2033,7 +2118,7 @@

Parameters

- + @@ -2103,6 +2188,23 @@

Parameters

+

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + +

PathParameter

namespace

object name and auth scope, such as for teams and projects

@@ -2120,7 +2222,7 @@

Responses

- + @@ -2198,7 +2300,7 @@

Parameters

- + @@ -2268,6 +2370,23 @@

Parameters

+

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + +

PathParameter

namespace

object name and auth scope, such as for teams and projects

@@ -2285,7 +2404,7 @@

Responses

- + @@ -2357,7 +2476,7 @@

Parameters

- + @@ -2404,7 +2523,7 @@

Responses

- + @@ -2476,7 +2595,7 @@

Parameters

- + @@ -2539,7 +2658,7 @@

Responses

- + @@ -2611,7 +2730,7 @@

Parameters

- + @@ -2666,7 +2785,7 @@

Responses

- + @@ -2738,7 +2857,7 @@

Parameters

- + @@ -2817,7 +2936,7 @@

Responses

- + @@ -2889,7 +3008,7 @@

Parameters

- + @@ -2944,7 +3063,7 @@

Responses

- + @@ -3022,7 +3141,7 @@

Parameters

- + @@ -3092,6 +3211,23 @@

Parameters

+

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + +

PathParameter

namespace

object name and auth scope, such as for teams and projects

@@ -3109,7 +3245,7 @@

Responses

- + @@ -3187,7 +3323,7 @@

Parameters

- + @@ -3257,6 +3393,23 @@

Parameters

+

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + +

PathParameter

namespace

object name and auth scope, such as for teams and projects

@@ -3274,7 +3427,7 @@

Responses

- + @@ -3346,7 +3499,7 @@

Parameters

- + @@ -3393,7 +3546,7 @@

Responses

- + @@ -3465,7 +3618,7 @@

Parameters

- + @@ -3528,7 +3681,7 @@

Responses

- + @@ -3600,7 +3753,7 @@

Parameters

- + @@ -3655,7 +3808,7 @@

Responses

- + @@ -3727,7 +3880,7 @@

Parameters

- + @@ -3806,7 +3959,7 @@

Responses

- + @@ -3878,7 +4031,7 @@

Parameters

- + @@ -3933,7 +4086,7 @@

Responses

- + @@ -4011,7 +4164,7 @@

Parameters

- + @@ -4081,6 +4234,23 @@

Parameters

+

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + +

PathParameter

namespace

object name and auth scope, such as for teams and projects

@@ -4098,7 +4268,7 @@

Responses

- + @@ -4176,7 +4346,7 @@

Parameters

- + @@ -4246,6 +4416,23 @@

Parameters

+

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + +

PathParameter

namespace

object name and auth scope, such as for teams and projects

@@ -4263,7 +4450,7 @@

Responses

- + @@ -4335,7 +4522,7 @@

Parameters

- + @@ -4382,7 +4569,7 @@

Responses

- + @@ -4454,7 +4641,7 @@

Parameters

- + @@ -4517,7 +4704,7 @@

Responses

- + @@ -4589,7 +4776,7 @@

Parameters

- + @@ -4644,7 +4831,7 @@

Responses

- + @@ -4716,7 +4903,7 @@

Parameters

- + @@ -4795,7 +4982,7 @@

Responses

- + @@ -4867,7 +5054,7 @@

Parameters

- + @@ -4922,7 +5109,7 @@

Responses

- + @@ -5000,7 +5187,7 @@

Parameters

- + @@ -5047,7 +5234,7 @@

Responses

- + @@ -5119,7 +5306,7 @@

Parameters

- + @@ -5174,7 +5361,7 @@

Responses

- + @@ -5246,7 +5433,7 @@

Parameters

- + @@ -5301,7 +5488,7 @@

Responses

- + @@ -5379,7 +5566,7 @@

Parameters

- + @@ -5434,7 +5621,7 @@

Responses

- + @@ -5506,7 +5693,7 @@

Parameters

- + @@ -5553,7 +5740,7 @@

Responses

- + @@ -5625,7 +5812,7 @@

Parameters

- + @@ -5696,7 +5883,7 @@

Responses

- + @@ -5768,7 +5955,7 @@

Parameters

- + @@ -5815,7 +6002,7 @@

Responses

- + @@ -5893,7 +6080,7 @@

Parameters

- + @@ -5940,7 +6127,7 @@

Responses

- + @@ -6012,7 +6199,7 @@

Parameters

- + @@ -6051,7 +6238,7 @@

Responses

- + @@ -6123,7 +6310,7 @@

Parameters

- + @@ -6170,7 +6357,7 @@

Responses

- + @@ -6242,7 +6429,7 @@

Parameters

- + @@ -6289,7 +6476,7 @@

Responses

- + @@ -6367,7 +6554,7 @@

Parameters

- + @@ -6436,6 +6623,23 @@

Parameters

integer (int32)

+ +

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + @@ -6446,7 +6650,7 @@

Responses

- + @@ -6524,7 +6728,7 @@

Parameters

- + @@ -6593,6 +6797,23 @@

Parameters

integer (int32)

+ +

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + @@ -6603,7 +6824,7 @@

Responses

- + @@ -6681,7 +6902,7 @@

Parameters

- + @@ -6750,6 +6971,23 @@

Parameters

integer (int32)

+ +

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + @@ -6760,7 +6998,7 @@

Responses

- + @@ -6838,7 +7076,7 @@

Parameters

- + @@ -6907,6 +7145,23 @@

Parameters

integer (int32)

+ +

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + @@ -6917,7 +7172,7 @@

Responses

- + @@ -6995,7 +7250,7 @@

Parameters

- + @@ -7064,6 +7319,23 @@

Parameters

integer (int32)

+ +

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + @@ -7074,7 +7346,7 @@

Responses

- + @@ -7152,7 +7424,7 @@

Parameters

- + @@ -7222,6 +7494,23 @@

Parameters

+

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + +

PathParameter

namespace

object name and auth scope, such as for teams and projects

@@ -7239,7 +7528,7 @@

Responses

- + @@ -7317,7 +7606,7 @@

Parameters

- + @@ -7387,6 +7676,23 @@

Parameters

+

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + +

PathParameter

namespace

object name and auth scope, such as for teams and projects

@@ -7412,7 +7718,7 @@

Responses

- + @@ -7490,7 +7796,7 @@

Parameters

- + @@ -7560,6 +7866,23 @@

Parameters

+

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + +

PathParameter

namespace

object name and auth scope, such as for teams and projects

@@ -7577,7 +7900,7 @@

Responses

- + @@ -7655,7 +7978,7 @@

Parameters

- + @@ -7725,6 +8048,23 @@

Parameters

+

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + +

PathParameter

namespace

object name and auth scope, such as for teams and projects

@@ -7750,7 +8090,7 @@

Responses

- + @@ -7828,7 +8168,7 @@

Parameters

- + @@ -7898,6 +8238,23 @@

Parameters

+

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + +

PathParameter

namespace

object name and auth scope, such as for teams and projects

@@ -7915,7 +8272,7 @@

Responses

- + @@ -7993,7 +8350,7 @@

Parameters

- + @@ -8063,6 +8420,23 @@

Parameters

+

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + +

PathParameter

namespace

object name and auth scope, such as for teams and projects

@@ -8088,7 +8462,7 @@

Responses

- + @@ -8166,7 +8540,7 @@

Parameters

- + @@ -8236,6 +8610,23 @@

Parameters

+

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + +

PathParameter

namespace

object name and auth scope, such as for teams and projects

@@ -8253,7 +8644,7 @@

Responses

- + @@ -8331,7 +8722,7 @@

Parameters

- + @@ -8401,6 +8792,23 @@

Parameters

+

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + +

PathParameter

namespace

object name and auth scope, such as for teams and projects

@@ -8426,7 +8834,7 @@

Responses

- + @@ -8504,7 +8912,7 @@

Parameters

- + @@ -8574,6 +8982,23 @@

Parameters

+

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + +

PathParameter

name

name of the Namespace

@@ -8591,7 +9016,7 @@

Responses

- + @@ -8669,7 +9094,7 @@

Parameters

- + @@ -8738,6 +9163,23 @@

Parameters

integer (int32)

+ +

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + @@ -8748,7 +9190,7 @@

Responses

- + @@ -8826,7 +9268,7 @@

Parameters

- + @@ -8895,6 +9337,23 @@

Parameters

integer (int32)

+ +

QueryParameter

+

limit

+

limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. +

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

+

false

+

integer (int32)

+ + + +

QueryParameter

+

continue

+

The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

+

false

+

string

+ + @@ -8905,7 +9364,7 @@

Responses

- + diff --git a/update-imported-docs.sh b/update-imported-docs.sh index 717bb90ffc002..b43f8903834ec 100755 --- a/update-imported-docs.sh +++ b/update-imported-docs.sh @@ -5,8 +5,8 @@ set -o errexit # Uncomment this to see the commands as they are run # set -x -VERSION=1.7 -OLDVERSION=1.6 +VERSION=1.8 +OLDVERSION=1.7 # Processes api reference docs. function process_api_ref_docs { @@ -136,7 +136,7 @@ done <_data/overrides.yml ) -BINARIES="federation-apiserver.md federation-controller-manager.md kube-apiserver.md kube-controller-manager.md kube-proxy.md kube-scheduler.md kubelet.md kubefed.md kubefed_init.md kubefed_join.md kubefed_options.md kubefed_unjoin.md kubefed_version.md" +BINARIES="cloud-controller-manager.md federation-apiserver.md federation-controller-manager.md kube-apiserver.md kube-controller-manager.md kube-proxy.md kube-scheduler.md kubelet.md kubefed.md kubefed_init.md kubefed_join.md kubefed_options.md kubefed_unjoin.md kubefed_version.md" ( cd docs/admin