SIG Docs approvers take week-long shifts managing pull requests for the repository. This section covers the duties of a PR wrangler. For more information on giving good reviews, see Reviewing changes. Duties Each day in a week-long shift as PR Wrangler: Review open pull requests for quality and adherence to the Style and Content guides. Start with the smallest PRs (size/XS) first, and end with the largest (size/XXL). Review as many PRs as you can.

Synopsis Show the status of the rollout. By default 'rollout status' will watch the status of the latest rollout until it's done. If you don't want to wait for the rollout to finish then you can use --watch=false. Note that if a new rollout starts in-between, then 'rollout status' will continue watching the latest revision. If you want to pin to a specific revision and abort if it is rolled over by another revision, use --revision=N where N is the revision you need to watch for.

Synopsis Experimental: Wait for a specific condition on one or many resources. The command takes multiple resources and waits until the specified condition is seen in the Status field of every given resource. Alternatively, the command can wait for the given set of resources to be deleted by providing the "delete" keyword as the value to the --for flag. A successful message will be printed to stdout indicating when the specified condition has been met.

Debug cluster Flow control Feedback Was this page helpful? Yes No Thanks for the feedback. If you have a specific, an...

Resource Types Config Config Config holds the information needed to build connect to remote kubernetes clusters as a given user FieldDescription apiVersionstring/v1 kindstringConfig kind string Legacy field from pkg/api/types.go TypeMeta. TODO(jlowdermilk): remove this after eliminating downstream dependencies. apiVersion string Legacy field from pkg/api/types.go TypeMeta. TODO(jlowdermilk): remove this after eliminating downstream dependencies. preferences [Required] Preferences Preferences holds general information to be use for cli interactions clusters [Required] []NamedCluster Clusters is a map of referencable names to cluster configs

Synopsis Create and run a particular image in a pod. kubectl run NAME --image=image [--env="key=value"] [--port=port] [--dry-run=server|client] [--overrides=inline-json] [--command] -- [COMMAND] [args...] Examples # Start a nginx pod kubectl run nginx --image=nginx # Start a hazelcast pod and let the container expose port 5701 kubectl run hazelcast --image=hazelcast/hazelcast --port=5701 # Start a hazelcast pod and set environment variables "DNS_DOMAIN=cluster" and "POD_NAMESPACE=default" in the container kubectl run hazelcast --image=hazelcast/hazelcast --env="DNS_DOMAIN=cluster" --env="POD_NAMESPACE=default" # Start a hazelcast pod and set labels "app=hazelcast" and "env=prod" in the container kubectl run hazelcast --image=hazelcast/hazelcast --labels="app=hazelcast,env=prod" # Dry run; print the corresponding API objects without creating them kubectl run nginx --image=nginx --dry-run=client # Start a nginx pod, but overload the spec with a partial set of values parsed from JSON kubectl run nginx --image=nginx --overrides='{ "apiVersion": "v1", "spec": { .

Configuration APIs Client Authentication (v1) Client Authentication (v1beta1) Event Rate Limit Configuration (v1alpha...

This page shows how to build the Kubernetes component and tool reference pages. Before you begin Start with the Prerequisites section in the Reference Documentation Quickstart guide. Follow the Reference Documentation Quickstart to generate the Kubernetes component and tool reference pages. What's next Generating Reference Documentation Quickstart Generating Reference Documentation for kubectl Commands Generating Reference Documentation for the Kubernetes API Contributing to the Upstream Kubernetes Project for Documentation

Synopsis Print the client and server version information for the current context. kubectl version [flags] Examples # Print the client and server versions for the current context kubectl version Options --client If true, shows client version only (no server required). -h, --help help for version -o, --output string One of 'yaml' or 'json'. --as string Username to impersonate for the operation. User could be a regular user or a service account in a namespace.

FEATURE STATE: Kubernetes v1.25 [stable] You can customize the behavior of the kube-scheduler by writing a configuration file and passing its path as a command line argument. A scheduling Profile allows you to configure the different stages of scheduling in the kube-scheduler. Each stage is exposed in an extension point. Plugins provide scheduling behaviors by implementing one or more of these extension points. You can specify scheduling profiles by running kube-scheduler --config <filename>, using the KubeSchedulerConfiguration v1 struct.