Kubernetes: Up and Running: Dive into the Future of Infrastructure by Hightower Kelsey & Burns Brendan & Beda Joe

Author:Hightower, Kelsey & Burns, Brendan & Beda, Joe [Hightower, Kelsey]
Language: eng
Format: azw3
Publisher: O'Reilly Media
Published: 2017-09-07T04:00:00+00:00

DaemonSets require a unique name across all DaemonSets in a given Kubernetes namespace. Each DaemonSet must include a Pod template spec, which will be used to create Pods as needed. This is where the similarities between ReplicaSets and DaemonSets end. Unlike ReplicaSets, DaemonSets will create Pods on every node in the cluster by default unless a node selector is used.

Once you have a valid DaemonSet configuration in place, you can use the kubectl apply command to submit the DaemonSet to the Kubernetes API. In this section we will create a DaemonSet to ensure the fluentd HTTP server is running on every node in our cluster:

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.