148422597X Kubernetes Management Design Patterns [Vohra 2017-01-29] {E559F6BB}
Chapter 3 ■ Kubernetes on Google Cloud PlatformThe Google Compute Engine API should be listed in the Dashboard as shown in Figure 3-24.Figure 3-24. Google Compute Engine API listed as EnabledAs indicated by the message A project is needed to enable APIs in Figure 3-25, to enable the GoogleCompute Engine API a project is required.Figure 3-25. A project is needed to enable APIs61
Chapter 3 ■ Kubernetes on Google Cloud PlatformCreating a VM InstanceThe Compute Engine API provisions virtual machine instances. To create a VM instance, navigate to the VMInstances page at https://console.cloud.google.com/compute/instances. In the Compute Engine dialog,click Create Instance as shown in Figure 3-26.Figure 3-26. Clicking on Create InstanceIn the Create an instance page, specify an instance name (vm-kube-gce for example). Select a Zone,Machine Type, Identity, and API Access as shown in Figure 3-27.62
- 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 and 56: Chapter 2 ■ Kubernetes on CoreOS
- Page 57 and 58: 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: 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
- Page 107 and 108: Chapter 4 ■ Using Multiple ZonesS
- Page 109 and 110: Chapter 4 ■ Using Multiple ZonesF
- Page 111 and 112: Chapter 4 ■ Using Multiple ZonesF
- Page 113 and 114: Chapter 4 ■ Using Multiple ZonesA
- Page 115 and 116: Chapter 4 ■ Using Multiple ZonesF
- Page 117 and 118: Chapter 4 ■ Using Multiple ZonesR
- Page 119 and 120: Chapter 4 ■ Using Multiple ZonesF
- Page 121 and 122: Chapter 4 ■ Using Multiple ZonesF
- Page 123 and 124: Chapter 4 ■ Using Multiple ZonesL
- Page 125 and 126: Chapter 4 ■ Using Multiple ZonesF
- Page 127 and 128: Chapter 4 ■ Using Multiple ZonesI
Chapter 3 ■ Kubernetes on Google Cloud Platform
The Google Compute Engine API should be listed in the Dashboard as shown in Figure 3-24.
Figure 3-24. Google Compute Engine API listed as Enabled
As indicated by the message A project is needed to enable APIs in Figure 3-25, to enable the Google
Compute Engine API a project is required.
Figure 3-25. A project is needed to enable APIs
61