Creating Secret objects using kustomization.yaml file.

Run and manage both stateless and stateful applications.

Managing confidential settings data using Secrets.

This page shows how to run an application using a Kubernetes Deployment object. Objectives Create an nginx deployment. Use kubectl to list information about the deployment. Update the deployment. Before you begin You need to have a Kubernetes cluster, and the kubectl command-line tool must be configured to communicate with your cluster. It is recommended to run this tutorial on a cluster with at least two nodes that are not acting as control plane hosts.

This page shows how to run automated tasks using Kubernetes CronJob object. Before you begin You need to have a Kubernetes cluster, and the kubectl command-line tool must be configured to communicate with your cluster. It is recommended to run this tutorial on a cluster with at least two nodes that are not acting as control plane hosts. If you do not already have a cluster, you can create one by using minikube or you can use one of these Kubernetes playgrounds:

Synopsis Create a TLS secret from the given public/private key pair. The public/private key pair must exist beforehand. The public key certificate must be .PEM encoded and match the given private key. kubectl create secret tls NAME --cert=path/to/cert/file --key=path/to/key/file [--dry-run=server|client|none] Examples # Create a new TLS secret named tls-secret with the given key pair kubectl create secret tls tls-secret --cert=path/to/tls.crt --key=path/to/tls.key Options --allow-missing-template-keys     Default: true If true, ignore any errors in templates when a field or map key is missing in the template.

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.

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.

This page serves two purposes: Demonstrate how the Kubernetes documentation uses Markdown Provide a "smoke test" document we can use to test HTML, CSS, and template changes that affect the overall documentation. Heading levels The above heading is an H2. The page title renders as an H1. The following sections show H3 - H6. ### H3 This is in an H3 section. #### H4 This is in an H4 section. ##### H5 This is in an H5 section.

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.