OpenShift DaemonSet Operations: Difference between revisions
Jump to navigation
Jump to search
| Line 36: | Line 36: | ||
=Updating Daemon Sets= | =Updating Daemon Sets= | ||
<font color=red>Currently, updating a daemonset’s pod template does not affect existing pod replicas. Moreover, if you delete a daemonset and then create a new daemonset with a different template but the same label selector, it will recognize any existing pod replicas as having matching labels and thus will not update them or create new replicas despite a mismatch in the pod template. | |||
To update a daemonset, force new pod replicas to be created by deleting the old replicas or nodes. | |||
</font> | |||
Revision as of 22:19, 30 July 2017
External
Internal
Obtaining Information about DaemonSets
The name of the DaemonSet that manages a pod is available in pod's "oc describe pod" output, as value for the "Controllers:" label. That value can be used to get the DaemonSet definition:
oc describe DaemonSet/<daemon-set-name>
Example:
oc describe DaemonSet/logging-fluentd
Name: logging-fluentd Image(s): registry.access.redhat.com/openshift3/logging-fluentd:3.5.0 Selector: component=fluentd,provider=openshift Node-Selector: logging-infra-fluentd=true Labels: component=fluentd logging-infra=fluentd provider=openshift Desired Number of Nodes Scheduled: 7 Current Number of Nodes Scheduled: 7 Number of Nodes Misscheduled: 0 Pods Status: 2 Running / 0 Waiting / 0 Succeeded / 5 Failed No events.
Creating Daemon Sets
Updating Daemon Sets
Currently, updating a daemonset’s pod template does not affect existing pod replicas. Moreover, if you delete a daemonset and then create a new daemonset with a different template but the same label selector, it will recognize any existing pod replicas as having matching labels and thus will not update them or create new replicas despite a mismatch in the pod template.
To update a daemonset, force new pod replicas to be created by deleting the old replicas or nodes.