- Sort Score
- Result 10 results
- Languages All
- Labels All
Results 261 - 270 of 669 for host:kubernetes.io (0.1 sec)
-
Example: Deploying Cassandra with a StatefulSet...
This tutorial shows you how to run Apache Cassandra on Kubernetes. Cassandra, a database, needs persistent storage to provide data durability (application state). In this example, a custom Cassandra seed provider lets the database discover new Cassandra instances as they join the Cassandra cluster. StatefulSets make it easier to deploy stateful applications into your Kubernetes cluster. For more information on the features used in this tutorial, see StatefulSet. Note:Cassandra and Kubernetes both use the term node to mean a member of a cluster.kubernetes.io/docs/tutorials/stateful-application/cassandra/Registered: Fri Nov 15 07:04:18 UTC 2024 - 470.4K bytes - Viewed (0) -
Using Source IP | Kubernetes
Applications running in a Kubernetes cluster find and communicate with each other, and the outside world, through the Service abstraction. This document explains what happens to the source IP of packets sent to different types of Services, and how you can toggle this behavior according to your needs. Before you begin Terminology This document makes use of the following terms: NAT Network address translation Source NAT Replacing the source IP on a packet; in this page, that usually means replacing with the IP address of a node.kubernetes.io/docs/tutorials/services/source-ip/Registered: Fri Nov 15 07:03:45 UTC 2024 - 449.5K bytes - Viewed (0) -
kubectl run | Kubernetes
Synopsis Create and run a particular image in a pod. kubectl run NAME --image=image [--env="key=value"] [--port=port] [--dry-run=server|client] [--overrides=inline-json] [--command] -- [COMMAND] [args...] Examples # Start a nginx pod kubectl run nginx --image=nginx # Start a hazelcast pod and let the container expose port 5701 kubectl run hazelcast --image=hazelcast/hazelcast --port=5701 # Start a hazelcast pod and set environment variables "DNS_DOMAIN=cluster" and "POD_NAMESPACE=default" in the container kubectl run hazelcast --image=hazelcast/hazelcast --env="DNS_DOMAIN=cluster" --env="POD_NAMESPACE=default" # Start a hazelcast pod and set labels "app=hazelcast" and "env=prod" in the container kubectl run hazelcast --image=hazelcast/hazelcast --labels="app=hazelcast,env=prod" # Dry run; print the corresponding API objects without creating them kubectl run nginx --image=nginx --dry-run=client # Start a nginx pod, but overload the spec with a partial set of values parsed from JSON kubectl run nginx --image=nginx --overrides='{ "apiVersion": "v1", "spec": { .kubernetes.io/docs/reference/kubectl/generated/kubectl_run/Registered: Fri Nov 15 07:21:24 UTC 2024 - 445.2K bytes - Viewed (0) -
kubectl api-versions | Kubernetes
Synopsis Print the supported API versions on the server, in the form of "group/version". kubectl api-versions Examples # Print the supported API versions kubectl api-versions Options -h, --help help for api-versions --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.kubernetes.io/docs/reference/kubectl/generated/kubectl_api-versions/Registered: Fri Nov 15 07:19:55 UTC 2024 - 432.1K bytes - Viewed (0) -
kubeadm certs | Kubernetes
kubeadm certs provides utilities for managing certificates. For more details on how these commands can be used, see Certificate Management with kubeadm. kubeadm certs A collection of operations for operating Kubernetes certificates. overview Commands related to handling kubernetes certificates Synopsis Commands related to handling kubernetes certificates kubeadm certs [flags] Options -h, --help help for certs Options inherited from parent commands --rootfs string The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path.kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-certs/Registered: Fri Nov 15 07:20:00 UTC 2024 - 467.1K bytes - Viewed (0) -
kubeadm join phase | Kubernetes
kubeadm join phase enables you to invoke atomic steps of the join process. Hence, you can let kubeadm do some of the work and you can fill in the gaps if you wish to apply customization. kubeadm join phase is consistent with the kubeadm join workflow, and behind the scene both use the same code. kubeadm join phase phase Use this command to invoke single phase of the join workflowkubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-join-phase/Registered: Fri Nov 15 07:20:17 UTC 2024 - 464.7K bytes - Viewed (0) -
kubectl rollout status | Kubernetes
Synopsis Show the status of the rollout. By default 'rollout status' will watch the status of the latest rollout until it's done. If you don't want to wait for the rollout to finish then you can use --watch=false. Note that if a new rollout starts in-between, then 'rollout status' will continue watching the latest revision. If you want to pin to a specific revision and abort if it is rolled over by another revision, use --revision=N where N is the revision you need to watch for.kubernetes.io/docs/reference/kubectl/generated/kubectl_rollout/kubectl_rollout_status/Registered: Fri Nov 15 07:21:51 UTC 2024 - 434.7K bytes - Viewed (0) -
kubectl create role | Kubernetes
Synopsis Create a role with single rule. kubectl create role NAME --verb=verb --resource=resource.group/subresource [--resource-name=resourcename] [--dry-run=server|client|none] Examples # Create a role named "pod-reader" that allows user to perform "get", "watch" and "list" on pods kubectl create role pod-reader --verb=get --verb=list --verb=watch --resource=pods # Create a role named "pod-reader" with ResourceName specified kubectl create role pod-reader --verb=get --resource=pods --resource-name=readablepod --resource-name=anotherpod # Create a role named "foo" with API Group specified kubectl create role foo --verb=get,list,watch --resource=rs.kubernetes.io/docs/reference/kubectl/generated/kubectl_create/kubectl_create_role/Registered: Fri Nov 15 07:21:56 UTC 2024 - 437.6K bytes - Viewed (0) -
kubectl rollout history | Kubernetes
Synopsis View previous rollout revisions and configurations. kubectl rollout history (TYPE NAME | TYPE/NAME) [flags] Examples # View the rollout history of a deployment kubectl rollout history deployment/abc # View the details of daemonset revision 3 kubectl rollout history daemonset/abc --revision=3 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.kubernetes.io/docs/reference/kubectl/generated/kubectl_rollout/kubectl_rollout_history/Registered: Fri Nov 15 07:22:01 UTC 2024 - 435.2K bytes - Viewed (0) -
kubectl events | Kubernetes
Synopsis Display events. Prints a table of the most important information about events. You can request events for a namespace, for all namespace, or filtered to only those pertaining to a specified resource. kubectl events [(-o|--output=)json|yaml|name|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-file] [--for TYPE/NAME] [--watch] [--types=Normal,Warning] Examples # List recent events in the default namespace kubectl events # List recent events in all namespaces kubectl events --all-namespaces # List recent events for the specified pod, then wait for more events and list them as they arrive kubectl events --for pod/web-pod-13je7 --watch # List recent events in YAML format kubectl events -oyaml # List recent only events of type 'Warning' or 'Normal' kubectl events --types=Warning,Normal Options -A, --all-namespaces If present, list the requested object(s) across all namespaces.kubernetes.io/docs/reference/kubectl/generated/kubectl_events/Registered: Fri Nov 15 07:28:25 UTC 2024 - 437.7K bytes - Viewed (0)