Production-Grade Container Orchestration

The kubectl tool supports JSONPath templates as an output format. A JSONPath template is composed of JSONPath expressions enclosed by curly braces: { and }. Kubectl uses JSONPath expressions to filter on specific fields in the JSON object and format the output. In addition to the original JSONPath template syntax, the following functions and syntax are valid: Use double quotes to quote text inside JSONPath expressions. Use the range, end operators to iterate lists.

Package v1 is the v1 version of the API. Resource Types AdmissionConfiguration AuthenticationConfiguration AuthorizationConfiguration EncryptionConfiguration TracingConfiguration TracingConfiguration Appears in: KubeletConfiguration TracingConfiguration TracingConfiguration TracingConfiguration TracingConfiguration provides versioned configuration for OpenTelemetry tracing clients. FieldDescription endpoint string Endpoint of the collector this component will report traces to. The connection is insecure, and does not currently support TLS. Recommended is unset, and endpoint is the otlp grpc default, localhost:4317. samplingRatePerMillion int32 SamplingRatePerMillion is the number of samples to collect per million spans.

Production-Grade Container Orchestration

Resource Types CredentialProviderRequest CredentialProviderResponse CredentialProviderRequest CredentialProviderRequest includes the image that the kubelet requires authentication for. Kubelet will pass this request object to the plugin via stdin. In general, plugins should prefer responding with the same apiVersion they were sent. FieldDescription apiVersionstringcredentialprovider.kubelet.k8s.io/v1 kindstringCredentialProviderRequest image [Required] string image is the container image that is being pulled as part of the credential provider plugin request. Plugins may optionally parse the image to extract any information required to fetch credentials.

Note:Code developers: If you are documenting a new feature for an upcoming Kubernetes release, see Document a new feature. To contribute new content pages or improve existing content pages, open a pull request (PR). Make sure you follow all the requirements in the Before you begin section. If your change is small, or you're unfamiliar with git, read Changes using GitHub to learn how to edit a page. If your changes are large, read Work from a local fork to learn how to make changes locally on your computer.

Production-Grade Container Orchestration

There are two official Kubernetes blogs, and the CNCF has its own blog where you can cover Kubernetes too. For the main Kubernetes blog, we (the Kubernetes project) like to publish articles with different perspectives and special focuses, that have a link to Kubernetes. Some articles appear on both blogs: there is a primary version of the article, and a mirror article on the other blog. This page describes the criteria for mirroring, the motivation for mirroring, and explains what you should do to ensure that an article publishes to both blogs.

Anyone can review a documentation pull request. Visit the pull requests section in the Kubernetes website repository to see open pull requests. Reviewing documentation pull requests is a great way to introduce yourself to the Kubernetes community. It helps you learn the code base and build trust with other contributors. Before reviewing, it's a good idea to: Read the content guide and style guide so you can leave informed comments.

Principles and practices for good RBAC design for cluster operators.