我的书签
添加书签
移除书签wait
Experimental: Wait for a specific condition on one or many resources.
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.
wait
- Tutorials
- Home
- Tasks
- Managing Secrets
- Administer a Cluster
- Securing a Cluster
- Manage Memory, CPU, and API Resources
- Configure Memory and CPU Quotas for a Namespace
- Configure Default Memory Requests and Limits for a Namespace
- Configure Default CPU Requests and Limits for a Namespace
- Configure Minimum and Maximum Memory Constraints for a Namespace
- Configure a Pod Quota for a Namespace
- Configure Minimum and Maximum CPU Constraints for a Namespace
- Namespaces Walkthrough
- Using CoreDNS for Service Discovery
- Access Clusters Using the Kubernetes API
- Upgrade A Cluster
- Operating etcd clusters for Kubernetes
- Use Cascading Deletion in a Cluster
- Set Kubelet parameters via a config file
- Autoscale the DNS Service in a Cluster
- Migrating from dockershim
- Using sysctls in a Kubernetes Cluster
- Running Kubernetes Node Components as a Non-root User
- Debugging DNS Resolution
- Safely Drain a Node
- Enabling Service Topology
- Declare Network Policy
- Reconfigure a Node’s Kubelet in a Live Cluster
- IP Masquerade Agent User Guide
- Share a Cluster with Namespaces
- Configure Quotas for API Objects
- Migrate Replicated Control Plane To Use Cloud Controller Manager
- Install a Network Policy Provider
- Advertise Extended Resources for a Node
- Developing Cloud Controller Manager
- Using a KMS provider for data encryption
- Cloud Controller Manager Administration
- Using NodeLocal DNSCache in Kubernetes clusters
- Administration with kubeadm
- Enable Or Disable A Kubernetes API
- Guaranteed Scheduling For Critical Add-On Pods
- Change the default StorageClass
- Reserve Compute Resources for System Daemons
- Limit Storage Consumption
- Utilizing the NUMA-aware Memory Manager
- Change the Reclaim Policy of a PersistentVolume
- Certificates
- Access Services Running on Clusters
- Customizing DNS Service
- Control Topology Management Policies on a node
- Encrypting Secret Data at Rest
- Control CPU Management Policies on the Node
- Install Tools
- Networking
- Manage Cluster Daemons
- Configure Pods and Containers
- Assign Pods to Nodes
- Assign Extended Resources to a Container
- Assign Memory Resources to Containers and Pods
- Create static Pods
- Share Process Namespace between Containers in a Pod
- Enforce Pod Security Standards with Namespace Labels
- Configure a Pod to Use a ConfigMap
- Configure a Pod to Use a Volume for Storage
- Configure Liveness, Readiness and Startup Probes
- Migrate from PodSecurityPolicy to the Built-In PodSecurity Admission Controller
- Configure a Security Context for a Pod or Container
- Configure GMSA for Windows Pods and containers
- Pull an Image from a Private Registry
- Configure Service Accounts for Pods
- Configure Quality of Service for Pods
- Configure Pod Initialization
- Assign Pods to Nodes using Node Affinity
- Create a Windows HostProcess Pod
- Attach Handlers to Container Lifecycle Events
- Configure a Pod to Use a PersistentVolume for Storage
- Configure a Pod to Use a Projected Volume for Storage
- Configure RunAsUserName for Windows pods and containers
- Enforce Pod Security Standards by Configuring the Built-in Admission Controller
- Translate a Docker Compose File to Kubernetes Resources
- Assign CPU Resources to Containers and Pods
- Extend Kubernetes
- Run Jobs
- TLS
- Manage Kubernetes Objects
- Service Catalog
- Run Applications
- Specifying a Disruption Budget for your Application
- Run a Single-Instance Stateful Application
- HorizontalPodAutoscaler Walkthrough
- Horizontal Pod Autoscaling
- Delete a StatefulSet
- Force Delete StatefulSet Pods
- Run a Stateless Application Using a Deployment
- Accessing the Kubernetes API from a Pod
- Run a Replicated Stateful Application
- Scale a StatefulSet
- Monitoring, Logging, and Debugging
- Debug Pods and ReplicationControllers
- Debug Running Pods
- Tools for Monitoring Resources
- Monitor Node Health
- Debug a StatefulSet
- Application Introspection and Debugging
- Troubleshooting
- Debugging Kubernetes nodes with crictl
- Auditing
- Troubleshoot Applications
- Developing and debugging services locally
- Determine the Reason for Pod Failure
- Troubleshoot Clusters
- Resource metrics pipeline
- Debug Services
- Get a Shell to a Running Container
- Debug Init Containers
- Access Applications in a Cluster
- Use Port Forwarding to Access Applications in a Cluster
- Communicate Between Containers in the Same Pod Using a Shared Volume
- Use a Service to Access an Application in a Cluster
- Configure DNS for a Cluster
- Accessing Clusters
- Connect a Frontend to a Backend Using Services
- Create an External Load Balancer
- Set up Ingress on Minikube with the NGINX Ingress Controller
- List All Container Images Running in a Cluster
- Configure Access to Multiple Clusters
- Deploy and Access the Kubernetes Dashboard
- Inject Data Into Applications
- Contribute
- Getting started
- Best practices
- Learning environment
- Production environment
- Container runtimes
- Turnkey Cloud Solutions
- Windows in Kubernetes
- Installing Kubernetes with deployment tools
- Installing Kubernetes with Kubespray
- Installing Kubernetes with kops
- Bootstrapping clusters with kubeadm
- Set up a High Availability etcd cluster with kubeadm
- Creating Highly Available clusters with kubeadm
- Options for Highly Available topology
- Installing kubeadm
- Customizing components with the kubeadm API
- Dual-stack support with kubeadm
- Configuring each kubelet in your cluster using kubeadm
- Troubleshooting kubeadm
- Creating a cluster with kubeadm
- Concepts
- Docs smoke test page
- Reference
- Kubernetes Issues and Security
- Ports and Protocols
- API Access Control
- Configuration APIs
- kubeadm Configuration (v1beta2)
- kube-proxy Configuration (v1alpha1)
- kube-scheduler Configuration (v1beta3)
- kubeadm Configuration (v1beta3)
- kube-scheduler Configuration (v1beta2)
- kube-scheduler Policy Configuration (v1)
- Kubelet Configuration (v1beta1)
- Client Authentication (v1beta1)
- WebhookAdmission Configuration (v1)
- kube-apiserver Audit Configuration (v1)
- kube-apiserver Configuration (v1beta1)
- kube-scheduler Configuration (v1beta1)
- Well-Known Labels, Annotations and Taints
- Scheduling
- Other Tools
- Setup tools
- Kubernetes API
- Glossary
- API Overview
- kubectl
- kubectl for Docker Users
- kubectl Usage Conventions
- kubectl Commands
- GETTING STARTED
- autoscale
- debug
- diff
- edit
- kustomize
- label
- patch
- replace
- rollout
- scale
- create
- set
- wait
- WORKING WITH APPS
- attach
- auth
- cp
- describe
- exec
- logs
- port-forward
- get
- proxy
- top
- CLUSTER MANAGEMENT
- api-versions
- certificate
- cluster-info
- cordon
- drain
- taint
- uncordon
- run
- KUBECTL SETTINGS AND USAGE
- alpha
- api-resources
- completion
- config
- explain
- options
- plugin
- version
- expose
- delete
- APP MANAGEMENT
- apply
- annotate
- kubectl
- JSONPath Support
- kubectl Cheat Sheet
- Overview of kubectl
- Component tools
暂无相关搜索结果！
本文档使用 全库网 构建
