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

Recommendations

Info

Chapter 13 ■ Using Autoscaling1 Pod3 Pods5 PodsFigure 13-1. Increasing the load increases the number of podsAn HPA has two main benefits over user-intervened scaling: the scaling is automatic, and extra podsare not kept running consuming resources that could be used for some other application. An autoscaler maybe created for a replication controller, replica set, or deployment. An autoscaler uses heapster to collectCPU utilization of a resource, based on which it determines whether more or fewer pods should be run.Autoscaling is based on a target CPU utilization, implying that the CPU utilization of a resource such as adeployment should be x%.OverviewIn this chapter we shall demonstrate the use of autoscaling. This chapter discusses the following topics.Setting the environmentRunning PHP Apache Server deploymentCreating a serviceCreating a horizontal pod autoscalerIncreasing loadSetting the EnvironmentCreate a Kubernetes cluster running as a CoreOS AWS CloudFormation consisting of one controller nodeand three worker nodes. List the nodes:./kubectl get nodes300
Chapter 13 ■ Using AutoscalingThe single controller node and the worker nodes should be listed as shown in Figure 13-2.Figure 13-2. Listing Kubernetes nodesList the services across all namespaces as shown in Figure 13-3. The heapster service, which monitorsthe CPU utilization, should be listed in the kube-system namespace.Figure 13-3. Listing services across all namespacesList pods across all the namespaces, and the heapster pod should be listed as shown in Figure 13-4.Figure 13-4. Listing pods across all namespaces301
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 181 and 182:
Page 183 and 184:
Page 185 and 186:
Chapter 7 ■ Using ServicesIn addi
Page 187 and 188:
Chapter 8 ■ Using Rolling Updates
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Chapter 9 ■ Scheduling Pods on No
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Chapter 10 ■ Configuring Compute
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264: Chapter 10 ■ Configuring Compute
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 285 and 286: Chapter 11 ■ Using ConfigMapsCrea
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 313: CHAPTER 13Using AutoscalingStarting
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 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 365 and 366:
Chapter 15 ■ Using an HA Master w
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?