148422597X Kubernetes Management Design Patterns [Vohra 2017-01-29] {E559F6BB}

Recommendations

Info

Chapter 9 ■ Scheduling Pods on NodesTable 9-1. Predicates for Filtering PolicyPredicateNoDiskConflictNoVolumeZoneConflictPodFitsResourcesPodFitsHostPortsHostNameMatchNodeSelectorMaxEBSVolumeCountMaxGCEPDVolumeCountCheckNodeMemoryPressureCheckNodeDiskPressureDescriptionEvaluates whether there is any disk conflict due to the volumes requestedby the pod. Supported volume types are AWS EBS, GCE PD, and CephRBD.Taking into consideration zone restrictions, evaluates whether thevolumes a pod requests are available on the zone.Verifies that the available resources (CPU and memory) on a node fit apod’s resource requirements.Verifies that a HostPort requested by a pod is not already taken up.If the pod’s spec specified a node name, filters out all the other nodes.Filters out nodes that do not have matching labels as set in the pod’snodeSelector field and the scheduler.alpha.kubernetes.io/affinitypod annotation if specified.Verifies that the number of attached EBS Volumes does not exceed thelimit of 39 available volumes (1 of the 40 available is reserved for the rootvolume).Verifies that the number of attached GCE PD Volumes does not exceed thelimit of 16 available volumes.Least priority (BestEffort) pods cannot be scheduled on nodes withmemory pressure condition.Pods cannot be scheduled on nodes with a disk pressure condition.After the unsuitable nodes have been filtered out, the remaining nodes are ranked using priorityfunctions. Some of the salient priority functions are discussed in Table 9-2.Table 9-2. Priority FunctionsPriority FunctionLeastRequestedPriorityBalancedResourceAllocationSelectorSpreadPriorityCalculateAntiAffinityPriorityDescriptionThe objective of this priority function is to spread out the resourceconsumption across the nodes. CPU and memory are equallyweighted in calculating the free resources fraction (the fraction of thenode that would be free if a pod were scheduled on the node) using aformula: (capacity – sum of requests of all pods already on the node –request of pod that is being scheduled) / capacity). The node with thegreatest free fraction is selected for scheduling.The objective of this priority function is to balance the CPU andmemory utilization rate.The objective is to avoid scheduling pods in the same replicationcontroller, replica set or service on to the same node or zone.The objective is to avoid scheduling pods in the same service onnodes with same label values for a particular label.(continued)201
Chapter 9 ■ Scheduling Pods on NodesTable 9-2. (continued)Priority FunctionImageLocalityPriorityNodeAffinityPriorityDescriptionThe objective is to schedule on nodes that already have some or allof the image packages installed. A node with the larger size of thealready installed packages is preferred.Evaluate node affinity usingpreferredDuringSchedulingIgnoredDuringExecution andrequiredDuringSchedulingIgnoredDuringExecution.The final node ranking is calculated using a weighted priority function score. Each node is given a scorein the range of 1–10 for each of the applied priority functions, and the final score is calculated by assigninga weight for each priority function. For example, given three priority functions priorityFunc1Score,priorityFunc2Score, and priorityFunc3Score, the final score is calculated as follows:RankingScoreNodeA = (weight1 * priorityFunc1Score) + (weight2 * priorityFunc2Score) +(weight3 * priorityFunc3Score)The node with the highest score is selected for scheduling a pod.The default scheduling policy as determined by default predicates and priority functions may becustomized or overridden using one of the following procedures:1. Use a --policy-config-file parameter to the scheduler. The policy config fileis a json file, for example https://github.com/kubernetes/kubernetes/blob/master/examples/scheduler-policy-config.json.2. Modify the default predicates and/or priority functions in plugin/pkg/scheduler/algorithm/predicates/predicates.go and/or plugin/pkg/scheduler/algorithm/priorities/priorities.go respectively and register thepolicy in defaultPredicates() and/or defaultPriorities() in plugin/pkg/scheduler/algorithmprovider/defaults/defaults.go.Setting the EnvironmentWe shall be using a CoreOS-based AWS EC2 Cloud Formation to run a one-controller-three-worker-nodeKubernetes cluster. Start an EC2 instance using Amazon Linux AMI. SSH log in to the EC2 instance:ssh -i docker.pem ec2-user@54.197.206.44Start a cloud configuration for a Kubernetes cluster and register the Public IP address of the controllerin the Public DNS name. While configuring the cluster set the Kubernetes version to v1.3.0_coreos.1 in thekubernetesVersion field in cluster.yaml.Install the kubectl binaries. Both the Client and Server versions should be 1.3, as shown in Figure 9-2.202
Page 1 and 2:
KubernetesManagementDesign Patterns
Page 3 and 4:
Kubernetes Management Design Patter
Page 5 and 6:
■ CONTENTS AT A GLANCE■Part
Page 7 and 8:
■ CONTENTSSetting Up Cluster Para
Page 9 and 10:
■ CONTENTS■Chapter ■ 6: Us
Page 11 and 12:
■ CONTENTSOvercommitting Resou
Page 13 and 14:
■ CONTENTSInstalling OpenShift
Page 15 and 16:
About the Technical ReviewerMassimo
Page 17 and 18:
■ INTRODUCTIONpatterns are lan
Page 19 and 20:
■ INTRODUCTIONIn Chapter 3 we
Page 21 and 22:
CHAPTER 1Kubernetes on AWSKubernete
Page 23 and 24:
Chapter 1 ■ Kubernetes on AWSIn t
Page 25 and 26:
Chapter 1 ■ Kubernetes on AWSUsin
Page 27 and 28:
Chapter 1 ■ Kubernetes on AWSClic
Page 29 and 30:
Chapter 1 ■ Kubernetes on AWSFigu
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Testing the ClusterChapter 1 ■ Ku
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
CHAPTER 2Kubernetes on CoreOS on AW
Page 43 and 44:
Chapter 2 ■ Kubernetes on CoreOS
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Customizing the ClusterChapter 2
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Chapter 3 ■ Kubernetes on Google
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
PART IIAdministration andConfigurat
Page 107 and 108:
Chapter 4 ■ Using Multiple ZonesS
Page 109 and 110:
Chapter 4 ■ Using Multiple ZonesF
Page 111 and 112:
Page 113 and 114:
Chapter 4 ■ Using Multiple ZonesA
Page 115 and 116:
Page 117 and 118:
Chapter 4 ■ Using Multiple ZonesR
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Chapter 4 ■ Using Multiple ZonesL
Page 125 and 126:
Page 127 and 128:
Chapter 4 ■ Using Multiple ZonesI
Page 129 and 130:
Chapter 4 ■ Using Multiple ZonesC
Page 131 and 132:
Chapter 4 ■ Using Multiple ZonesA
Page 133 and 134:
Chapter 5 ■ Using the Tectonic Co
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Chapter 6 ■ Using VolumesPodDocke
Page 153 and 154:
Chapter 6 ■ Using VolumesObtain t
Page 155 and 156:
Chapter 6 ■ Using VolumesFigure 6
Page 157 and 158:
Chapter 6 ■ Using VolumesThe prec
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Chapter 6 ■ Using VolumesThe kube
Page 165 and 166: Chapter 6 ■ Using Volumesvolumes:
Page 167 and 168: Chapter 6 ■ Using VolumesChange d
Page 169 and 170: Chapter 7 ■ Using ServicesAnother
Page 171 and 172: Chapter 7 ■ Using ServicesCreatin
Page 173 and 174: Chapter 7 ■ Using ServicesSimilar
Page 175 and 176: Chapter 7 ■ Using ServicesList th
Page 177 and 178: Chapter 7 ■ Using ServicesFigure
Page 179 and 180: Chapter 7 ■ Using ServicesInvoke
Page 185 and 186: Chapter 7 ■ Using ServicesIn addi
Page 187 and 188: Chapter 8 ■ Using Rolling Updates
Page 215: Chapter 9 ■ Scheduling Pods on No
Page 219 and 220: Chapter 9 ■ Scheduling Pods on No
Page 253 and 254: Chapter 10 ■ Configuring Compute
Page 267 and 268:
Chapter 10 ■ Configuring Compute
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Chapter 11 ■ Using ConfigMapsIn t
Page 275 and 276:
Chapter 11 ■ Using ConfigMapsFigu
Page 277 and 278:
Chapter 11 ■ Using ConfigMapsNext
Page 279 and 280:
Chapter 11 ■ Using ConfigMapsThe
Page 281 and 282:
Chapter 11 ■ Using ConfigMapsCrea
Page 283 and 284:
Page 285 and 286:
Chapter 11 ■ Using ConfigMapsCrea
Page 287 and 288:
Page 289 and 290:
Chapter 11 ■ Using ConfigMapsCons
Page 291 and 292:
Chapter 11 ■ Using ConfigMapsmoun
Page 293 and 294:
CHAPTER 12Using Resource QuotasIn C
Page 295 and 296:
Chapter 12 ■ Using Resource Quota
Page 297 and 298:
Page 299 and 300:
Page 301 and 302:
Page 303 and 304:
Page 305 and 306:
Page 307 and 308:
Page 309 and 310:
Page 311 and 312:
Page 313 and 314:
CHAPTER 13Using AutoscalingStarting
Page 315 and 316:
Chapter 13 ■ Using AutoscalingThe
Page 317 and 318:
Chapter 13 ■ Using AutoscalingFig
Page 319 and 320:
Chapter 13 ■ Using Autoscaling./k
Page 321 and 322:
Chapter 13 ■ Using AutoscalingFig
Page 323 and 324:
CHAPTER 14Configuring LoggingLoggin
Page 325 and 326:
Chapter 14 ■ Configuring Logging
Page 327 and 328:
Docker Log FilesChapter 14 ■ Conf
Page 329 and 330:
Chapter 14 ■ Configuring LoggingF
Page 331 and 332:
Chapter 14 ■ Configuring LoggingC
Page 333 and 334:
Chapter 14 ■ Configuring Loggingv
Page 335 and 336:
Chapter 14 ■ Configuring LoggingI
Page 337 and 338:
Chapter 14 ■ Configuring LoggingT
Page 339 and 340:
Chapter 14 ■ Configuring Loggingt
Page 341 and 342:
Chapter 14 ■ Configuring LoggingT
Page 343 and 344:
Page 345 and 346:
Page 347 and 348:
CHAPTER 15Using an HA Master with O
Page 349 and 350:
Chapter 15 ■ Using an HA Master w
Page 351 and 352:
Installing the Network ManagerChapt
Page 353 and 354:
Page 355 and 356:
Page 357 and 358:
Page 359 and 360:
Page 361 and 362:
Page 363 and 364:
Page 365 and 366:
Page 367 and 368:
Chapter 16 ■ Developing a Highly
Page 369 and 370:
Page 371 and 372:
Page 373 and 374:
Page 375 and 376:
Page 377 and 378:
Page 379 and 380:
Page 381 and 382:
Page 383 and 384:
Page 385 and 386:
Page 387 and 388:
Page 389 and 390:
Page 391 and 392:
Page 393 and 394:
Page 395 and 396:
Page 397 and 398:
Page 399 and 400:
Page 401 and 402:
Page 403 and 404:
Page 405 and 406:
■ INDEXClusters (cont.)configurat
Page 407 and 408:
■ INDEXKubernetes (cont.)nodes, 6
Page 409 and 410:
■ INDEXRoute 53 service (cont.)de
show all

148422597X Kubernetes Management Design Patterns [Vohra 2017-01-29] {E559F6BB}

Create successful ePaper yourself

Delete template?

Save as template?