Synopsis Set the current-context in a kubeconfig file. kubectl config use-context CONTEXT_NAME Examples # Use the context for the minikube cluster kubectl config use-context minikube Options -h, --help help for use-context Parent Options Inherited --as string Username to impersonate for the operation. User could be a regular user or a service account in a namespace. --as-group strings Group to impersonate for the operation, this flag can be repeated to specify multiple groups.

Production-Grade Container Orchestration

Production-Grade Container Orchestration

FastAPI framework, high performance, easy to learn, fast to code, ready for production

Skip to main content Back to top Ctrl + K Plot types User guide Tutorials Examples Reference Contribute Releases Gitt...

FastAPI framework, high performance, easy to learn, fast to code, ready for production

FastAPI framework, high performance, easy to learn, fast to code, ready for production

Synopsis Create a deployment with the specified name. kubectl create deployment NAME --image=image -- [COMMAND] [args...] Examples # Create a deployment named my-dep that runs the busybox image kubectl create deployment my-dep --image=busybox # Create a deployment with a command kubectl create deployment my-dep --image=busybox -- date # Create a deployment named my-dep that runs the nginx image with 3 replicas kubectl create deployment my-dep --image=nginx --replicas=3 # Create a deployment named my-dep that runs the busybox image and expose port 5701 kubectl create deployment my-dep --image=busybox --port=5701 # Create a deployment named my-dep that runs multiple containers kubectl create deployment my-dep --image=busybox:latest --image=ubuntu:latest --image=nginx 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.

FastAPI framework, high performance, easy to learn, fast to code, ready for production

Synopsis Create a config map based on a file, directory, or specified literal value. A single config map may package one or more key/value pairs. When creating a config map based on a file, the key will default to the basename of the file, and the value will default to the file content. If the basename is an invalid key, you may specify an alternate key. When creating a config map based on a directory, each file whose basename is a valid key in the directory will be packaged into the config map.