- Sort Score
- Result 10 results
- Languages All
- Labels All
Results 191 - 200 of 699 for host:kubernetes.io (0.02 sec)
-
kubectl create service loadbalancer | Kubernetes
Synopsis Create a LoadBalancer service with the specified name. kubectl create service loadbalancer NAME [--tcp=port:targetPort] [--dry-run=server|client|none] Examples # Create a new LoadBalancer service named my-lbs kubectl create service loadbalancer my-lbs --tcp=5678:8080 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. Only applies to golang and jsonpath output formats. --dry-run string[="unchanged"] Default: "none" Must be "none", "server", or "client". If client strategy, only print the object that would be sent, without sending it.kubernetes.io/docs/reference/kubectl/generated/kubectl_create/kubectl_create_service_loadbalancer/Registered: Mon Sep 15 09:27:13 UTC 2025 - 467.5K bytes - Viewed (0) -
kubectl expose | Kubernetes
Production-Grade Container Orchestrationkubernetes.io/docs/reference/kubectl/generated/kubectl_expose/Registered: Mon Sep 15 09:26:46 UTC 2025 - 470.3K bytes - Viewed (0) -
Kubectl user preferences (kuberc) | Kubernetes
FEATURE STATE: Kubernetes 1.34 [beta] A Kubernetes kuberc configuration file allows you to define preferences for kubectl, such as default options and command aliases. Unlike the kubeconfig file, a kuberc configuration file does not contain cluster details, usernames or passwords. The default location of this configuration file is $HOME/.kube/kuberc. To provide kubectl with a path to a custom kuberc file, use the --kuberc command line option, or set the KUBERC environment variable.kubernetes.io/docs/reference/kubectl/kuberc/Registered: Mon Sep 15 09:27:44 UTC 2025 - 473K bytes - Viewed (0) -
kubectl explain | Kubernetes
Production-Grade Container Orchestrationkubernetes.io/docs/reference/kubectl/generated/kubectl_explain/Registered: Mon Sep 15 09:28:12 UTC 2025 - 465.3K bytes - Viewed (0) -
Contributing to the Upstream Kubernetes Code | ...
This page shows how to contribute to the upstream kubernetes/kubernetes project. You can fix bugs found in the Kubernetes API documentation or the content of the Kubernetes components such as kubeadm, kube-apiserver, and kube-controller-manager. If you instead want to regenerate the reference documentation for the Kubernetes API or the kube-* components from the upstream code, see the following instructions: Generating Reference Documentation for the Kubernetes API Generating Reference Documentation for the Kubernetes Components and Tools Before you begin You need to have these tools installed:kubernetes.io/docs/contribute/generate-ref-docs/contribute-upstream/Registered: Mon Sep 15 09:33:52 UTC 2025 - 471.3K bytes - Viewed (0) -
Configure a Pod to Use a PersistentVolume for S...
This page shows you how to configure a Pod to use a PersistentVolumeClaim for storage. Here is a summary of the process: You, as cluster administrator, create a PersistentVolume backed by physical storage. You do not associate the volume with any Pod. You, now taking the role of a developer / cluster user, create a PersistentVolumeClaim that is automatically bound to a suitable PersistentVolume. You create a Pod that uses the above PersistentVolumeClaim for storage.kubernetes.io/docs/tasks/configure-pod-container/configure-persistent-volume-storage/Registered: Mon Sep 15 08:54:03 UTC 2025 - 500.1K bytes - Viewed (0) -
Troubleshooting Applications | Kubernetes
Debugging common containerized application issues.kubernetes.io/docs/tasks/debug/debug-application/Registered: Mon Sep 15 08:56:32 UTC 2025 - 456.1K bytes - Viewed (0) -
Determine the Reason for Pod Failure | Kubernetes
This page shows how to write and read a Container termination message. Termination messages provide a way for containers to write information about fatal events to a location where it can be easily retrieved and surfaced by tools like dashboards and monitoring software. In most cases, information that you put in a termination message should also be written to the general Kubernetes logs. Before you begin You need to have a Kubernetes cluster, and the kubectl command-line tool must be configured to communicate with your cluster.kubernetes.io/docs/tasks/debug/debug-application/determine-reason-pod-failure/Registered: Mon Sep 15 08:56:38 UTC 2025 - 471.9K bytes - Viewed (0) -
Update API Objects in Place Using kubectl patch...
Use kubectl patch to update Kubernetes API objects in place. Do a strategic merge patch or a JSON merge patch.kubernetes.io/docs/tasks/manage-kubernetes-objects/update-api-object-kubectl-patch/Registered: Mon Sep 15 08:56:42 UTC 2025 - 509.4K bytes - Viewed (0) -
Configure a Security Context for a Pod or Conta...
A security context defines privilege and access control settings for a Pod or Container. Security context settings include, but are not limited to: Discretionary Access Control: Permission to access an object, like a file, is based on user ID (UID) and group ID (GID). Security Enhanced Linux (SELinux): Objects are assigned security labels. Running as privileged or unprivileged. Linux Capabilities: Give a process some privileges, but not all the privileges of the root user.kubernetes.io/docs/tasks/configure-pod-container/security-context/Registered: Mon Sep 15 08:56:47 UTC 2025 - 537.3K bytes - Viewed (0)