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

You can use the Kubernetes command line tool kubectl to interact with the API Server. Using kubectl is straightforward if you are familiar with the Docker command line tool. However, there are a few differences between the Docker commands and the kubectl commands. The following sections show a Docker sub-command and describe the equivalent kubectl command. docker run To run an nginx Deployment and expose the Deployment, see kubectl create deployment.

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

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.

Alongside the PR Wrangler, formal approvers, reviewers and members of SIG Docs take week-long shifts triaging and categorising issues for the repository. Duties Each day in a week-long shift the Issue Wrangler will be responsible for: Triaging and tagging incoming issues daily. See Triage and categorize issues for guidelines on how SIG Docs uses metadata. Keeping an eye on stale & rotten issues within the kubernetes/website repository. Maintenance of the Issues board.

The Kubernetes documentation follows several types of page content: Concept Task Tutorial Reference Content sections Each page content type contains a number of sections defined by Markdown comments and HTML headings. You can add content headings to your page with the heading shortcode. The comments and headings help maintain the structure of the page content types. Examples of Markdown comments defining page content sections: <!-- overview --> <!-- body --> To create common headings in your content pages, use the heading shortcode with a heading string.

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

Resource Types AdmissionReview AdmissionReview AdmissionReview describes an admission review request/response. FieldDescription apiVersionstringadmission.k8s.io/v1 kindstringAdmissionReview request AdmissionRequest Request describes the attributes for the admission request. response AdmissionResponse Response describes the attributes for the admission response. AdmissionRequest Appears in: AdmissionReview AdmissionRequest describes the admission.Attributes for the admission request. FieldDescription uid [Required] k8s.io/apimachinery/pkg/types.UID UID is an identifier for the individual request/response. It allows us to distinguish instances of requests which are otherwise identical (parallel requests, requests when earlier requests did not modify etc) The UID is meant to track the round trip (request/response) between the KAS and the WebHook, not the user request.

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.

External APIs Kubernetes Custom Metrics (v1beta2) Kubernetes External Metrics (v1beta1) Kubernetes Metrics (v1beta1) ...