![148422597X Kubernetes Management Design Patterns [Vohra 2017-01-29] {E559F6BB}](https://documents.yumpu.com/000/065/726/563/004114de54e45591c9e60ff7561f9a6a79b64780/3936726d307573422b67724e435173486158323441413d3d/594770706731334a4f334e67434f6e6573594e5374773d3d.jpg?AWSAccessKeyId=AKIAICNEWSPSEKTJ5M3Q&Expires=1726570800&Signature=kQ8zvDne8IDHcYxkBGmEn%2BaU3Jc%3D)
148422597X Kubernetes Management Design Patterns [Vohra 2017-01-29] {E559F6BB}
Chapter 2 ■ Kubernetes on CoreOS on AWSClick on Save Changes to save the modifications to the A record as shown in Figure 2-16.Figure 2-16. Saving changes to the A recordThe A record should list the Points To as the public IP address of the controller instance as shown inFigure 2-17.38
Chapter 2 ■ Kubernetes on CoreOS on AWSFigure 2-17. The updated A recordAccessing the ClusterDownload the kubectl binaries, which are used to manage the Kubernetes cluster. Set access permissions tothe kubectl binaries to make them executable, and move the kubectl binaries to /usr/local/bin, which isin the path:sudo wget https://storage.googleapis.com/kubernetes-release/release/v1.3.0/bin/linux/amd64/kubectlsudo chmod +x kubectlsudo mv kubectl /usr/local/bin/Using the kubectl config file access the cluster to list the nodes. The one controller node and the threeworker nodes should be listed as shown in Figure 2-18. The controller node is not schedulable by default,which implies that pods cannot be run on the node.Figure 2-18. Listing the Kubernetes cluster nodes39
- 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: Chapter 1 ■ Kubernetes on AWSFigu
- Page 33 and 34: Chapter 1 ■ Kubernetes on AWSFigu
- Page 35 and 36: Testing the ClusterChapter 1 ■ Ku
- Page 37 and 38: Chapter 1 ■ Kubernetes on AWSFigu
- Page 39 and 40: Chapter 1 ■ Kubernetes on AWSFigu
- Page 41 and 42: CHAPTER 2Kubernetes on CoreOS on AW
- Page 43 and 44: Chapter 2 ■ Kubernetes on CoreOS
- Page 45 and 46: Chapter 2 ■ Kubernetes on CoreOS
- Page 47 and 48: Chapter 2 ■ Kubernetes on CoreOS
- Page 49 and 50: Customizing the ClusterChapter 2
- Page 51 and 52: Chapter 2 ■ Kubernetes on CoreOS
- Page 53 and 54: Chapter 2 ■ Kubernetes on CoreOS
- Page 55: Chapter 2 ■ Kubernetes on CoreOS
- Page 59 and 60: Chapter 2 ■ Kubernetes on CoreOS
- Page 61 and 62: Chapter 2 ■ Kubernetes on CoreOS
- Page 63 and 64: Chapter 2 ■ Kubernetes on CoreOS
- Page 65 and 66: Chapter 2 ■ Kubernetes on CoreOS
- Page 67 and 68: Chapter 3 ■ Kubernetes on Google
- Page 69 and 70: Chapter 3 ■ Kubernetes on Google
- Page 71 and 72: Chapter 3 ■ Kubernetes on Google
- Page 73 and 74: Chapter 3 ■ Kubernetes on Google
- Page 75 and 76: Chapter 3 ■ Kubernetes on Google
- Page 77 and 78: Chapter 3 ■ Kubernetes on Google
- Page 79 and 80: Chapter 3 ■ Kubernetes on Google
- Page 81 and 82: Chapter 3 ■ Kubernetes on Google
- Page 83 and 84: Chapter 3 ■ Kubernetes on Google
- Page 85 and 86: Chapter 3 ■ Kubernetes on Google
- Page 87 and 88: Chapter 3 ■ Kubernetes on Google
- Page 89 and 90: Chapter 3 ■ Kubernetes on Google
- Page 91 and 92: Chapter 3 ■ Kubernetes on Google
- Page 93 and 94: Chapter 3 ■ Kubernetes on Google
- Page 95 and 96: Chapter 3 ■ Kubernetes on Google
- Page 97 and 98: Chapter 3 ■ Kubernetes on Google
- Page 99 and 100: Chapter 3 ■ Kubernetes on Google
- Page 101 and 102: Chapter 3 ■ Kubernetes on Google
- Page 103 and 104: Chapter 3 ■ Kubernetes on Google
- Page 105 and 106: PART IIAdministration andConfigurat
Chapter 2 ■ Kubernetes on CoreOS on AWS
Click on Save Changes to save the modifications to the A record as shown in Figure 2-16.
Figure 2-16. Saving changes to the A record
The A record should list the Points To as the public IP address of the controller instance as shown in
Figure 2-17.
38
Change language