Tag Archives: kubernetes

Kubernetes Cluster on Azure and Expose Couchbase Service

June 1, 2016containers, couchbaseazure, couchbase, kubernetesarungupta

This blog is part of a multi-part blog series that shows how to run your applications on Kubernetes. It will use the Couchbase, an open source NoSQL distributed document database, as the Docker container.

Part 1 explained how to start Kubernetes cluster using Vagrant – Kubernetes on Vagrant
Part 2 did the same for Amazon Web Services – Kubernetes on Amazon Web Services
Part 3 did the same for Google Cloud – Kubernetes on Google Cloud

This fourth part will show:

How to setup and start the Kubernetes cluster on Azure
Run Docker container in the Kubernetes cluster
Expose Pod on Kubernetes as Service
Shutdown the cluster

Many thanks to @colemickens for helping me through this recipe. This blog content is heavily based upon the instructions at colemickens.github.io/docs/getting-started-guides/azure/.

Install and Configure Azure CLI

Azure CLI is a command-line interface to develop, deploy and manage Azure applications. This is needed in order to install Kubernetes cluster on Azure.

Install Node:

brew install node
==> Downloading https://homebrew.bintray.com/bottles/node-6.2.0.yosemite.bottle.tar.gz
######################################################################## 100.0%
==> Pouring node-6.2.0.yosemite.bottle.tar.gz
==> Caveats
Please note by default only English locale support is provided. If you need
full locale support you should either rebuild with full icu:
  `brew reinstall node --with-full-icu`
or add full icu data at runtime following:
  https://github.com/nodejs/node/wiki/Intl#using-and-customizing-the-small-icu-build

Bash completion has been installed to:
  /usr/local/etc/bash_completion.d
==> Summary
🍺  /usr/local/Cellar/node/6.2.0: 3,979 files, 40.4M

brew install node

==> Downloading https://homebrew.bintray.com/bottles/node-6.2.0.yosemite.bottle.tar.gz

######################################################################## 100.0%

==> Pouring node-6.2.0.yosemite.bottle.tar.gz

==> Caveats

Please note by default only English locale support is provided. If you need

full locale support you should either rebuild with full icu:

`brew reinstall node --with-full-icu`

or add full icu data at runtime following:

https://github.com/nodejs/node/wiki/Intl#using-and-customizing-the-small-icu-build

Bash completion has been installed to:

/usr/local/etc/bash_completion.d

==> Summary

🍺 /usr/local/Cellar/node/6.2.0: 3,979 files, 40.4M

Install Azure CLI:

npm install -g azure-cli
/usr/local/bin/azure -> /usr/local/lib/node_modules/azure-cli/bin/azure

> fibers@1.0.13 install /usr/local/lib/node_modules/azure-cli/node_modules/fibers
> node build.js || nodejs build.js

`darwin-x64-v8-5.0` exists; testing
Binary is fine; exiting
/usr/local/lib
└─┬ azure-cli@0.10.0
  ├─┬ adal-node@0.1.17
  │ ├── date-utils@1.2.21
  │ ├─┬ jws@3.1.3
  │ │ ├─┬ base64url@1.0.6
  │ │ │ └─┬ meow@2.0.0
  │ │ │   ├─┬ camelcase-keys@1.0.0
  │ │ │   │ ├── camelcase@1.2.1
  │ │ │   │ └── map-obj@1.0.1
  │ │ │   ├─┬ indent-string@1.2.2
  │ │ │   │ ├── get-stdin@4.0.1
  │ │ │   │ └─┬ repeating@1.1.3
  │ │ │   │   └── is-finite@1.0.1
  │ │ │   ├── minimist@1.2.0
  │ │ │   └── object-assign@1.0.0
  │ │ └─┬ jwa@1.1.3
  │ │   ├── buffer-equal-constant-time@1.0.1
  │ │   └─┬ ecdsa-sig-formatter@1.0.5
  │ │     └── base64-url@1.2.2
  │ ├── node-uuid@1.4.1
  │ ├── xmldom@0.1.22
  │ └── xpath.js@1.0.6
  ├── applicationinsights@0.15.12
  ├── async@1.4.2
  ├── azure-arm-authorization@2.0.0
  ├── azure-arm-batch@0.1.0
  ├── azure-arm-cdn@0.1.0-preview
  ├── azure-arm-commerce@0.1.1
  ├── azure-arm-compute@0.18.0
  ├── azure-arm-datalake-analytics@0.3.2
  ├── azure-arm-datalake-store@0.3.0
  ├── azure-arm-dns@0.10.1
  ├── azure-arm-hdinsight@0.2.0
  ├── azure-arm-hdinsight-jobs@0.1.0
  ├── azure-arm-insights@0.11.1
  ├── azure-arm-network@0.13.1
  ├── azure-arm-rediscache@0.2.1
  ├── azure-arm-resource@1.4.4-preview
  ├── azure-arm-storage@0.13.1-preview
  ├── azure-arm-trafficmanager@0.10.5
  ├─┬ azure-arm-website@0.10.0
  │ ├─┬ azure-common@0.9.12
  │ │ ├─┬ request@2.45.0
  │ │ │ ├── aws-sign2@0.5.0
  │ │ │ ├── bl@0.9.5
  │ │ │ ├── caseless@0.6.0
  │ │ │ ├── forever-agent@0.5.2
  │ │ │ ├─┬ form-data@0.1.4
  │ │ │ │ ├── async@0.9.2
  │ │ │ │ └─┬ combined-stream@0.0.7
  │ │ │ │   └── delayed-stream@0.0.5
  │ │ │ ├─┬ hawk@1.1.1
  │ │ │ │ ├── boom@0.4.2
  │ │ │ │ ├── cryptiles@0.2.2
  │ │ │ │ ├── hoek@0.9.1
  │ │ │ │ └── sntp@0.2.4
  │ │ │ ├─┬ http-signature@0.10.1
  │ │ │ │ ├── asn1@0.1.11
  │ │ │ │ └── assert-plus@0.1.5
  │ │ │ ├── mime-types@1.0.2
  │ │ │ ├── node-uuid@1.4.7
  │ │ │ ├── oauth-sign@0.4.0
  │ │ │ └── qs@1.2.2
  │ │ └── xml2js@0.2.7
  │ └── moment@2.6.0
  ├── azure-asm-compute@0.15.0
  ├── azure-asm-hdinsight@0.10.2
  ├── azure-asm-mgmt@0.10.1
  ├── azure-asm-network@0.11.0
  ├── azure-asm-sb@0.10.1
  ├── azure-asm-sql@0.10.1
  ├── azure-asm-storage@0.10.1
  ├── azure-asm-subscription@0.10.1
  ├── azure-asm-trafficmanager@0.10.3
  ├─┬ azure-asm-website@0.10.1
  │ └── moment@2.6.0
  ├── azure-batch@0.3.0
  ├─┬ azure-common@0.9.16
  │ ├── dateformat@1.0.2-1.2.3
  │ ├── duplexer@0.1.1
  │ ├── envconf@0.0.4
  │ ├─┬ request@2.45.0
  │ │ ├── aws-sign2@0.5.0
  │ │ ├── bl@0.9.5
  │ │ ├── caseless@0.6.0
  │ │ ├── forever-agent@0.5.2
  │ │ ├─┬ form-data@0.1.4
  │ │ │ ├── async@0.9.2
  │ │ │ ├─┬ combined-stream@0.0.7
  │ │ │ │ └── delayed-stream@0.0.5
  │ │ │ └── mime@1.2.11
  │ │ ├─┬ hawk@1.1.1
  │ │ │ ├── boom@0.4.2
  │ │ │ ├── cryptiles@0.2.2
  │ │ │ ├── hoek@0.9.1
  │ │ │ └── sntp@0.2.4
  │ │ ├─┬ http-signature@0.10.1
  │ │ │ ├── asn1@0.1.11
  │ │ │ ├── assert-plus@0.1.5
  │ │ │ └── ctype@0.5.3
  │ │ ├── mime-types@1.0.2
  │ │ ├── node-uuid@1.4.7
  │ │ ├── oauth-sign@0.4.0
  │ │ └── qs@1.2.2
  │ ├── validator@3.22.2
  │ └── xml2js@0.2.7
  ├── azure-gallery@2.0.0-pre.18
  ├── azure-graph@0.1.1
  ├─┬ azure-keyvault@0.10.1
  │ └── node-uuid@1.4.7
  ├─┬ azure-monitoring@0.10.2
  │ └── moment@2.6.0
  ├─┬ azure-storage@0.7.0
  │ ├── browserify-mime@1.2.9
  │ ├── extend@1.2.1
  │ ├── node-uuid@1.4.7
  │ ├─┬ readable-stream@2.0.6
  │ │ ├── isarray@1.0.0
  │ │ ├── process-nextick-args@1.0.7
  │ │ └── util-deprecate@1.0.2
  │ ├─┬ request@2.57.0
  │ │ ├── aws-sign2@0.5.0
  │ │ ├─┬ bl@0.9.5
  │ │ │ └─┬ readable-stream@1.0.34
  │ │ │   └── isarray@0.0.1
  │ │ ├── caseless@0.10.0
  │ │ ├─┬ form-data@0.2.0
  │ │ │ ├── async@0.9.2
  │ │ │ └─┬ combined-stream@0.0.7
  │ │ │   └── delayed-stream@0.0.5
  │ │ ├─┬ har-validator@1.8.0
  │ │ │ ├── bluebird@2.10.2
  │ │ │ └── commander@2.9.0
  │ │ ├── hawk@2.3.1
  │ │ ├─┬ http-signature@0.11.0
  │ │ │ ├── asn1@0.1.11
  │ │ │ └── assert-plus@0.1.5
  │ │ ├─┬ mime-types@2.0.14
  │ │ │ └── mime-db@1.12.0
  │ │ └── qs@3.1.0
  │ ├── validator@3.22.2
  │ └── xml2js@0.2.7
  ├─┬ caller-id@0.1.0
  │ └── stack-trace@0.0.9
  ├── colors@0.6.2
  ├─┬ commander@1.0.4
  │ └── keypress@0.1.0
  ├── easy-table@0.0.1
  ├─┬ event-stream@3.1.5
  │ ├── from@0.1.3
  │ ├── map-stream@0.1.0
  │ ├── pause-stream@0.0.11
  │ ├── split@0.2.10
  │ └── stream-combiner@0.0.4
  ├── eyes@0.1.8
  ├── fast-json-patch@0.5.6
  ├── github@0.1.6
  ├── js2xmlparser@1.0.0
  ├── jsrsasign@4.8.2
  ├─┬ kuduscript@1.0.6
  │ ├── commander@1.1.1
  │ └── streamline@0.4.11
  ├── moment@2.13.0
  ├── ms-rest@1.14.2
  ├─┬ ms-rest-azure@1.14.2
  │ ├── async@0.2.7
  │ └── uuid@2.0.1
  ├── node-forge@0.6.23
  ├── node-uuid@1.2.0
  ├── number-is-nan@1.0.0
  ├── omelette@0.1.0
  ├─┬ openssl-wrapper@0.2.1
  │ ├── debug@0.7.4
  │ └── q@0.9.7
  ├─┬ read@1.0.7
  │ └── mute-stream@0.0.6
  ├─┬ readable-stream@1.0.34
  │ ├── core-util-is@1.0.2
  │ ├── inherits@2.0.1
  │ ├── isarray@0.0.1
  │ └── string_decoder@0.10.31
  ├─┬ request@2.69.0
  │ ├── aws-sign2@0.6.0
  │ ├── aws4@1.4.1
  │ ├─┬ bl@1.0.3
  │ │ └─┬ readable-stream@2.0.6
  │ │   └── isarray@1.0.0
  │ ├── caseless@0.11.0
  │ ├─┬ combined-stream@1.0.5
  │ │ └── delayed-stream@1.0.0
  │ ├── extend@3.0.0
  │ ├── forever-agent@0.6.1
  │ ├─┬ form-data@1.0.0-rc4
  │ │ └── async@1.5.2
  │ ├─┬ har-validator@2.0.6
  │ │ ├─┬ chalk@1.1.3
  │ │ │ ├── ansi-styles@2.2.1
  │ │ │ ├── escape-string-regexp@1.0.5
  │ │ │ ├─┬ has-ansi@2.0.0
  │ │ │ │ └── ansi-regex@2.0.0
  │ │ │ ├── strip-ansi@3.0.1
  │ │ │ └── supports-color@2.0.0
  │ │ ├─┬ commander@2.9.0
  │ │ │ └── graceful-readlink@1.0.1
  │ │ ├─┬ is-my-json-valid@2.13.1
  │ │ │ ├── generate-function@2.0.0
  │ │ │ ├─┬ generate-object-property@1.2.0
  │ │ │ │ └── is-property@1.0.2
  │ │ │ ├── jsonpointer@2.0.0
  │ │ │ └── xtend@4.0.1
  │ │ └─┬ pinkie-promise@2.0.1
  │ │   └── pinkie@2.0.4
  │ ├─┬ hawk@3.1.3
  │ │ ├── boom@2.10.1
  │ │ ├── cryptiles@2.0.5
  │ │ ├── hoek@2.16.3
  │ │ └── sntp@1.0.9
  │ ├─┬ http-signature@1.1.1
  │ │ ├── assert-plus@0.2.0
  │ │ ├─┬ jsprim@1.2.2
  │ │ │ ├── extsprintf@1.0.2
  │ │ │ ├── json-schema@0.2.2
  │ │ │ └── verror@1.3.6
  │ │ └─┬ sshpk@1.8.3
  │ │   ├── asn1@0.2.3
  │ │   ├── assert-plus@1.0.0
  │ │   ├─┬ dashdash@1.13.1
  │ │   │ └── assert-plus@1.0.0
  │ │   ├── ecc-jsbn@0.1.1
  │ │   ├─┬ getpass@0.1.6
  │ │   │ └── assert-plus@1.0.0
  │ │   ├── jodid25519@1.0.2
  │ │   ├── jsbn@0.1.0
  │ │   └── tweetnacl@0.13.3
  │ ├── is-typedarray@1.0.0
  │ ├── isstream@0.1.2
  │ ├── json-stringify-safe@5.0.1
  │ ├─┬ mime-types@2.1.11
  │ │ └── mime-db@1.23.0
  │ ├── node-uuid@1.4.7
  │ ├── oauth-sign@0.8.2
  │ ├── qs@6.0.2
  │ ├── stringstream@0.0.5
  │ ├── tough-cookie@2.2.2
  │ └── tunnel-agent@0.4.3
  ├─┬ ssh-key-to-pem@0.11.0
  │ ├── asn1@0.1.11
  │ └── ctype@0.5.2
  ├─┬ streamline@0.10.17
  │ ├── fibers@1.0.13
  │ ├── galaxy@0.1.12
  │ └─┬ source-map@0.1.43
  │   └── amdefine@1.0.0
  ├── streamline-streams@0.1.5
  ├─┬ sync-request@3.0.0
  │ ├─┬ concat-stream@1.4.10
  │ │ ├── readable-stream@1.1.14
  │ │ └── typedarray@0.0.6
  │ ├── http-response-object@1.1.0
  │ └─┬ then-request@2.2.0
  │   ├── http-basic@2.5.1
  │   ├─┬ promise@7.1.1
  │   │ └── asap@2.0.4
  │   └── qs@6.2.0
  ├── through@2.3.4
  ├── tunnel@0.0.2
  ├── underscore@1.4.4
  ├── validator@3.1.0
  ├─┬ winston@0.6.2
  │ ├── async@0.1.22
  │ ├── cycle@1.0.3
  │ ├── pkginfo@0.2.3
  │ └── request@2.9.203
  ├── wordwrap@0.0.2
  ├─┬ xml2js@0.1.14
  │ └── sax@0.5.2
  └── xmlbuilder@0.4.3

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

146

147

148

149

150

151

152

153

154

155

156

157

158

159

160

161

162

163

164

165

166

167

168

169

170

171

172

173

174

175

176

177

178

179

180

181

182

183

184

185

186

187

188

189

190

191

192

193

194

195

196

197

198

199

200

201

202

203

204

205

206

207

208

209

210

211

212

213

214

215

216

217

218

219

220

221

222

223

224

225

226

227

228

229

230

231

232

233

234

235

236

237

238

239

240

241

242

243

244

245

246

247

248

249

250

251

252

253

254

255

256

257

258

259

260

261

262

263

264

265

266

267

268

269

270

271

272

273

274

275

276

277

278

279

280

281

282

283

284

285

286

287

288

npm install -g azure-cli

/usr/local/bin/azure -> /usr/local/lib/node_modules/azure-cli/bin/azure

> fibers@1.0.13 install /usr/local/lib/node_modules/azure-cli/node_modules/fibers

> node build.js || nodejs build.js

`darwin-x64-v8-5.0` exists; testing

Binary is fine; exiting

/usr/local/lib

└─┬ azure-cli@0.10.0

├─┬ adal-node@0.1.17

│ ├── date-utils@1.2.21

│ ├─┬ jws@3.1.3

│ │ ├─┬ base64url@1.0.6

│ │ │ └─┬ meow@2.0.0

│ │ │ ├─┬ camelcase-keys@1.0.0

│ │ │ │ ├── camelcase@1.2.1

│ │ │ │ └── map-obj@1.0.1

│ │ │ ├─┬ indent-string@1.2.2

│ │ │ │ ├── get-stdin@4.0.1

│ │ │ │ └─┬ repeating@1.1.3

│ │ │ │ └── is-finite@1.0.1

│ │ │ ├── minimist@1.2.0

│ │ │ └── object-assign@1.0.0

│ │ └─┬ jwa@1.1.3

│ │ ├── buffer-equal-constant-time@1.0.1

│ │ └─┬ ecdsa-sig-formatter@1.0.5

│ │ └── base64-url@1.2.2

│ ├── node-uuid@1.4.1

│ ├── xmldom@0.1.22

│ └── xpath.js@1.0.6

├── applicationinsights@0.15.12

├── async@1.4.2

├── azure-arm-authorization@2.0.0

├── azure-arm-batch@0.1.0

├── azure-arm-cdn@0.1.0-preview

├── azure-arm-commerce@0.1.1

├── azure-arm-compute@0.18.0

├── azure-arm-datalake-analytics@0.3.2

├── azure-arm-datalake-store@0.3.0

├── azure-arm-dns@0.10.1

├── azure-arm-hdinsight@0.2.0

├── azure-arm-hdinsight-jobs@0.1.0

├── azure-arm-insights@0.11.1

├── azure-arm-network@0.13.1

├── azure-arm-rediscache@0.2.1

├── azure-arm-resource@1.4.4-preview

├── azure-arm-storage@0.13.1-preview

├── azure-arm-trafficmanager@0.10.5

├─┬ azure-arm-website@0.10.0

│ ├─┬ azure-common@0.9.12

│ │ ├─┬ request@2.45.0

│ │ │ ├── aws-sign2@0.5.0

│ │ │ ├── bl@0.9.5

│ │ │ ├── caseless@0.6.0

│ │ │ ├── forever-agent@0.5.2

│ │ │ ├─┬ form-data@0.1.4

│ │ │ │ ├── async@0.9.2

│ │ │ │ └─┬ combined-stream@0.0.7

│ │ │ │ └── delayed-stream@0.0.5

│ │ │ ├─┬ hawk@1.1.1

│ │ │ │ ├── boom@0.4.2

│ │ │ │ ├── cryptiles@0.2.2

│ │ │ │ ├── hoek@0.9.1

│ │ │ │ └── sntp@0.2.4

│ │ │ ├─┬ http-signature@0.10.1

│ │ │ │ ├── asn1@0.1.11

│ │ │ │ └── assert-plus@0.1.5

│ │ │ ├── mime-types@1.0.2

│ │ │ ├── node-uuid@1.4.7

│ │ │ ├── oauth-sign@0.4.0

│ │ │ └── qs@1.2.2

│ │ └── xml2js@0.2.7

│ └── moment@2.6.0

├── azure-asm-compute@0.15.0

├── azure-asm-hdinsight@0.10.2

├── azure-asm-mgmt@0.10.1

├── azure-asm-network@0.11.0

├── azure-asm-sb@0.10.1

├── azure-asm-sql@0.10.1

├── azure-asm-storage@0.10.1

├── azure-asm-subscription@0.10.1

├── azure-asm-trafficmanager@0.10.3

├─┬ azure-asm-website@0.10.1

│ └── moment@2.6.0

├── azure-batch@0.3.0

├─┬ azure-common@0.9.16

│ ├── dateformat@1.0.2-1.2.3

│ ├── duplexer@0.1.1

│ ├── envconf@0.0.4

│ ├─┬ request@2.45.0

│ │ ├── aws-sign2@0.5.0

│ │ ├── bl@0.9.5

│ │ ├── caseless@0.6.0

│ │ ├── forever-agent@0.5.2

│ │ ├─┬ form-data@0.1.4

│ │ │ ├── async@0.9.2

│ │ │ ├─┬ combined-stream@0.0.7

│ │ │ │ └── delayed-stream@0.0.5

│ │ │ └── mime@1.2.11

│ │ ├─┬ hawk@1.1.1

│ │ │ ├── boom@0.4.2

│ │ │ ├── cryptiles@0.2.2

│ │ │ ├── hoek@0.9.1

│ │ │ └── sntp@0.2.4

│ │ ├─┬ http-signature@0.10.1

│ │ │ ├── asn1@0.1.11

│ │ │ ├── assert-plus@0.1.5

│ │ │ └── ctype@0.5.3

│ │ ├── mime-types@1.0.2

│ │ ├── node-uuid@1.4.7

│ │ ├── oauth-sign@0.4.0

│ │ └── qs@1.2.2

│ ├── validator@3.22.2

│ └── xml2js@0.2.7

├── azure-gallery@2.0.0-pre.18

├── azure-graph@0.1.1

├─┬ azure-keyvault@0.10.1

│ └── node-uuid@1.4.7

├─┬ azure-monitoring@0.10.2

│ └── moment@2.6.0

├─┬ azure-storage@0.7.0

│ ├── browserify-mime@1.2.9

│ ├── extend@1.2.1

│ ├── node-uuid@1.4.7

│ ├─┬ readable-stream@2.0.6

│ │ ├── isarray@1.0.0

│ │ ├── process-nextick-args@1.0.7

│ │ └── util-deprecate@1.0.2

│ ├─┬ request@2.57.0

│ │ ├── aws-sign2@0.5.0

│ │ ├─┬ bl@0.9.5

│ │ │ └─┬ readable-stream@1.0.34

│ │ │ └── isarray@0.0.1

│ │ ├── caseless@0.10.0

│ │ ├─┬ form-data@0.2.0

│ │ │ ├── async@0.9.2

│ │ │ └─┬ combined-stream@0.0.7

│ │ │ └── delayed-stream@0.0.5

│ │ ├─┬ har-validator@1.8.0

│ │ │ ├── bluebird@2.10.2

│ │ │ └── commander@2.9.0

│ │ ├── hawk@2.3.1

│ │ ├─┬ http-signature@0.11.0

│ │ │ ├── asn1@0.1.11

│ │ │ └── assert-plus@0.1.5

│ │ ├─┬ mime-types@2.0.14

│ │ │ └── mime-db@1.12.0

│ │ └── qs@3.1.0

│ ├── validator@3.22.2

│ └── xml2js@0.2.7

├─┬ caller-id@0.1.0

│ └── stack-trace@0.0.9

├── colors@0.6.2

├─┬ commander@1.0.4

│ └── keypress@0.1.0

├── easy-table@0.0.1

├─┬ event-stream@3.1.5

│ ├── from@0.1.3

│ ├── map-stream@0.1.0

│ ├── pause-stream@0.0.11

│ ├── split@0.2.10

│ └── stream-combiner@0.0.4

├── eyes@0.1.8

├── fast-json-patch@0.5.6

├── github@0.1.6

├── js2xmlparser@1.0.0

├── jsrsasign@4.8.2

├─┬ kuduscript@1.0.6

│ ├── commander@1.1.1

│ └── streamline@0.4.11

├── moment@2.13.0

├── ms-rest@1.14.2

├─┬ ms-rest-azure@1.14.2

│ ├── async@0.2.7

│ └── uuid@2.0.1

├── node-forge@0.6.23

├── node-uuid@1.2.0

├── number-is-nan@1.0.0

├── omelette@0.1.0

├─┬ openssl-wrapper@0.2.1

│ ├── debug@0.7.4

│ └── q@0.9.7

├─┬ read@1.0.7

│ └── mute-stream@0.0.6

├─┬ readable-stream@1.0.34

│ ├── core-util-is@1.0.2

│ ├── inherits@2.0.1

│ ├── isarray@0.0.1

│ └── string_decoder@0.10.31

├─┬ request@2.69.0

│ ├── aws-sign2@0.6.0

│ ├── aws4@1.4.1

│ ├─┬ bl@1.0.3

│ │ └─┬ readable-stream@2.0.6

│ │ └── isarray@1.0.0

│ ├── caseless@0.11.0

│ ├─┬ combined-stream@1.0.5

│ │ └── delayed-stream@1.0.0

│ ├── extend@3.0.0

│ ├── forever-agent@0.6.1

│ ├─┬ form-data@1.0.0-rc4

│ │ └── async@1.5.2

│ ├─┬ har-validator@2.0.6

│ │ ├─┬ chalk@1.1.3

│ │ │ ├── ansi-styles@2.2.1

│ │ │ ├── escape-string-regexp@1.0.5

│ │ │ ├─┬ has-ansi@2.0.0

│ │ │ │ └── ansi-regex@2.0.0

│ │ │ ├── strip-ansi@3.0.1

│ │ │ └── supports-color@2.0.0

│ │ ├─┬ commander@2.9.0

│ │ │ └── graceful-readlink@1.0.1

│ │ ├─┬ is-my-json-valid@2.13.1

│ │ │ ├── generate-function@2.0.0

│ │ │ ├─┬ generate-object-property@1.2.0

│ │ │ │ └── is-property@1.0.2

│ │ │ ├── jsonpointer@2.0.0

│ │ │ └── xtend@4.0.1

│ │ └─┬ pinkie-promise@2.0.1

│ │ └── pinkie@2.0.4

│ ├─┬ hawk@3.1.3

│ │ ├── boom@2.10.1

│ │ ├── cryptiles@2.0.5

│ │ ├── hoek@2.16.3

│ │ └── sntp@1.0.9

│ ├─┬ http-signature@1.1.1

│ │ ├── assert-plus@0.2.0

│ │ ├─┬ jsprim@1.2.2

│ │ │ ├── extsprintf@1.0.2

│ │ │ ├── json-schema@0.2.2

│ │ │ └── verror@1.3.6

│ │ └─┬ sshpk@1.8.3

│ │ ├── asn1@0.2.3

│ │ ├── assert-plus@1.0.0

│ │ ├─┬ dashdash@1.13.1

│ │ │ └── assert-plus@1.0.0

│ │ ├── ecc-jsbn@0.1.1

│ │ ├─┬ getpass@0.1.6

│ │ │ └── assert-plus@1.0.0

│ │ ├── jodid25519@1.0.2

│ │ ├── jsbn@0.1.0

│ │ └── tweetnacl@0.13.3

│ ├── is-typedarray@1.0.0

│ ├── isstream@0.1.2

│ ├── json-stringify-safe@5.0.1

│ ├─┬ mime-types@2.1.11

│ │ └── mime-db@1.23.0

│ ├── node-uuid@1.4.7

│ ├── oauth-sign@0.8.2

│ ├── qs@6.0.2

│ ├── stringstream@0.0.5

│ ├── tough-cookie@2.2.2

│ └── tunnel-agent@0.4.3

├─┬ ssh-key-to-pem@0.11.0

│ ├── asn1@0.1.11

│ └── ctype@0.5.2

├─┬ streamline@0.10.17

│ ├── fibers@1.0.13

│ ├── galaxy@0.1.12

│ └─┬ source-map@0.1.43

│ └── amdefine@1.0.0

├── streamline-streams@0.1.5

├─┬ sync-request@3.0.0

│ ├─┬ concat-stream@1.4.10

│ │ ├── readable-stream@1.1.14

│ │ └── typedarray@0.0.6

│ ├── http-response-object@1.1.0

│ └─┬ then-request@2.2.0

│ ├── http-basic@2.5.1

│ ├─┬ promise@7.1.1

│ │ └── asap@2.0.4

│ └── qs@6.2.0

├── through@2.3.4

├── tunnel@0.0.2

├── underscore@1.4.4

├── validator@3.1.0

├─┬ winston@0.6.2

│ ├── async@0.1.22

│ ├── cycle@1.0.3

│ ├── pkginfo@0.2.3

│ └── request@2.9.203

├── wordwrap@0.0.2

├─┬ xml2js@0.1.14

│ └── sax@0.5.2

└── xmlbuilder@0.4.3

azure login
info:    Executing command login
\info:    To sign in, use a web browser to open the page https://aka.ms/devicelogin. Enter the code BS5P64ANU to authenticate.
|info:    Added subscription Free Trial
info:    Setting subscription "Free Trial" as default
+
info:    login command OK

azure login

info: Executing command login

\info: To sign in, use a web browser to open the page https://aka.ms/devicelogin. Enter the code BS5P64ANU to authenticate.

|info: Added subscription Free Trial

info: Setting subscription "Free Trial" as default

info: login command OK

Get account information using azure account show command:

azure account show
info:    Executing command account show
data:    Name                        : Free Trial
data:    ID                          : XXX
data:    State                       : Enabled
data:    Tenant ID                   : YYY
data:    Is Default                  : true
data:    Environment                 : AzureCloud
data:    Has Certificate             : No
data:    Has Access Token            : Yes
data:    User name                   : arun.gupta@gmail.com
data:
info:    account show command OK

azure account show

info: Executing command account show

data: Name : Free Trial

data: ID : XXX

data: State : Enabled

data: Tenant ID : YYY

data: Is Default : true

data: Environment : AzureCloud

data: Has Certificate : No

data: Has Access Token : Yes

data: User name : arun.gupta@gmail.com

data:

info: account show command OK

Note the value shown instead of XXX and YYY. These will be used to configure the Kubernetes cluster.

Start Kubernetes Cluster

Download Kubernetes 1.2.4 and extract it.

Kubernetes cluster on Azure can be started as:

export KUBERNETES_PROVIDER=azure
export AZURE_SUBSCRIPTION_ID=XXX
export AZURE_TENANT_ID=YYY
./cluster/kube-up.sh

export KUBERNETES_PROVIDER=azure

export AZURE_SUBSCRIPTION_ID=XXX

export AZURE_TENANT_ID=YYY

./cluster/kube-up.sh

Make sure to specify the appropriate values for XXX and YYY from the previous command. AZURE_SUBSCRIPTION_ID and AZURE_TENANT_ID are specific to Azure.

These values can also be edited in cluster/azure/config-default.sh.

Start Kubernetes cluster:

./kubernetes/cluster/kube-up.sh 
... Starting cluster using provider: azure
... calling verify-prereqs
... calling kube-up
++> AZURE KUBE-UP STARTED: Tue May 31 16:15:26 PDT 2016
This will be interactive. (export AZURE_AUTH_METHOD=client_secret to avoid the prompt)
hyperkube-amd64:v1.2.4 was found in the gcr.io/google_containers repository
Flag --tenant-id has been deprecated, tenant-id is deprecated. it is now determined automatically from the subscription id
WARN[0000] --resource-group is unset. Derived one from --deployment-name: "kube-20160531-161525" 
WARN[0000] --master-fqdn is unset. Derived one from input: "kube-20160531-161525.westus.cloudapp.azure.com". 
To sign in, use a web browser to open the page https://aka.ms/devicelogin. Enter the code BPRLH2ARJ to authenticate.
INFO[0034] Starting ARM Deployment. This will take some time. deployment="kube-20160531-161525-1464736561" 
INFO[0279] Finished ARM Deployment. deployment="kube-20160531-161525-1464736561" 
INFO[0279] Validating Kubernetes cluster.               
WARN[0279] Failed to validate components: Get https://kube-20160531-161525.westus.cloudapp.azure.com:6443/api/v1/componentstatuses: dial tcp 23.99.60.138:6443: getsockopt: connection refused 
INFO[0294] Validating Kubernetes cluster.               
WARN[0294] Failed to validate components: Get https://kube-20160531-161525.westus.cloudapp.azure.com:6443/api/v1/componentstatuses: dial tcp 23.99.60.138:6443: getsockopt: connection refused 
INFO[0309] Validating Kubernetes cluster.               
WARN[0309] Failed to validate components: Get https://kube-20160531-161525.westus.cloudapp.azure.com:6443/api/v1/componentstatuses: dial tcp 23.99.60.138:6443: getsockopt: connection refused 
INFO[0324] Validating Kubernetes cluster.               
WARN[0347] validate: incorrect healthy count. expected=3 actual=4 
INFO[0347] Deployment Complete!                         
INFO[0347] master: "https://kube-20160531-161525.westus.cloudapp.azure.com:6443" 
INFO[0347] output: "/opt/azkube/_deployments/kube-20160531-161525" 
cluster "kube-20160531-161525" set.
user "kube-20160531-161525_user" set.
context "kube-20160531-161525" set.
switched to context "kube-20160531-161525".
++> AZURE KUBE-UP FINISHED: Tue May 31 16:21:15 PDT 2016 (duration: -349 seconds)
... calling validate-cluster
Detected 4 ready nodes, found 4 nodes out of expected 3. Found more nodes than expected, your cluster may not behave correctly.
Found 4 node(s).
NAME                             STATUS                     AGE
kube-20160531-161525-vm-master   Ready,SchedulingDisabled   21s
kube-20160531-161525-vm-node-0   Ready                      18s
kube-20160531-161525-vm-node-1   Ready                      19s
kube-20160531-161525-vm-node-2   Ready                      19s
Flag --api-version has been deprecated, flag is no longer respected and will be deleted in the next release
Validate output:
NAME                 STATUS    MESSAGE              ERROR
scheduler            Healthy   ok                   
controller-manager   Healthy   ok                   
etcd-1               Healthy   {"health": "true"}   
etcd-0               Healthy   {"health": "true"}   
Cluster validation succeeded
Done, listing cluster services:

Kubernetes master is running at https://kube-20160531-161525.westus.cloudapp.azure.com:6443

./kubernetes/cluster/kube-up.sh

... Starting cluster using provider: azure

... calling verify-prereqs

... calling kube-up

++> AZURE KUBE-UP STARTED: Tue May 31 16:15:26 PDT 2016

This will be interactive. (export AZURE_AUTH_METHOD=client_secret to avoid the prompt)

hyperkube-amd64:v1.2.4 was found in the gcr.io/google_containers repository

Flag --tenant-id has been deprecated, tenant-id is deprecated. it is now determined automatically from the subscription id

WARN[0000] --resource-group is unset. Derived one from --deployment-name: "kube-20160531-161525"

WARN[0000] --master-fqdn is unset. Derived one from input: "kube-20160531-161525.westus.cloudapp.azure.com".

To sign in, use a web browser to open the page https://aka.ms/devicelogin. Enter the code BPRLH2ARJ to authenticate.

INFO[0034] Starting ARM Deployment. This will take some time. deployment="kube-20160531-161525-1464736561"

INFO[0279] Finished ARM Deployment. deployment="kube-20160531-161525-1464736561"

INFO[0279] Validating Kubernetes cluster.

WARN[0279] Failed to validate components: Get https://kube-20160531-161525.westus.cloudapp.azure.com:6443/api/v1/componentstatuses: dial tcp 23.99.60.138:6443: getsockopt: connection refused

INFO[0294] Validating Kubernetes cluster.

WARN[0294] Failed to validate components: Get https://kube-20160531-161525.westus.cloudapp.azure.com:6443/api/v1/componentstatuses: dial tcp 23.99.60.138:6443: getsockopt: connection refused

INFO[0309] Validating Kubernetes cluster.

WARN[0309] Failed to validate components: Get https://kube-20160531-161525.westus.cloudapp.azure.com:6443/api/v1/componentstatuses: dial tcp 23.99.60.138:6443: getsockopt: connection refused

INFO[0324] Validating Kubernetes cluster.

WARN[0347] validate: incorrect healthy count. expected=3 actual=4

INFO[0347] Deployment Complete!

INFO[0347] master: "https://kube-20160531-161525.westus.cloudapp.azure.com:6443"

INFO[0347] output: "/opt/azkube/_deployments/kube-20160531-161525"

cluster "kube-20160531-161525" set.

user "kube-20160531-161525_user" set.

context "kube-20160531-161525" set.

switched to context "kube-20160531-161525".

++> AZURE KUBE-UP FINISHED: Tue May 31 16:21:15 PDT 2016 (duration: -349 seconds)

... calling validate-cluster

Detected 4 ready nodes, found 4 nodes out of expected 3. Found more nodes than expected, your cluster may not behave correctly.

Found 4 node(s).

NAME STATUS AGE

kube-20160531-161525-vm-master Ready,SchedulingDisabled 21s

kube-20160531-161525-vm-node-0 Ready 18s

kube-20160531-161525-vm-node-1 Ready 19s

kube-20160531-161525-vm-node-2 Ready 19s

Flag --api-version has been deprecated, flag is no longer respected and will be deleted in the next release

Validate output:

NAME STATUS MESSAGE ERROR

scheduler Healthy ok

controller-manager Healthy ok

etcd-1 Healthy {"health": "true"}

etcd-0 Healthy {"health": "true"}

Cluster validation succeeded

Done, listing cluster services:

Kubernetes master is running at https://kube-20160531-161525.westus.cloudapp.azure.com:6443

It starts four nodes of Standard_A1 size. Each node gives you 1 core, 1.75 GB RAM, and 40GB HDD.

Run Docker Container in Kubernetes Cluster on Azure

Now that the cluster is up and running, get a list of all the nodes:

./kubernetes/cluster/kubectl.sh get no
NAME                             STATUS                     AGE
kube-20160531-161525-vm-master   Ready,SchedulingDisabled   3m
kube-20160531-161525-vm-node-0   Ready                      3m
kube-20160531-161525-vm-node-1   Ready                      3m
kube-20160531-161525-vm-node-2   Ready                      3m

./kubernetes/cluster/kubectl.sh get no

NAME STATUS AGE

kube-20160531-161525-vm-master Ready,SchedulingDisabled 3m

kube-20160531-161525-vm-node-0 Ready 3m

kube-20160531-161525-vm-node-1 Ready 3m

kube-20160531-161525-vm-node-2 Ready 3m

Four instances are created as shown – one for master node and three for worker nodes.

Azure Portal shows all the created artifacts in the Resource Group:

More details about the created nodes is available:

Create a Couchbase pod:

./kubernetes/cluster/kubectl.sh run couchbase --image=arungupta/couchbase
deployment "couchbase" created

./kubernetes/cluster/kubectl.sh run couchbase --image=arungupta/couchbase

deployment "couchbase" created

Notice, how the image name can be specified on the CLI. Kubernetes pre-1.2 versions created a Replication Controller with this command. This is explained in Kubernetes on Amazon Web Services or Kubernetes on Google Cloud. Kubernetes 1.2 introduced Deployments and so this creates a Deployment instead. This enables simplified application deployment and management including versioning, multiple simultaneous rollouts, aggregating status across all pods, maintaining application availability and rollback.

The pod uses arungupta/couchbase Docker image that provides a pre-configured Couchbase server. Any Docker image can be specified here.

Status of the pod can be watched:

./kubernetes/cluster/kubectl.sh get -w po
NAME                         READY     STATUS              RESTARTS   AGE
couchbase-2830197765-f0s9c   0/1       ContainerCreating   0          5s
NAME                         READY     STATUS    RESTARTS   AGE
couchbase-2830197765-f0s9c   1/1       Running   0          1m

./kubernetes/cluster/kubectl.sh get -w po

NAME READY STATUS RESTARTS AGE

couchbase-2830197765-f0s9c 0/1 ContainerCreating 0 5s

NAME READY STATUS RESTARTS AGE

couchbase-2830197765-f0s9c 1/1 Running 0 1m

Get more details about the pod:

./kubernetes/cluster/kubectl.sh describe po couchbase-2830197765-f0s9c
Name:           couchbase-2830197765-f0s9c
Namespace:      default
Node:           kube-20160531-161525-vm-node-2/10.0.0.6
Start Time:     Tue, 31 May 2016 16:28:02 -0700
Labels:         pod-template-hash=2830197765,run=couchbase
Status:         Running
IP:             10.2.74.2
Controllers:    ReplicaSet/couchbase-2830197765
Containers:
  couchbase:
    Container ID:       docker://eba043085c95645cf650206469be5c7e2d6c7395883a053d197446a14e757440
    Image:              arungupta/couchbase
    Image ID:           docker://sha256:f6b013d9694354148ace6804127dadee01c733151b5ff5e169f7c3b0e4faf321
    Port:               
    QoS Tier:
      cpu:              BestEffort
      memory:           BestEffort
    State:              Running
      Started:          Tue, 31 May 2016 16:29:04 -0700
    Ready:              True
    Restart Count:      0
    Environment Variables:
Conditions:
  Type          Status
  Ready         True 
Volumes:
  default-token-ylszs:
    Type:       Secret (a volume populated by a Secret)
    SecretName: default-token-ylszs
Events:
  FirstSeen     LastSeen        Count   From                                            SubobjectPath                   Type            Reason          Message
  ---------     --------        -----   ----                                            -------------                   --------        ------          -------
  7m            7m              1       {default-scheduler }                                                            Normal          Scheduled       Successfully assigned couchbase-2830197765-f0s9c to kube-20160531-161525-vm-node-2
  7m            7m              1       {kubelet kube-20160531-161525-vm-node-2}        spec.containers{couchbase}      Normal          Pulling         pulling image "arungupta/couchbase"
  6m            6m              1       {kubelet kube-20160531-161525-vm-node-2}        spec.containers{couchbase}      Normal          Pulled          Successfully pulled image "arungupta/couchbase"
  6m            6m              1       {kubelet kube-20160531-161525-vm-node-2}        spec.containers{couchbase}      Normal          Created         Created container with docker id eba043085c95
  6m            6m              1       {kubelet kube-20160531-161525-vm-node-2}        spec.containers{couchbase}      Normal          Started         Started container with docker id eba043085c95

./kubernetes/cluster/kubectl.sh describe po couchbase-2830197765-f0s9c

Name: couchbase-2830197765-f0s9c

Namespace: default

Node: kube-20160531-161525-vm-node-2/10.0.0.6

Start Time: Tue, 31 May 2016 16:28:02 -0700

Labels: pod-template-hash=2830197765,run=couchbase

Status: Running

IP: 10.2.74.2

Controllers: ReplicaSet/couchbase-2830197765

Containers:

couchbase:

Container ID: docker://eba043085c95645cf650206469be5c7e2d6c7395883a053d197446a14e757440

Image: arungupta/couchbase

Image ID: docker://sha256:f6b013d9694354148ace6804127dadee01c733151b5ff5e169f7c3b0e4faf321

Port:

QoS Tier:

cpu: BestEffort

memory: BestEffort

State: Running

Started: Tue, 31 May 2016 16:29:04 -0700

Ready: True

Restart Count: 0

Environment Variables:

Conditions:

Type Status

Ready True

Volumes:

default-token-ylszs:

Type: Secret (a volume populated by a Secret)

SecretName: default-token-ylszs

Events:

FirstSeen LastSeen Count From SubobjectPath Type Reason Message

--------- -------- ----- ---- ------------- -------- ------ -------

7m 7m 1 {default-scheduler } Normal Scheduled Successfully assigned couchbase-2830197765-f0s9c to kube-20160531-161525-vm-node-2

7m 7m 1 {kubelet kube-20160531-161525-vm-node-2} spec.containers{couchbase} Normal Pulling pulling image "arungupta/couchbase"

6m 6m 1 {kubelet kube-20160531-161525-vm-node-2} spec.containers{couchbase} Normal Pulled Successfully pulled image "arungupta/couchbase"

6m 6m 1 {kubelet kube-20160531-161525-vm-node-2} spec.containers{couchbase} Normal Created Created container with docker id eba043085c95

6m 6m 1 {kubelet kube-20160531-161525-vm-node-2} spec.containers{couchbase} Normal Started Started container with docker id eba043085c95

Expose Pod on Kubernetes as Service

Now that our pod is running, how do I access the Couchbase server? You need to expose the Deployment as a Service outside the Kubernetes cluster.

Typically, this will be exposed using the command:

./kubernetes/cluster/kubectl.sh expose deployment couchbase --target-port=8091 --port=8091 --type=LoadBalancer

./kubernetes/cluster/kubectl.sh expose deployment couchbase --target-port=8091 --port=8091 --type=LoadBalancer

But Azure does not support --type=LoadBalancer at this time. This feature is being worked upon and will hopefully be available in the near future. So in the meanwhile, we’ll expose the Service as:

./kubernetes/cluster/kubectl.sh expose deployment couchbase --target-port=8091 --port=8091
service "couchbase" exposed

./kubernetes/cluster/kubectl.sh expose deployment couchbase --target-port=8091 --port=8091

service "couchbase" exposed

Now proxy to this Service using kubectl proxy command:

./kubernetes/cluster/kubectl.sh proxy --address='0.0.0.0' --port=9999 --accept-hosts='.*'
Starting to serve on [::]:9999

./kubernetes/cluster/kubectl.sh proxy --address='0.0.0.0' --port=9999 --accept-hosts='.*'

Starting to serve on [::]:9999

And now this exposed Service is accessible at http://127.0.0.1:9999/api/v1/proxy/namespaces/default/services/couchbase/index.html. This shows the login screen of Couchbase Web Console:

Shutdown Kubernetes Cluster

Finally, shutdown the cluster using cluster/kube-down.sh script.

./kubernetes/cluster/kube-down.sh 
Bringing down cluster using provider: azure
Bringing down cluster

You must do this manually (for now)!
This can be done with:
./kubernetes/cluster/../cluster/../cluster/azure/util.sh: line 246: AZ_RESOURCE_GROUP: unbound variable

./kubernetes/cluster/kube-down.sh

Bringing down cluster using provider: azure

Bringing down cluster

You must do this manually (for now)!

This can be done with:

./kubernetes/cluster/../cluster/../cluster/azure/util.sh: line 246: AZ_RESOURCE_GROUP: unbound variable

This script shuts down the cluster but the Azure resource group need to be explicitly removed. This can be done by selecting the Resource Group from portal.azure.com:

This is filed as #26601.

Enjoy!

Further references …

Couchbase Server Developer Portal
Couchbase on Containers
Questions on StackOverflow, Forums or Slack Channel
Follow us @couchbasedev
Couchbase 4.5 Beta

Source: http://blog.couchbase.com/2016/june/kubernetes-cluster-azure-couchbase-service

Kubernetes Namespaces, Resource Quota, and Limits for QoS in Cluster

March 5, 2016containers, couchbasecouchbase, kubernetesarungupta

By default, all resources in Kubernetes cluster are created in a default namespace. A pod will run with unbounded CPU and memory requests/limits.

A Kubernetes namespace allows to partition created resources into a logically named group. Each namespace provides:

a unique scope for resources to avoid name collisions
policiesto ensure appropriate authority to trusted users
ability to specify constraints for resource consumption

This allows a Kubernetes cluster to share resources by multiple groups and provide different levels of QoS each group.

Resources created in one namespace are hidden from other namespaces. Multiple namespaces can be created, each potentially with different constraints.

Default Kubernetes Namespace

By default, each resource created by user in Kubernetes cluster runs in a default namespace, called default.

./kubernetes/cluster/kubectl.sh get namespace
NAME          LABELS    STATUS    AGE
default       <none>    Active    1m
kube-system   <none>    Active    1m

./kubernetes/cluster/kubectl.sh get namespace

NAME LABELS STATUS AGE

default <none> Active 1m

kube-system <none> Active 1m

Any pod, service or replication controller will be created in this namespace. kube-system namespace is reserved for resources created by the Kubernetes cluster.

More details about the namespace can be seen:

./kubernetes/cluster/kubectl.sh describe namespaces default
Name:   default
Labels: <none>
Status: Active

No resource quota.

Resource Limits
 Type           Resource        Min     Max     Request Limit   Limit/Request
 ----           --------        ---     ---     ------- -----   -------------
 Container      cpu             -       -       100m    -       -

./kubernetes/cluster/kubectl.sh describe namespaces default

Name: default

Labels: <none>

Status: Active

No resource quota.

Resource Limits

Type Resource Min Max Request Limit Limit/Request

---- -------- --- --- ------- ----- -------------

Container cpu - - 100m - -

This description shows resource quota (if present), as well as resource limit ranges.

So let’s create a Couchbase replication controller as:

./kubernetes/cluster/kubectl.sh run couchbase --image=arungupta/couchbase

./kubernetes/cluster/kubectl.sh run couchbase --image=arungupta/couchbase

Check the existing replication controller:

./kubernetes/cluster/kubectl.sh get rc
CONTROLLER   CONTAINER(S)   IMAGE(S)              SELECTOR        REPLICAS   AGE
couchbase    couchbase      arungupta/couchbase   run=couchbase   1          5m

./kubernetes/cluster/kubectl.sh get rc

CONTROLLER CONTAINER(S) IMAGE(S) SELECTOR REPLICAS AGE

couchbase couchbase arungupta/couchbase run=couchbase 1 5m

By default, only resources in user namespace are shown. Resources in all namespaces can be shown using --all-namespaces option:

./kubernetes/cluster/kubectl.sh get rc --all-namespaces
NAMESPACE     CONTROLLER                       CONTAINER(S)           IMAGE(S)                                                SELECTOR                           REPLICAS   AGE
default       couchbase                        couchbase              arungupta/couchbase                                     run=couchbase                      1          5m
kube-system   heapster-v11                     heapster               gcr.io/google_containers/heapster:v0.18.4               k8s-app=heapster,version=v11       1          6m
kube-system   kube-dns-v9                      etcd                   gcr.io/google_containers/etcd:2.0.9                     k8s-app=kube-dns,version=v9        1          6m
                                               kube2sky               gcr.io/google_containers/kube2sky:1.11                                                     
                                               skydns                 gcr.io/google_containers/skydns:2015-10-13-8c72f8c                                         
                                               healthz                gcr.io/google_containers/exechealthz:1.0                                                   
kube-system   kube-ui-v4                       kube-ui                gcr.io/google_containers/kube-ui:v4                     k8s-app=kube-ui,version=v4         1         6m
kube-system   l7-lb-controller-v0.5.2          default-http-backend   gcr.io/google_containers/defaultbackend:1.0             k8s-app=glbc,version=v0.5.2        1         6m
                                               l7-lb-controller       gcr.io/google_containers/glbc:0.5.2                                                        
kube-system   monitoring-influxdb-grafana-v2   influxdb               gcr.io/google_containers/heapster_influxdb:v0.4         k8s-app=influxGrafana,version=v2   1         6m
                                               grafana                beta.gcr.io/google_containers/heapster_grafana:v2.1.1

./kubernetes/cluster/kubectl.sh get rc --all-namespaces

NAMESPACE CONTROLLER CONTAINER(S) IMAGE(S) SELECTOR REPLICAS AGE

default couchbase couchbase arungupta/couchbase run=couchbase 1 5m

kube-system heapster-v11 heapster gcr.io/google_containers/heapster:v0.18.4 k8s-app=heapster,version=v11 1 6m

kube-system kube-dns-v9 etcd gcr.io/google_containers/etcd:2.0.9 k8s-app=kube-dns,version=v9 1 6m

kube2sky gcr.io/google_containers/kube2sky:1.11

skydns gcr.io/google_containers/skydns:2015-10-13-8c72f8c

healthz gcr.io/google_containers/exechealthz:1.0

kube-system kube-ui-v4 kube-ui gcr.io/google_containers/kube-ui:v4 k8s-app=kube-ui,version=v4 1 6m

kube-system l7-lb-controller-v0.5.2 default-http-backend gcr.io/google_containers/defaultbackend:1.0 k8s-app=glbc,version=v0.5.2 1 6m

l7-lb-controller gcr.io/google_containers/glbc:0.5.2

kube-system monitoring-influxdb-grafana-v2 influxdb gcr.io/google_containers/heapster_influxdb:v0.4 k8s-app=influxGrafana,version=v2 1 6m

grafana beta.gcr.io/google_containers/heapster_grafana:v2.1.1

As you can see, the arungupta/couchbase image runs in the default namespace. All other resources run in the kube-system namespace.

Lets check the context of this replication controller:

./kubernetes/cluster/kubectl.sh config view couchbase
apiVersion: v1
clusters:
- cluster:
    certificate-authority-data: REDACTED
    server: https://104.197.10.200
  name: couchbase-on-kubernetes_kubernetes
contexts:
- context:
    cluster: couchbase-on-kubernetes_kubernetes
    user: couchbase-on-kubernetes_kubernetes
  name: couchbase-on-kubernetes_kubernetes
current-context: couchbase-on-kubernetes_kubernetes
kind: Config
preferences: {}
users:
- name: couchbase-on-kubernetes_kubernetes
  user:
    client-certificate-data: REDACTED
    client-key-data: REDACTED
    token: 1RUrsvA5RDwwRNf0eOvz86elmniOK0oj
- name: couchbase-on-kubernetes_kubernetes-basic-auth
  user:
    password: cZ9fZSuzIqq5kdnj
    username: admin

./kubernetes/cluster/kubectl.sh config view couchbase

apiVersion: v1

clusters:

- cluster:

certificate-authority-data: REDACTED

server: https://104.197.10.200

contexts:

- context:

cluster: couchbase-on-kubernetes_kubernetes

user: couchbase-on-kubernetes_kubernetes

current-context: couchbase-on-kubernetes_kubernetes

kind: Config

preferences: {}

users:

- name: couchbase-on-kubernetes_kubernetes

user:

client-certificate-data: REDACTED

client-key-data: REDACTED

token: 1RUrsvA5RDwwRNf0eOvz86elmniOK0oj

- name: couchbase-on-kubernetes_kubernetes-basic-auth

user:

password: cZ9fZSuzIqq5kdnj

username: admin

Look for contexts.context.name attribute to see the existing context. This will be manipulated later.

Create a Resource in New Kubernetes Namespace

Lets create a new namespace first. This can be done using the following configuration file:

apiVersion: v1
kind: Namespace
metadata:
  name: development
  labels:
    name: development

apiVersion: v1

kind: Namespace

metadata:

labels:

Namespace is created as:

./kubernetes/cluster/kubectl.sh create -f myns.yaml 
namespace "development" created

./kubernetes/cluster/kubectl.sh create -f myns.yaml

namespace "development" created

Then querying for all the namespaces gives:

./kubernetes/cluster/kubectl.sh get namespace
NAME          LABELS             STATUS    AGE
default       <none>             Active    9m
development   name=development   Active    13s
kube-system   <none>             Active    8m

./kubernetes/cluster/kubectl.sh get namespace

NAME LABELS STATUS AGE

default <none> Active 9m

development name=development Active 13s

kube-system <none> Active 8m

A new replication controller can be created in this new namespace by using --namespace option:

./kubernetes/cluster/kubectl.sh --namespace=development run couchbase --image=arungupta/couchbase
replicationcontroller "couchbase" created

./kubernetes/cluster/kubectl.sh --namespace=development run couchbase --image=arungupta/couchbase

replicationcontroller "couchbase" created

List of resources in all namespaces looks like:

./kubernetes/cluster/kubectl.sh get rc --all-namespaces
NAMESPACE     CONTROLLER                       CONTAINER(S)           IMAGE(S)                                                SELECTOR                           REPLICAS   AGE
default       couchbase                        couchbase              arungupta/couchbase                                     run=couchbase                      1          4m
development   couchbase                        couchbase              arungupta/couchbase                                     run=couchbase                      1          2m
kube-system   heapster-v11                     heapster               gcr.io/google_containers/heapster:v0.18.4               k8s-app=heapster,version=v11       1          31m
. . .

./kubernetes/cluster/kubectl.sh get rc --all-namespaces

NAMESPACE CONTROLLER CONTAINER(S) IMAGE(S) SELECTOR REPLICAS AGE

default couchbase couchbase arungupta/couchbase run=couchbase 1 4m

development couchbase couchbase arungupta/couchbase run=couchbase 1 2m

kube-system heapster-v11 heapster gcr.io/google_containers/heapster:v0.18.4 k8s-app=heapster,version=v11 1 31m

. . .

As seen, there are two replication controllers with arungupta/couchbase image – one in default namespace and another in development namespace.

Set Kubernetes Namespace For an Existing Resource

If a resource is already created then it can be assigned a namespace.

On a previously created resource, new context can be set in the namespace:

./kubernetes/cluster/kubectl.sh config set-context dev --namespace=development --cluster=couchbase-on-kubernetes_kubernetes --user=couchbase-on-kubernetes_kubernetes
context "dev" set.

./kubernetes/cluster/kubectl.sh config set-context dev --namespace=development --cluster=couchbase-on-kubernetes_kubernetes --user=couchbase-on-kubernetes_kubernetes

context "dev" set.

Viewing the context now shows:

./kubernetes/cluster/kubectl.sh config view couchbase
apiVersion: v1
clusters:
- cluster:
    certificate-authority-data: REDACTED
    server: https://104.197.10.200
  name: couchbase-on-kubernetes_kubernetes
contexts:
- context:
    cluster: couchbase-on-kubernetes_kubernetes
    user: couchbase-on-kubernetes_kubernetes
  name: couchbase-on-kubernetes_kubernetes
- context:
    cluster: couchbase-on-kubernetes_kubernetes
    namespace: development
    user: couchbase-on-kubernetes_kubernetes
  name: dev
current-context: couchbase-on-kubernetes_kubernetes
kind: Config
preferences: {}
users:
- name: couchbase-on-kubernetes_kubernetes
  user:
    client-certificate-data: REDACTED
    client-key-data: REDACTED
    token: 1RUrsvA5RDwwRNf0eOvz86elmniOK0oj
- name: couchbase-on-kubernetes_kubernetes-basic-auth
  user:
    password: cZ9fZSuzIqq5kdnj
    username: admin

./kubernetes/cluster/kubectl.sh config view couchbase

apiVersion: v1

clusters:

- cluster:

certificate-authority-data: REDACTED

server: https://104.197.10.200

contexts:

- context:

cluster: couchbase-on-kubernetes_kubernetes

user: couchbase-on-kubernetes_kubernetes

- context:

cluster: couchbase-on-kubernetes_kubernetes

namespace: development

user: couchbase-on-kubernetes_kubernetes

current-context: couchbase-on-kubernetes_kubernetes

kind: Config

preferences: {}

users:

- name: couchbase-on-kubernetes_kubernetes

user:

client-certificate-data: REDACTED

client-key-data: REDACTED

token: 1RUrsvA5RDwwRNf0eOvz86elmniOK0oj

- name: couchbase-on-kubernetes_kubernetes-basic-auth

user:

password: cZ9fZSuzIqq5kdnj

username: admin

The second attribute in contexts.context array shows that a new context has been created. It also shows that the current context is still couchbase-on-kubernetes_kubernetes. Since no namespace is specified in that context, it belongs to the default namespace.

Change the context:

./kubernetes/cluster/kubectl.sh config use-context dev
switched to context "dev".

./kubernetes/cluster/kubectl.sh config use-context dev

switched to context "dev".

See the list of replication controllers:

./kubernetes/cluster/kubectl.sh get rc
CONTROLLER   CONTAINER(S)   IMAGE(S)   SELECTOR   REPLICAS   AGE

./kubernetes/cluster/kubectl.sh get rc

CONTROLLER CONTAINER(S) IMAGE(S) SELECTOR REPLICAS AGE

Obviously, no replication controllers are running in this context. Lets create a new replication controller in this new namespace:

./kubernetes/cluster/kubectl.sh run couchbase --image=arungupta/couchbase
replicationcontroller "couchbase" created

./kubernetes/cluster/kubectl.sh run couchbase --image=arungupta/couchbase

replicationcontroller "couchbase" created

And see the list of replication controllers in all namespaces:

./kubernetes/cluster/kubectl.sh get rc --all-namespaces
NAMESPACE     CONTROLLER                       CONTAINER(S)           IMAGE(S)                                                SELECTOR                           REPLICAS   AGE
default       couchbase                        couchbase              arungupta/couchbase                                     run=couchbase                      1          16m
development   couchbase                        couchbase              arungupta/couchbase                                     run=couchbase                      1          4s
kube-system   heapster-v11                     heapster               gcr.io/google_containers/heapster:v0.18.4               k8s-app=heapster,version=v11       1          17m
. . .

./kubernetes/cluster/kubectl.sh get rc --all-namespaces

NAMESPACE CONTROLLER CONTAINER(S) IMAGE(S) SELECTOR REPLICAS AGE

default couchbase couchbase arungupta/couchbase run=couchbase 1 16m

development couchbase couchbase arungupta/couchbase run=couchbase 1 4s

kube-system heapster-v11 heapster gcr.io/google_containers/heapster:v0.18.4 k8s-app=heapster,version=v11 1 17m

. . .

Now you can see two arungupta/couchbase replication controllers running in two difference namespaces.

Delete a Kubernetes Resource in Namespace

A resource can be deleted by fully-qualifying the resource name:

./kubernetes/cluster/kubectl.sh --namespace=default delete rc couchbase
replicationcontroller "couchbase" deleted

./kubernetes/cluster/kubectl.sh --namespace=default delete rc couchbase

replicationcontroller "couchbase" deleted

Similarly the other replication controller can be deleted as:

./kubernetes/cluster/kubectl.sh --namespace=development delete rc couchbase
replicationcontroller "couchbase" deleted

./kubernetes/cluster/kubectl.sh --namespace=development delete rc couchbase

replicationcontroller "couchbase" deleted

Finally, see the list of all replication controllers in all namespaces:

./kubernetes/cluster/kubectl.sh get rc --all-namespaces
NAMESPACE     CONTROLLER                       CONTAINER(S)           IMAGE(S)                                                SELECTOR                           REPLICAS   AGE
kube-system   heapster-v11                     heapster               gcr.io/google_containers/heapster:v0.18.4               k8s-app=heapster,version=v11       1          3h
kube-system   kube-dns-v9                      etcd                   gcr.io/google_containers/etcd:2.0.9                     k8s-app=kube-dns,version=v9        1          3h
. . .

./kubernetes/cluster/kubectl.sh get rc --all-namespaces

NAMESPACE CONTROLLER CONTAINER(S) IMAGE(S) SELECTOR REPLICAS AGE

kube-system heapster-v11 heapster gcr.io/google_containers/heapster:v0.18.4 k8s-app=heapster,version=v11 1 3h

kube-system kube-dns-v9 etcd gcr.io/google_containers/etcd:2.0.9 k8s-app=kube-dns,version=v9 1 3h

. . .

This confirms that all user created replication controllers are deleted.

Resource Quota and Limit using Kubernetes Namespace

Each namespace can be assigned resource quota.

By default, a pod will run with unbounded CPU and memory requests/limits. Specifying quota allows to restrict how much of cluster resources can be consumed across all pods in a namespace.

Resource quota can be specified using a configuration file:

apiVersion: v1
kind: ResourceQuota
metadata:
  name: quota
spec:
  hard:
    cpu: "20"
    memory: 1Gi
    pods: "10"
    replicationcontrollers: "20"
    resourcequotas: "1"
    services: "5"

apiVersion: v1

kind: ResourceQuota

metadata:

spec:

hard:

cpu: "20"

memory: 1Gi

pods: "10"

replicationcontrollers: "20"

resourcequotas: "1"

services: "5"

The following resources are supported by the quota system:

Resource	Description
`cpu`	Total requested cpu usage
`memory`	Total requested memory usage
`pods`	Total number of active pods where phase is pending or active.
`services`	Total number of services
`replicationcontrollers`	Total number of replication controllers
`resourcequotas`	Total number of resource quotas
`secrets`	Total number of secrets
`persistentvolumeclaims`	Total number of persistent volume claims

This resource quota can be created in a namespace:

./kubernetes/cluster/kubectl.sh --namespace=development create -f quota.yaml
resourcequota "quota" created

./kubernetes/cluster/kubectl.sh --namespace=development create -f quota.yaml

resourcequota "quota" created

The created quota can be seen as:

./kubernetes/cluster/kubectl.sh --namespace=development describe quota
Name:                   quota
Namespace:              development
Resource                Used    Hard
--------                ----    ----
cpu                     0       20
memory                  0       1Gi
pods                    0       10
replicationcontrollers  0       20
resourcequotas          1       1
services                0       5

./kubernetes/cluster/kubectl.sh --namespace=development describe quota

Name: quota

Namespace: development

Resource Used Hard

-------- ---- ----

cpu 0 20

memory 0 1Gi

pods 0 10

replicationcontrollers 0 20

resourcequotas 1 1

services 0 5

Now, if you try to create the replication controller that works:

./kubernetes/cluster/kubectl.sh --namespace=development run couchbase --image=arungupta/couchbase
replicationcontroller "couchbase" created

./kubernetes/cluster/kubectl.sh --namespace=development run couchbase --image=arungupta/couchbase

replicationcontroller "couchbase" created

But describing the quota again shows:

./kubernetes/cluster/kubectl.sh --namespace=development describe quota
Name:                   quota
Namespace:              development
Resource                Used    Hard
--------                ----    ----
cpu                     0       20
memory                  0       1Gi
pods                    0       10
replicationcontrollers  1       20
resourcequotas          1       1
services                0       5

./kubernetes/cluster/kubectl.sh --namespace=development describe quota

Name: quota

Namespace: development

Resource Used Hard

-------- ---- ----

cpu 0 20

memory 0 1Gi

pods 0 10

replicationcontrollers 1 20

resourcequotas 1 1

services 0 5

We expected a new pod to be created as part of this replication controller but it’s not there. So lets describe our replication controller:

./kubernetes/cluster/kubectl.sh --namespace=development describe rc
Name:           couchbase
Namespace:      development
Image(s):       arungupta/couchbase
Selector:       run=couchbase
Labels:         run=couchbase
Replicas:       0 current / 1 desired
Pods Status:    0 Running / 0 Waiting / 0 Succeeded / 0 Failed
No volumes.
Events:
  FirstSeen     LastSeen        Count   From                            SubobjectPath   Reason          Message
  ─────────     ────────        ─────   ────                            ─────────────   ──────          ───────
  1m            24s             4       {replication-controller }                       FailedCreate    Error creating: Pod "couchbase-" is forbidden: must make a non-zero request for memory since it is tracked by quota.

./kubernetes/cluster/kubectl.sh --namespace=development describe rc

Name: couchbase

Namespace: development

Image(s): arungupta/couchbase

Selector: run=couchbase

Labels: run=couchbase

Replicas: 0 current / 1 desired

Pods Status: 0 Running / 0 Waiting / 0 Succeeded / 0 Failed

No volumes.

Events:

FirstSeen LastSeen Count From SubobjectPath Reason Message

───────── ──────── ───── ──── ───────────── ────── ───────

1m 24s 4 {replication-controller } FailedCreate Error creating: Pod "couchbase-" is forbidden: must make a non-zero request for memory since it is tracked by quota.

By default, pod consumes all the cpu and memory available. With resource quotas applied, an explicit value must be specified. Alternatively a default value for the pod can be specified using the following configuration file:

apiVersion: v1
kind: LimitRange
metadata:
  name: limits
spec:
  limits:
  - default:
      cpu: 200m
      memory: 512Mi
    defaultRequest:
      cpu: 100m
      memory: 256Mi
    type: Container

apiVersion: v1

kind: LimitRange

metadata:

spec:

limits:

- default:

cpu: 200m

memory: 512Mi

defaultRequest:

cpu: 100m

memory: 256Mi

type: Container

This restricts the CPU and memory that can be consumed by a pod. Lets apply these limits as:

./kubernetes/cluster/kubectl.sh --namespace=development create -f limits.yaml 
limitrange "limits" created

./kubernetes/cluster/kubectl.sh --namespace=development create -f limits.yaml

limitrange "limits" created

Now when you describe the replication controller again, it shows:

./kubernetes/cluster/kubectl.sh --namespace=development describe rc
Name:           couchbase
Namespace:      development
Image(s):       arungupta/couchbase
Selector:       run=couchbase
Labels:         run=couchbase
Replicas:       1 current / 1 desired
Pods Status:    1 Running / 0 Waiting / 0 Succeeded / 0 Failed
No volumes.
Events:
  FirstSeen     LastSeen        Count   From                            SubobjectPath   Reason                  Message
  ─────────     ────────        ─────   ────                            ─────────────   ──────                  ───────
  8m            2m              14      {replication-controller }                       FailedCreate            Error creating: Pod "couchbase-" is forbidden: must make a non-zero request for memory since it is tracked by quota.
  2m            2m              1       {replication-controller }                       SuccessfulCreate        Created pod: couchbase-gzk0l

./kubernetes/cluster/kubectl.sh --namespace=development describe rc

Name: couchbase

Namespace: development

Image(s): arungupta/couchbase

Selector: run=couchbase

Labels: run=couchbase

Replicas: 1 current / 1 desired

Pods Status: 1 Running / 0 Waiting / 0 Succeeded / 0 Failed

No volumes.

Events:

FirstSeen LastSeen Count From SubobjectPath Reason Message

───────── ──────── ───── ──── ───────────── ────── ───────

8m 2m 14 {replication-controller } FailedCreate Error creating: Pod "couchbase-" is forbidden: must make a non-zero request for memory since it is tracked by quota.

2m 2m 1 {replication-controller } SuccessfulCreate Created pod: couchbase-gzk0l

This shows successful creation of the pod.

And now when you describe the quota, it shows correct values as well:

./kubernetes/cluster/kubectl.sh --namespace=development describe quota
Name:                   quota
Namespace:              development
Resource                Used            Hard
--------                ----            ----
cpu                     100m            20
memory                  268435456       1Gi
pods                    1               10
replicationcontrollers  1               20
resourcequotas          1               1
services                0               5

./kubernetes/cluster/kubectl.sh --namespace=development describe quota

Name: quota

Namespace: development

Resource Used Hard

-------- ---- ----

cpu 100m 20

memory 268435456 1Gi

pods 1 10

replicationcontrollers 1 20

resourcequotas 1 1

services 0 5

Resource Quota provide more details about how to set/update these values.

Creating another quota gives the following error:

./kubernetes/cluster/kubectl.sh --namespace=development create -f quota.yaml
Error from server: error when creating "quota.yaml": ResourceQuota "quota" is forbidden: limited to 1 resourcequotas

./kubernetes/cluster/kubectl.sh --namespace=development create -f quota.yaml

Error from server: error when creating "quota.yaml": ResourceQuota "quota" is forbidden: limited to 1 resourcequotas

Specifying Limits During Pod Creation

Limits can be specified during pod creation as well:

If memory limit for each pod is restricted to 1g, then a valid pod definition would be:

apiVersion: v1
kind: Pod
metadata:
  name: couchbase-pod
spec:
  containers:
  - name: couchbase
    image: couchbase
    ports:
    - containerPort: 8091
    resources:
      limits:
        cpu: "1"
        memory: 512Mi

apiVersion: v1

kind: Pod

metadata:

spec:

containers:

- name: couchbase

image: couchbase

ports:

- containerPort: 8091

resources:

limits:

cpu: "1"

memory: 512Mi

This is because the pod request 0.5G of memory only. And an invalid pod definition would be:

apiVersion: v1
kind: Pod
metadata:
  name: couchbase-pod
spec:
  containers:
  - name: couchbase
    image: couchbase
    ports:
    - containerPort: 8091
    resources:
      limits:
        cpu: "1"
        memory: 2G

apiVersion: v1

kind: Pod

metadata:

spec:

containers:

- name: couchbase

image: couchbase

ports:

- containerPort: 8091

resources:

limits:

cpu: "1"

memory: 2G

This is because the pod requests 2G of memory. Creating such a pod gives the following error:

./kubernetes/cluster/kubectl.sh --namespace=development create -f couchbase-pod.yaml 
Error from server: error when creating "couchbase-pod.yaml": Pod "couchbase-pod" is forbidden: unable to admit pod without exceeding quota for resource memory:  limited to 1Gi but require 2805306368 to succeed

./kubernetes/cluster/kubectl.sh --namespace=development create -f couchbase-pod.yaml

Error from server: error when creating "couchbase-pod.yaml": Pod "couchbase-pod" is forbidden: unable to admit pod without exceeding quota for resource memory: limited to 1Gi but require 2805306368 to succeed

Hope you can apply namespaces, resource quotas, and limits for sharing your clusters across different environments.

Source: http://blog.couchbase.com/2016/march/kubernetes-namespaces-resource-quota-limits-qos-cluster

Kubernetes Cluster on Google Cloud and Expose Couchbase Service

March 3, 2016containers, couchbasecouchbase, docker, google, kubernetesarungupta

The first part (Couchbase on Kubernetes) explained how to start the Kubernetes cluster using Vagrant. The second part (Kubernetes on Amazon) explained how run that setup on Amazon Web Services.

This third part will show:

How to setup and start the Kubernetes cluster on Google Cloud
Run Docker container in the Kubernetes cluster
Expose Pod on Kubernetes as Service
Shutdown the cluster

Here is a quick overview:

Let’s get into details!

Getting Started with Google Compute Engine provide detailed instructions on how to setup Kubernetes on Google Cloud.

Download and Configure Google Cloud SDK

There is a bit of setup required if you’ve never accessed Google Cloud on your machine. This was a bit overwhelming and wish can be simplified.

Create a billable account on Google Cloud
Install Google Cloud SDK
Configure credentials: gcloud auth login
Create a new Google Cloud project and name it couchbase-on-kubernetes
Set the project: gcloud config set project couchbase-on-kubernetes
Set default zone: gcloud config set compute/zone us-central1-a
Create an instance: gcloud compute instances create example-instance --machine-type n1-standard-1 --image debian-8
SSH into the instance: gcloud compute ssh example-instance
Delete the instance: gcloud compute instances delete example-instance

Setup Kubernetes Cluster on Google Cloud

Kubernetes cluster can be created on Google Cloud as:

set KUBERNETES_PROVIDER=gce
./cluster/kube-up.sh

set KUBERNETES_PROVIDER=gce

./cluster/kube-up.sh

Make sure KUBERNETES_PROVIDER is either set to gce or not set at all.

By default, this provisions a 4 node Kubernetes cluster with one master. This means 5 Virtual Machines are created.

If you downloaded Kubernetes from github.com/kubernetes/kubernetes/releases, then all the values can be changed in cluster/aws/config-default.sh.

Starting Kubernetes on Google Cloud shows the following log. Google Cloud SDK was behaving little weird but taking the defaults seem to work:

./kubernetes/cluster/kube-up.sh 
... Starting cluster using provider: gce
... calling verify-prereqs
You have specified individual components to update.  If you are trying
 to install new components, use:
  $ gcloud components install alpha

Do you want to run install instead (y/N)?  



Your current Cloud SDK version is: 99.0.0
Installing components from version: 99.0.0

┌──────────────────────────────────────────────┐
│     These components will be installed.      │
├───────────────────────┬────────────┬─────────┤
│          Name         │  Version   │   Size  │
├───────────────────────┼────────────┼─────────┤
│ gcloud Alpha Commands │ 2016.01.12 │ < 1 MiB │
└───────────────────────┴────────────┴─────────┘

For the latest full release notes, please visit:
  https://cloud.google.com/sdk/release_notes

Do you want to continue (Y/n)?  

╔════════════════════════════════════════════════════════════╗
╠═ Creating update staging area                             ═╣
╠════════════════════════════════════════════════════════════╣
╠═ Installing: gcloud Alpha Commands                        ═╣
╠════════════════════════════════════════════════════════════╣
╠═ Creating backup and activating new installation          ═╣
╚════════════════════════════════════════════════════════════╝

Performing post processing steps...done.

Update done!

You have specified individual components to update.  If you are trying
 to install new components, use:
  $ gcloud components install beta

Do you want to run install instead (y/N)?  



Your current Cloud SDK version is: 99.0.0
Installing components from version: 99.0.0

┌─────────────────────────────────────────────┐
│     These components will be installed.     │
├──────────────────────┬────────────┬─────────┤
│         Name         │  Version   │   Size  │
├──────────────────────┼────────────┼─────────┤
│ gcloud Beta Commands │ 2016.01.12 │ < 1 MiB │
└──────────────────────┴────────────┴─────────┘

For the latest full release notes, please visit:
  https://cloud.google.com/sdk/release_notes

Do you want to continue (Y/n)?  

╔════════════════════════════════════════════════════════════╗
╠═ Creating update staging area                             ═╣
╠════════════════════════════════════════════════════════════╣
╠═ Installing: gcloud Beta Commands                         ═╣
╠════════════════════════════════════════════════════════════╣
╠═ Creating backup and activating new installation          ═╣
╚════════════════════════════════════════════════════════════╝

Performing post processing steps...done.

Update done!


All components are up to date.
... calling kube-up
Your active configuration is: [default]

Project: couchbase-on-kubernetes
Zone: us-central1-b
Creating gs://kubernetes-staging-9479406781
Creating gs://kubernetes-staging-9479406781/...
+++ Staging server tars to Google Storage: gs://kubernetes-staging-9479406781/devel
+++ kubernetes-server-linux-amd64.tar.gz uploaded (sha1 = 1ff42f7c31837851d919a66fc07f34b9dbdacf28)
+++ kubernetes-salt.tar.gz uploaded (sha1 = f307380ad6af7dabcf881b132146fa775c18dca8)
Looking for already existing resources
Starting master and configuring firewalls
Created [https://www.googleapis.com/compute/v1/projects/couchbase-on-kubernetes/zones/us-central1-b/disks/kubernetes-master-pd].
NAME                 ZONE          SIZE_GB TYPE   STATUS
kubernetes-master-pd us-central1-b 20      pd-ssd READY
Created [https://www.googleapis.com/compute/v1/projects/couchbase-on-kubernetes/regions/us-central1/addresses/kubernetes-master-ip].
Created [https://www.googleapis.com/compute/v1/projects/couchbase-on-kubernetes/global/firewalls/default-default-ssh].
Created [https://www.googleapis.com/compute/v1/projects/couchbase-on-kubernetes/global/firewalls/kubernetes-master-https].
NAME                NETWORK SRC_RANGES RULES  SRC_TAGS TARGET_TAGS
default-default-ssh default 0.0.0.0/0  tcp:22
NAME                    NETWORK SRC_RANGES RULES   SRC_TAGS TARGET_TAGS
kubernetes-master-https default 0.0.0.0/0  tcp:443          kubernetes-master
+++ Logging using Fluentd to gcp
./kubernetes/cluster/../cluster/../cluster/gce/util.sh: line 434: @: unbound variable
./kubernetes/cluster/../cluster/../cluster/gce/util.sh: line 434: @: unbound variable
./kubernetes/cluster/../cluster/../cluster/gce/util.sh: line 434: @: unbound variable
./kubernetes/cluster/../cluster/../cluster/gce/util.sh: line 434: @: unbound variable
Created [https://www.googleapis.com/compute/v1/projects/couchbase-on-kubernetes/global/firewalls/default-default-internal].
NAME                     NETWORK SRC_RANGES RULES                        SRC_TAGS TARGET_TAGS
default-default-internal default 10.0.0.0/8 tcp:1-65535,udp:1-65535,icmp
Created [https://www.googleapis.com/compute/v1/projects/couchbase-on-kubernetes/global/firewalls/kubernetes-minion-all].
NAME                  NETWORK SRC_RANGES    RULES                    SRC_TAGS TARGET_TAGS
kubernetes-minion-all default 10.244.0.0/16 tcp,udp,icmp,esp,ah,sctp          kubernetes-minion
Created [https://www.googleapis.com/compute/v1/projects/couchbase-on-kubernetes/zones/us-central1-b/instances/kubernetes-master].
NAME              ZONE          MACHINE_TYPE  PREEMPTIBLE INTERNAL_IP EXTERNAL_IP     STATUS
kubernetes-master us-central1-b n1-standard-1             10.128.0.2  104.197.213.249 RUNNING
Creating minions.
./kubernetes/cluster/../cluster/../cluster/gce/util.sh: line 434: @: unbound variable
./kubernetes/cluster/../cluster/../cluster/gce/util.sh: line 434: @: unbound variable
Attempt 1 to create kubernetes-minion-template
WARNING: You have selected a disk size of under [200GB]. This may result in poor I/O performance. For more information, see: https://developers.google.com/compute/docs/disks/persistent-disks#pdperformance.
Created [https://www.googleapis.com/compute/v1/projects/couchbase-on-kubernetes/global/instanceTemplates/kubernetes-minion-template].
NAME                       MACHINE_TYPE  PREEMPTIBLE CREATION_TIMESTAMP
kubernetes-minion-template n1-standard-1             2016-03-03T14:01:14.322-08:00
Created [https://www.googleapis.com/compute/v1/projects/couchbase-on-kubernetes/zones/us-central1-b/instanceGroupManagers/kubernetes-minion-group].
NAME                    ZONE          BASE_INSTANCE_NAME SIZE TARGET_SIZE INSTANCE_TEMPLATE          AUTOSCALED
kubernetes-minion-group us-central1-b kubernetes-minion       4           kubernetes-minion-template
Waiting for group to become stable, current operations: creating: 4
Waiting for group to become stable, current operations: creating: 4
Waiting for group to become stable, current operations: creating: 4
Waiting for group to become stable, current operations: creating: 4
Waiting for group to become stable, current operations: creating: 4
Waiting for group to become stable, current operations: creating: 4
Waiting for group to become stable, current operations: creating: 3
Group is stable
MINION_NAMES=kubernetes-minion-1hmm kubernetes-minion-3x1d kubernetes-minion-h1ov kubernetes-minion-nshn
Using master: kubernetes-master (external IP: 104.197.213.249)
Waiting for cluster initialization.

  This will continually check to see if the API for kubernetes is reachable.
  This might loop forever if there was some uncaught error during start
  up.

Kubernetes cluster created.
cluster "couchbase-on-kubernetes_kubernetes" set.
user "couchbase-on-kubernetes_kubernetes" set.
context "couchbase-on-kubernetes_kubernetes" set.
switched to context "couchbase-on-kubernetes_kubernetes".
user "couchbase-on-kubernetes_kubernetes-basic-auth" set.
Wrote config for couchbase-on-kubernetes_kubernetes to /Users/arungupta/.kube/config

Kubernetes cluster is running.  The master is running at:

  https://104.197.213.249

The user name and password to use is located in /Users/arungupta/.kube/config.

... calling validate-cluster
Waiting for 4 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 4 ready nodes. 0 ready nodes, 2 registered. Retrying.
Waiting for 4 ready nodes. 0 ready nodes, 3 registered. Retrying.
Waiting for 4 ready nodes. 0 ready nodes, 4 registered. Retrying.
Waiting for 4 ready nodes. 3 ready nodes, 4 registered. Retrying.
Waiting for 4 ready nodes. 3 ready nodes, 4 registered. Retrying.
Found 4 node(s).
NAME                     LABELS                                          STATUS    AGE
kubernetes-minion-1hmm   kubernetes.io/hostname=kubernetes-minion-1hmm   Ready     1m
kubernetes-minion-3x1d   kubernetes.io/hostname=kubernetes-minion-3x1d   Ready     52s
kubernetes-minion-h1ov   kubernetes.io/hostname=kubernetes-minion-h1ov   Ready     1m
kubernetes-minion-nshn   kubernetes.io/hostname=kubernetes-minion-nshn   Ready     1m
Validate output:
NAME                 STATUS    MESSAGE              ERROR
controller-manager   Healthy   ok                   nil
scheduler            Healthy   ok                   nil
etcd-0               Healthy   {"health": "true"}   nil
etcd-1               Healthy   {"health": "true"}   nil
Cluster validation succeeded
Done, listing cluster services:

Kubernetes master is running at https://104.197.213.249
GLBCDefaultBackend is running at https://104.197.213.249/api/v1/proxy/namespaces/kube-system/services/default-http-backend
Heapster is running at https://104.197.213.249/api/v1/proxy/namespaces/kube-system/services/heapster
KubeDNS is running at https://104.197.213.249/api/v1/proxy/namespaces/kube-system/services/kube-dns
KubeUI is running at https://104.197.213.249/api/v1/proxy/namespaces/kube-system/services/kube-ui
Grafana is running at https://104.197.213.249/api/v1/proxy/namespaces/kube-system/services/monitoring-grafana
InfluxDB is running at https://104.197.213.249/api/v1/proxy/namespaces/kube-system/services/monitoring-influxdb

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

146

147

148

149

150

151

152

153

154

155

156

157

158

159

160

161

162

163

164

165

166

167

168

169

170

171

172

173

174

175

176

177

178

179

180

181

182

183

184

185

./kubernetes/cluster/kube-up.sh

... Starting cluster using provider: gce

... calling verify-prereqs

You have specified individual components to update. If you are trying

to install new components, use:

$ gcloud components install alpha

Do you want to run install instead (y/N)?

Your current Cloud SDK version is: 99.0.0

Installing components from version: 99.0.0

┌──────────────────────────────────────────────┐

│ These components will be installed. │

├───────────────────────┬────────────┬─────────┤

│ Name │ Version │ Size │

├───────────────────────┼────────────┼─────────┤

│ gcloud Alpha Commands │ 2016.01.12 │ < 1 MiB │

└───────────────────────┴────────────┴─────────┘

For the latest full release notes, please visit:

https://cloud.google.com/sdk/release_notes

Do you want to continue (Y/n)?

╔════════════════════════════════════════════════════════════╗

╠═ Creating update staging area ═╣

╠════════════════════════════════════════════════════════════╣

╠═ Installing: gcloud Alpha Commands ═╣

╠════════════════════════════════════════════════════════════╣

╠═ Creating backup and activating new installation ═╣

╚════════════════════════════════════════════════════════════╝

Performing post processing steps...done.

Update done!

You have specified individual components to update. If you are trying

to install new components, use:

$ gcloud components install beta

Do you want to run install instead (y/N)?

Your current Cloud SDK version is: 99.0.0

Installing components from version: 99.0.0

┌─────────────────────────────────────────────┐

│ These components will be installed. │

├──────────────────────┬────────────┬─────────┤

│ Name │ Version │ Size │

├──────────────────────┼────────────┼─────────┤

│ gcloud Beta Commands │ 2016.01.12 │ < 1 MiB │

└──────────────────────┴────────────┴─────────┘

For the latest full release notes, please visit:

https://cloud.google.com/sdk/release_notes

Do you want to continue (Y/n)?

╔════════════════════════════════════════════════════════════╗

╠═ Creating update staging area ═╣

╠════════════════════════════════════════════════════════════╣

╠═ Installing: gcloud Beta Commands ═╣

╠════════════════════════════════════════════════════════════╣

╠═ Creating backup and activating new installation ═╣

╚════════════════════════════════════════════════════════════╝

Performing post processing steps...done.

Update done!

All components are up to date.

... calling kube-up

Your active configuration is: [default]

Project: couchbase-on-kubernetes

Zone: us-central1-b

Creating gs://kubernetes-staging-9479406781

Creating gs://kubernetes-staging-9479406781/...

+++ Staging server tars to Google Storage: gs://kubernetes-staging-9479406781/devel

+++ kubernetes-server-linux-amd64.tar.gz uploaded (sha1 = 1ff42f7c31837851d919a66fc07f34b9dbdacf28)

+++ kubernetes-salt.tar.gz uploaded (sha1 = f307380ad6af7dabcf881b132146fa775c18dca8)

Looking for already existing resources

Starting master and configuring firewalls

Created [https://www.googleapis.com/compute/v1/projects/couchbase-on-kubernetes/zones/us-central1-b/disks/kubernetes-master-pd].

NAME ZONE SIZE_GB TYPE STATUS

kubernetes-master-pd us-central1-b 20 pd-ssd READY

Created [https://www.googleapis.com/compute/v1/projects/couchbase-on-kubernetes/regions/us-central1/addresses/kubernetes-master-ip].

Created [https://www.googleapis.com/compute/v1/projects/couchbase-on-kubernetes/global/firewalls/default-default-ssh].

Created [https://www.googleapis.com/compute/v1/projects/couchbase-on-kubernetes/global/firewalls/kubernetes-master-https].

NAME NETWORK SRC_RANGES RULES SRC_TAGS TARGET_TAGS

default-default-ssh default 0.0.0.0/0 tcp:22

NAME NETWORK SRC_RANGES RULES SRC_TAGS TARGET_TAGS

kubernetes-master-https default 0.0.0.0/0 tcp:443 kubernetes-master

+++ Logging using Fluentd to gcp

./kubernetes/cluster/../cluster/../cluster/gce/util.sh: line 434: @: unbound variable

Created [https://www.googleapis.com/compute/v1/projects/couchbase-on-kubernetes/global/firewalls/default-default-internal].

NAME NETWORK SRC_RANGES RULES SRC_TAGS TARGET_TAGS

default-default-internal default 10.0.0.0/8 tcp:1-65535,udp:1-65535,icmp

Created [https://www.googleapis.com/compute/v1/projects/couchbase-on-kubernetes/global/firewalls/kubernetes-minion-all].

NAME NETWORK SRC_RANGES RULES SRC_TAGS TARGET_TAGS

kubernetes-minion-all default 10.244.0.0/16 tcp,udp,icmp,esp,ah,sctp kubernetes-minion

Created [https://www.googleapis.com/compute/v1/projects/couchbase-on-kubernetes/zones/us-central1-b/instances/kubernetes-master].

NAME ZONE MACHINE_TYPE PREEMPTIBLE INTERNAL_IP EXTERNAL_IP STATUS

kubernetes-master us-central1-b n1-standard-1 10.128.0.2 104.197.213.249 RUNNING

Creating minions.

./kubernetes/cluster/../cluster/../cluster/gce/util.sh: line 434: @: unbound variable

Attempt 1 to create kubernetes-minion-template

WARNING: You have selected a disk size of under [200GB]. This may result in poor I/O performance. For more information, see: https://developers.google.com/compute/docs/disks/persistent-disks#pdperformance.

Created [https://www.googleapis.com/compute/v1/projects/couchbase-on-kubernetes/global/instanceTemplates/kubernetes-minion-template].

NAME MACHINE_TYPE PREEMPTIBLE CREATION_TIMESTAMP

kubernetes-minion-template n1-standard-1 2016-03-03T14:01:14.322-08:00

Created [https://www.googleapis.com/compute/v1/projects/couchbase-on-kubernetes/zones/us-central1-b/instanceGroupManagers/kubernetes-minion-group].

NAME ZONE BASE_INSTANCE_NAME SIZE TARGET_SIZE INSTANCE_TEMPLATE AUTOSCALED

kubernetes-minion-group us-central1-b kubernetes-minion 4 kubernetes-minion-template

Waiting for group to become stable, current operations: creating: 4

Waiting for group to become stable, current operations: creating: 3

Group is stable

MINION_NAMES=kubernetes-minion-1hmm kubernetes-minion-3x1d kubernetes-minion-h1ov kubernetes-minion-nshn

Using master: kubernetes-master (external IP: 104.197.213.249)

Waiting for cluster initialization.

This will continually check to see if the API for kubernetes is reachable.

This might loop forever if there was some uncaught error during start

up.

Kubernetes cluster created.

cluster "couchbase-on-kubernetes_kubernetes" set.

user "couchbase-on-kubernetes_kubernetes" set.

context "couchbase-on-kubernetes_kubernetes" set.

switched to context "couchbase-on-kubernetes_kubernetes".

user "couchbase-on-kubernetes_kubernetes-basic-auth" set.

Wrote config for couchbase-on-kubernetes_kubernetes to /Users/arungupta/.kube/config

Kubernetes cluster is running. The master is running at:

https://104.197.213.249

The user name and password to use is located in /Users/arungupta/.kube/config.

... calling validate-cluster

Waiting for 4 ready nodes. 0 ready nodes, 0 registered. Retrying.

Waiting for 4 ready nodes. 0 ready nodes, 2 registered. Retrying.

Waiting for 4 ready nodes. 0 ready nodes, 3 registered. Retrying.

Waiting for 4 ready nodes. 0 ready nodes, 4 registered. Retrying.

Waiting for 4 ready nodes. 3 ready nodes, 4 registered. Retrying.

Found 4 node(s).

NAME LABELS STATUS AGE

kubernetes-minion-1hmm kubernetes.io/hostname=kubernetes-minion-1hmm Ready 1m

kubernetes-minion-3x1d kubernetes.io/hostname=kubernetes-minion-3x1d Ready 52s

kubernetes-minion-h1ov kubernetes.io/hostname=kubernetes-minion-h1ov Ready 1m

kubernetes-minion-nshn kubernetes.io/hostname=kubernetes-minion-nshn Ready 1m

Validate output:

NAME STATUS MESSAGE ERROR

controller-manager Healthy ok nil

scheduler Healthy ok nil

etcd-0 Healthy {"health": "true"} nil

etcd-1 Healthy {"health": "true"} nil

Cluster validation succeeded

Done, listing cluster services:

Kubernetes master is running at https://104.197.213.249

GLBCDefaultBackend is running at https://104.197.213.249/api/v1/proxy/namespaces/kube-system/services/default-http-backend

Heapster is running at https://104.197.213.249/api/v1/proxy/namespaces/kube-system/services/heapster

KubeDNS is running at https://104.197.213.249/api/v1/proxy/namespaces/kube-system/services/kube-dns

KubeUI is running at https://104.197.213.249/api/v1/proxy/namespaces/kube-system/services/kube-ui

Grafana is running at https://104.197.213.249/api/v1/proxy/namespaces/kube-system/services/monitoring-grafana

InfluxDB is running at https://104.197.213.249/api/v1/proxy/namespaces/kube-system/services/monitoring-influxdb

There are a couple of unbound variables and a WARNING message, but that didn’t seem to break the script.

Google Cloud Console shows:

Five instances are created as shown – one for master node and four for worker nodes.

Run Docker Container in Kubernetes Cluster on Google Cloud

Now that the cluster is up and running, get a list of all the nodes:

./kubernetes/cluster/kubectl.sh get no
NAME                     LABELS                                          STATUS    AGE
kubernetes-minion-1hmm   kubernetes.io/hostname=kubernetes-minion-1hmm   Ready     47m
kubernetes-minion-3x1d   kubernetes.io/hostname=kubernetes-minion-3x1d   Ready     46m
kubernetes-minion-h1ov   kubernetes.io/hostname=kubernetes-minion-h1ov   Ready     47m
kubernetes-minion-nshn   kubernetes.io/hostname=kubernetes-minion-nshn   Ready     47m

./kubernetes/cluster/kubectl.sh get no

NAME LABELS STATUS AGE

kubernetes-minion-1hmm kubernetes.io/hostname=kubernetes-minion-1hmm Ready 47m

kubernetes-minion-3x1d kubernetes.io/hostname=kubernetes-minion-3x1d Ready 46m

kubernetes-minion-h1ov kubernetes.io/hostname=kubernetes-minion-h1ov Ready 47m

kubernetes-minion-nshn kubernetes.io/hostname=kubernetes-minion-nshn Ready 47m

It shows four worker nodes.

Create a Couchbase pod:

./kubernetes/cluster/kubectl.sh run couchbase --image=arungupta/couchbase
replicationcontroller "couchbase" created

./kubernetes/cluster/kubectl.sh run couchbase --image=arungupta/couchbase

replicationcontroller "couchbase" created

Notice, how the image name can be specified on the CLI. This command creates a Replication Controller with a single pod. The pod uses arungupta/couchbase Docker image that provides a pre-configured Couchbase server. Any Docker image can be specified here.

Get all the RC resources:

./kubernetes/cluster/kubectl.sh get rc
CONTROLLER   CONTAINER(S)   IMAGE(S)              SELECTOR        REPLICAS   AGE
couchbase    couchbase      arungupta/couchbase   run=couchbase   1          48s

./kubernetes/cluster/kubectl.sh get rc

CONTROLLER CONTAINER(S) IMAGE(S) SELECTOR REPLICAS AGE

couchbase couchbase arungupta/couchbase run=couchbase 1 48s

This shows the Replication Controller that is created for you.

Get all the Pods:

./kubernetes/cluster/kubectl.sh get po
NAME              READY     STATUS    RESTARTS   AGE
couchbase-s8v9r   1/1       Running   0          1m

./kubernetes/cluster/kubectl.sh get po

NAME READY STATUS RESTARTS AGE

couchbase-s8v9r 1/1 Running 0 1m

The output shows the Pod that is created as part of the Replication Controller.

Get more details about the Pod:

./kubernetes/cluster/kubectl.sh describe po couchbase-s8v9r
Name:                           couchbase-s8v9r
Namespace:                      default
Image(s):                       arungupta/couchbase
Node:                           kubernetes-minion-3x1d/10.128.0.3
Start Time:                     Thu, 03 Mar 2016 14:53:36 -0800
Labels:                         run=couchbase
Status:                         Running
Reason:                         
Message:                        
IP:                             10.244.3.3
Replication Controllers:        couchbase (1/1 replicas created)
Containers:
  couchbase:
    Container ID:       docker://601ee2e4c822814c3969a241e37c97bf4d0d209f952f24707ab308192d289098
    Image:              arungupta/couchbase
    Image ID:           docker://298618e67e495c2535abd17b60241565e456a4c9ee96c923ecf844a9dbcccced
    QoS Tier:
      cpu:      Burstable
    Requests:
      cpu:              100m
    State:              Running
      Started:          Thu, 03 Mar 2016 14:54:46 -0800
    Ready:              True
    Restart Count:      0
    Environment Variables:
Conditions:
  Type          Status
  Ready         True 
Volumes:
  default-token-frsd7:
    Type:       Secret (a secret that should populate this volume)
    SecretName: default-token-frsd7
Events:
  FirstSeen     LastSeen        Count   From                                    SubobjectPath                           Reason          Message
  ─────────     ────────        ─────   ────                                    ─────────────                           ──────          ───────
  1m            1m              1       {kubelet kubernetes-minion-3x1d}        implicitly required container POD       Pulled          Container image "gcr.io/google_containers/pause:0.8.0" already present on machine
  1m            1m              1       {scheduler }                                                                    Scheduled       Successfully assigned couchbase-s8v9r to kubernetes-minion-3x1d
  1m            1m              1       {kubelet kubernetes-minion-3x1d}        implicitly required container POD       Created         Created with docker id c1de9da87f1e
  1m            1m              1       {kubelet kubernetes-minion-3x1d}        spec.containers{couchbase}              Pulling         Pulling image "arungupta/couchbase"
  1m            1m              1       {kubelet kubernetes-minion-3x1d}        implicitly required container POD       Started         Started with docker id c1de9da87f1e
  29s           29s             1       {kubelet kubernetes-minion-3x1d}        spec.containers{couchbase}              Pulled          Successfully pulled image "arungupta/couchbase"
  29s           29s             1       {kubelet kubernetes-minion-3x1d}        spec.containers{couchbase}              Created         Created with docker id 601ee2e4c822
  29s           29s             1       {kubelet kubernetes-minion-3x1d}        spec.containers{couchbase}              Started         Started with docker id 601ee2e4c822

./kubernetes/cluster/kubectl.sh describe po couchbase-s8v9r

Name: couchbase-s8v9r

Namespace: default

Image(s): arungupta/couchbase

Node: kubernetes-minion-3x1d/10.128.0.3

Start Time: Thu, 03 Mar 2016 14:53:36 -0800

Labels: run=couchbase

Status: Running

Reason:

Message:

IP: 10.244.3.3

Replication Controllers: couchbase (1/1 replicas created)

Containers:

couchbase:

Container ID: docker://601ee2e4c822814c3969a241e37c97bf4d0d209f952f24707ab308192d289098

Image: arungupta/couchbase

Image ID: docker://298618e67e495c2535abd17b60241565e456a4c9ee96c923ecf844a9dbcccced

QoS Tier:

cpu: Burstable

Requests:

cpu: 100m

State: Running

Started: Thu, 03 Mar 2016 14:54:46 -0800

Ready: True

Restart Count: 0

Environment Variables:

Conditions:

Type Status

Ready True

Volumes:

default-token-frsd7:

Type: Secret (a secret that should populate this volume)

SecretName: default-token-frsd7

Events:

FirstSeen LastSeen Count From SubobjectPath Reason Message

───────── ──────── ───── ──── ───────────── ────── ───────

1m 1m 1 {kubelet kubernetes-minion-3x1d} implicitly required container POD Pulled Container image "gcr.io/google_containers/pause:0.8.0" already present on machine

1m 1m 1 {scheduler } Scheduled Successfully assigned couchbase-s8v9r to kubernetes-minion-3x1d

1m 1m 1 {kubelet kubernetes-minion-3x1d} implicitly required container POD Created Created with docker id c1de9da87f1e

1m 1m 1 {kubelet kubernetes-minion-3x1d} spec.containers{couchbase} Pulling Pulling image "arungupta/couchbase"

1m 1m 1 {kubelet kubernetes-minion-3x1d} implicitly required container POD Started Started with docker id c1de9da87f1e

29s 29s 1 {kubelet kubernetes-minion-3x1d} spec.containers{couchbase} Pulled Successfully pulled image "arungupta/couchbase"

29s 29s 1 {kubelet kubernetes-minion-3x1d} spec.containers{couchbase} Created Created with docker id 601ee2e4c822

29s 29s 1 {kubelet kubernetes-minion-3x1d} spec.containers{couchbase} Started Started with docker id 601ee2e4c822

Expose Pod on Kubernetes as Service

Now that our pod is running, how do I access the Couchbase server?

You need to expose it outside the Kubernetes cluster.

The kubectl expose command takes a pod, service or replication controller and expose it as a Kubernetes Service. Let’s expose the replication controller previously created and expose it:

./kubernetes/cluster/kubectl.sh expose rc couchbase --target-port=8091 --port=8091 --type=LoadBalancer
service "couchbase" exposed

./kubernetes/cluster/kubectl.sh expose rc couchbase --target-port=8091 --port=8091 --type=LoadBalancer

service "couchbase" exposed

Get more details about Service:

./kubernetes/cluster/kubectl.sh describe svc couchbase
Name:                   couchbase
Namespace:              default
Labels:                 run=couchbase
Selector:               run=couchbase
Type:                   LoadBalancer
IP:                     10.0.37.150
LoadBalancer Ingress:   104.197.118.35
Port:                   <unnamed> 8091/TCP
NodePort:               <unnamed> 30808/TCP
Endpoints:              10.244.3.3:8091
Session Affinity:       None
Events:
  FirstSeen     LastSeen        Count   From                    SubobjectPath   Reason                  Message
  ─────────     ────────        ─────   ────                    ─────────────   ──────                  ───────
  2m            2m              1       {service-controller }                   CreatingLoadBalancer    Creating load balancer
  1m            1m              1       {service-controller }                   CreatedLoadBalancer     Created load balancer

./kubernetes/cluster/kubectl.sh describe svc couchbase

Name: couchbase

Namespace: default

Labels: run=couchbase

Selector: run=couchbase

Type: LoadBalancer

IP: 10.0.37.150

LoadBalancer Ingress: 104.197.118.35

Port: <unnamed> 8091/TCP

NodePort: <unnamed> 30808/TCP

Endpoints: 10.244.3.3:8091

Session Affinity: None

Events:

FirstSeen LastSeen Count From SubobjectPath Reason Message

───────── ──────── ───── ──── ───────────── ────── ───────

2m 2m 1 {service-controller } CreatingLoadBalancer Creating load balancer

1m 1m 1 {service-controller } CreatedLoadBalancer Created load balancer

The Loadbalancer Ingress attribute gives you the IP address of the load balancer that is now publicly accessible.

Wait for 3 minutes to let the load balancer settle down. Access it using port 8091 and the login page for Couchbase Web Console shows up:

Enter the credentials as “Administrator” and “password” to see the Web Console:

Google Cloud Kubernetes Couchbase Web Console

And so you just accessed your pod outside the Kubernetes cluster.

Shutdown Kubernetes Cluster

Finally, shutdown the cluster using cluster/kube-down.sh script.

./kubernetes/cluster/kube-down.sh
Bringing down cluster using provider: gce
You have specified individual components to update.  If you are trying
 to install new components, use:
  $ gcloud components install alpha

Do you want to run install instead (y/N)?  


All components are up to date.
You have specified individual components to update.  If you are trying
 to install new components, use:
  $ gcloud components install beta

Do you want to run install instead (y/N)?  


All components are up to date.

All components are up to date.
Your active configuration is: [default]

Project: couchbase-on-kubernetes
Zone: us-central1-b
Bringing down cluster
Deleted [https://www.googleapis.com/compute/v1/projects/couchbase-on-kubernetes/zones/us-central1-b/instanceGroupManagers/kubernetes-minion-group].
Deleted [https://www.googleapis.com/compute/v1/projects/couchbase-on-kubernetes/global/instanceTemplates/kubernetes-minion-template].
Updated [https://www.googleapis.com/compute/v1/projects/couchbase-on-kubernetes/zones/us-central1-b/instances/kubernetes-master].
Deleted [https://www.googleapis.com/compute/v1/projects/couchbase-on-kubernetes/zones/us-central1-b/instances/kubernetes-master].
Deleted [https://www.googleapis.com/compute/v1/projects/couchbase-on-kubernetes/global/firewalls/kubernetes-master-https].
Deleted [https://www.googleapis.com/compute/v1/projects/couchbase-on-kubernetes/global/firewalls/kubernetes-minion-all].
Deleting routes kubernetes-ad3beb92-e18b-11e5-8e71-42010a800002
Deleted [https://www.googleapis.com/compute/v1/projects/couchbase-on-kubernetes/global/routes/kubernetes-ad3beb92-e18b-11e5-8e71-42010a800002].
Deleted [https://www.googleapis.com/compute/v1/projects/couchbase-on-kubernetes/regions/us-central1/addresses/kubernetes-master-ip].
property "clusters.couchbase-on-kubernetes_kubernetes" unset.
property "users.couchbase-on-kubernetes_kubernetes" unset.
property "users.couchbase-on-kubernetes_kubernetes-basic-auth" unset.
property "contexts.couchbase-on-kubernetes_kubernetes" unset.
property "current-context" unset.
Cleared config for couchbase-on-kubernetes_kubernetes from /Users/arungupta/.kube/config
Done

./kubernetes/cluster/kube-down.sh

Bringing down cluster using provider: gce

You have specified individual components to update. If you are trying

to install new components, use:

$ gcloud components install alpha

Do you want to run install instead (y/N)?

All components are up to date.

You have specified individual components to update. If you are trying

to install new components, use:

$ gcloud components install beta

Do you want to run install instead (y/N)?

All components are up to date.

Your active configuration is: [default]

Project: couchbase-on-kubernetes

Zone: us-central1-b

Bringing down cluster

Deleted [https://www.googleapis.com/compute/v1/projects/couchbase-on-kubernetes/zones/us-central1-b/instanceGroupManagers/kubernetes-minion-group].

Deleted [https://www.googleapis.com/compute/v1/projects/couchbase-on-kubernetes/global/instanceTemplates/kubernetes-minion-template].

Updated [https://www.googleapis.com/compute/v1/projects/couchbase-on-kubernetes/zones/us-central1-b/instances/kubernetes-master].

Deleted [https://www.googleapis.com/compute/v1/projects/couchbase-on-kubernetes/zones/us-central1-b/instances/kubernetes-master].

Deleted [https://www.googleapis.com/compute/v1/projects/couchbase-on-kubernetes/global/firewalls/kubernetes-master-https].

Deleted [https://www.googleapis.com/compute/v1/projects/couchbase-on-kubernetes/global/firewalls/kubernetes-minion-all].

Deleting routes kubernetes-ad3beb92-e18b-11e5-8e71-42010a800002

Deleted [https://www.googleapis.com/compute/v1/projects/couchbase-on-kubernetes/global/routes/kubernetes-ad3beb92-e18b-11e5-8e71-42010a800002].

Deleted [https://www.googleapis.com/compute/v1/projects/couchbase-on-kubernetes/regions/us-central1/addresses/kubernetes-master-ip].

property "clusters.couchbase-on-kubernetes_kubernetes" unset.

property "users.couchbase-on-kubernetes_kubernetes" unset.

property "users.couchbase-on-kubernetes_kubernetes-basic-auth" unset.

property "contexts.couchbase-on-kubernetes_kubernetes" unset.

property "current-context" unset.

Cleared config for couchbase-on-kubernetes_kubernetes from /Users/arungupta/.kube/config

Done

Enjoy!

Source: http://blog.couchbase.com/2016/march/kubernetes-cluster-google-cloud-expose-service

Kubernetes Cluster on Amazon and Expose Couchbase Service

March 2, 2016containers, couchbaseamazon, couchbase, docker, kubernetesarungupta

The first part (Couchbase on Kubernetes) explained how to start the Kubernetes cluster using Vagrant. That is a simple and easy way to develop, test, and deploy Kubernetes cluster on your local machine. But this could be of limited use rather soon as the resources are constrained by the local machine. So what do you do?

Kubernetes cluster can be installed on Amazon as well. This second part will show:

How to setup and start the Kubernetes cluster on Amazon Web Services
Run Docker container in the Kubernetes cluster
Expose Pod on Kubernetes as Service
Shutdown the cluster

Here is a quick overview:

Let’s dig into the details!

Setup Kubernetes Cluster on Amazon Web Services

Getting Started on AWS EC2 provide complete instructions to start Kubernetes cluster on Amazon. Make sure to have the pre-requisites (AWS account, AWS CLI, Full EC2 access) met before you follow these instructions.

Kubernetes cluster can be created on Amazon as:

set KUBERNETES_PROVIDER=aws
./cluster/kube-up.sh

set KUBERNETES_PROVIDER=aws

./cluster/kube-up.sh

By default, this provisions a new VPC and a 4 node Kubernetes cluster in us-west-2a (Oregon) with t2.micro instances running on Ubuntu. This means 5 AMIs (one for master and 4 for the worker nodes) are created. Some properties that are worth updating:

Set NUM_MINIONS environment variable to whatever number of nodes are required in the cluster. Set it to 2 if you want only two worker nodes to be created.
Each instance size is 1.1.x is t2.micro. Set MASTER_SIZE and MINION_SIZE environment variables to m3.medium otherwise the nodes are going to crawl.

If you downloaded Kubernetes from github.com/kubernetes/kubernetes/releases, then all the values can be changed in cluster/aws/config-default.sh.

Starting Kubernetes on Amazon shows the following log:

./kubernetes/cluster/kube-up.sh
... Starting cluster using provider: aws
... calling verify-prereqs
... calling kube-up
Starting cluster using os distro: vivid
Uploading to Amazon S3
+++ Staging server tars to S3 Storage: kubernetes-staging-0eaf81fbc51209dd47c13b6d8b424149/devel
{
    "InstanceProfile": {
        "InstanceProfileId": "AIPAJMNMKZSXNWXQBHXHI",
        "Roles": [
            {
                "RoleName": "kubernetes-master",
                "AssumeRolePolicyDocument": {
                    "Version": "2012-10-17",
                    "Statement": [
                        {
                            "Action": "sts:AssumeRole",
                            "Effect": "Allow",
                            "Principal": {
                                "Service": "ec2.amazonaws.com"
                            }
                        }
                    ]
                },
                "CreateDate": "2016-02-29T23:19:17Z",
                "Path": "/",
                "RoleId": "AROAJW7ER37BPXX5KFTFS",
                "Arn": "arn:aws:iam::598307997273:role/kubernetes-master"
            }
        ],
        "Arn": "arn:aws:iam::598307997273:instance-profile/kubernetes-master",
        "CreateDate": "2016-02-29T23:19:19Z",
        "Path": "/",
        "InstanceProfileName": "kubernetes-master"
    }
}
{
    "InstanceProfile": {
        "InstanceProfileId": "AIPAILRAU7RF4R2SDCULG",
        "Path": "/",
        "Arn": "arn:aws:iam::598307997273:instance-profile/kubernetes-minion",
        "Roles": [
            {
                "Path": "/",
                "AssumeRolePolicyDocument": {
                    "Statement": [
                        {
                            "Effect": "Allow",
                            "Action": "sts:AssumeRole",
                            "Principal": {
                                "Service": "ec2.amazonaws.com"
                            }
                        }
                    ],
                    "Version": "2012-10-17"
                },
                "RoleName": "kubernetes-minion",
                "Arn": "arn:aws:iam::598307997273:role/kubernetes-minion",
                "RoleId": "AROAIBEPV6VW4IEE6MRHS",
                "CreateDate": "2016-02-29T23:19:21Z"
            }
        ],
        "InstanceProfileName": "kubernetes-minion",
        "CreateDate": "2016-02-29T23:19:22Z"
    }
}
Using SSH key with (AWS) fingerprint: 39:b3:cb:c1:af:6a:86:de:98:95:01:3d:9a:56:bb:8b
Creating vpc.
Adding tag to vpc-7b46ac1f: Name=kubernetes-vpc
Adding tag to vpc-7b46ac1f: KubernetesCluster=kubernetes
Using VPC vpc-7b46ac1f
Creating subnet.
Adding tag to subnet-cc906fa8: KubernetesCluster=kubernetes
Using subnet subnet-cc906fa8
Creating Internet Gateway.
Using Internet Gateway igw-40055525
Associating route table.
Creating route table
Adding tag to rtb-f2dc1596: KubernetesCluster=kubernetes
Associating route table rtb-f2dc1596 to subnet subnet-cc906fa8
Adding route to route table rtb-f2dc1596
Using Route Table rtb-f2dc1596
Creating master security group.
Creating security group kubernetes-master-kubernetes.
Adding tag to sg-308b3357: KubernetesCluster=kubernetes
Creating minion security group.
Creating security group kubernetes-minion-kubernetes.
Adding tag to sg-3b8b335c: KubernetesCluster=kubernetes
Using master security group: kubernetes-master-kubernetes sg-308b3357
Using minion security group: kubernetes-minion-kubernetes sg-3b8b335c
Starting Master
Adding tag to i-b71a6f70: Name=kubernetes-master
Adding tag to i-b71a6f70: Role=kubernetes-master
Adding tag to i-b71a6f70: KubernetesCluster=kubernetes
Waiting for master to be ready
Attempt 1 to check for master nodeWaiting for instance i-b71a6f70 to spawn
Sleeping for 3 seconds...
Waiting for instance i-b71a6f70 to spawn
Sleeping for 3 seconds...
Waiting for instance i-b71a6f70 to spawn
Sleeping for 3 seconds...
Waiting for instance i-b71a6f70 to spawn
Sleeping for 3 seconds...
Waiting for instance i-b71a6f70 to spawn
Sleeping for 3 seconds...
Waiting for instance i-b71a6f70 to spawn
Sleeping for 3 seconds...
 [master running @52.34.244.195]
Attaching persistent data volume (vol-e072d316) to master
{
    "Device": "/dev/sdb",
    "State": "attaching",
    "InstanceId": "i-b71a6f70",
    "VolumeId": "vol-e072d316",
    "AttachTime": "2016-03-02T18:10:15.985Z"
}
Attempt 1 to check for SSH to master [ssh to master working]
Attempt 1 to check for salt-master [salt-master not working yet]
Attempt 2 to check for salt-master [salt-master not working yet]
Attempt 3 to check for salt-master [salt-master not working yet]
Attempt 4 to check for salt-master [salt-master not working yet]
Attempt 5 to check for salt-master [salt-master not working yet]
Attempt 6 to check for salt-master [salt-master not working yet]
Attempt 7 to check for salt-master [salt-master not working yet]
Attempt 8 to check for salt-master [salt-master not working yet]
Attempt 9 to check for salt-master [salt-master not working yet]
Attempt 10 to check for salt-master [salt-master not working yet]
Attempt 11 to check for salt-master [salt-master not working yet]
Attempt 12 to check for salt-master [salt-master not working yet]
Attempt 13 to check for salt-master [salt-master not working yet]
Attempt 14 to check for salt-master [salt-master running]
Creating minion configuration
Creating autoscaling group
 0 minions started; waiting
 0 minions started; waiting
 0 minions started; waiting
 0 minions started; waiting
 2 minions started; ready
Waiting 3 minutes for cluster to settle
..................Re-running salt highstate
Waiting for cluster initialization.

  This will continually check to see if the API for kubernetes is reachable.
  This might loop forever if there was some uncaught error during start
  up.

Kubernetes cluster created.
cluster "aws_kubernetes" set.
user "aws_kubernetes" set.
context "aws_kubernetes" set.
switched to context "aws_kubernetes".
Wrote config for aws_kubernetes to /Users/arungupta/.kube/config
Sanity checking cluster...
Attempt 1 to check Docker on node @ 52.37.172.215 ...not working yet
Attempt 2 to check Docker on node @ 52.37.172.215 ...not working yet
Attempt 3 to check Docker on node @ 52.37.172.215 ...working
Attempt 1 to check Docker on node @ 52.27.90.19 ...working

Kubernetes cluster is running.  The master is running at:

  https://52.34.244.195

The user name and password to use is located in /Users/arungupta/.kube/config.

... calling validate-cluster
Waiting for 2 ready nodes. 1 ready nodes, 2 registered. Retrying.
Found 2 node(s).
NAME                                        LABELS                                                             STATUS    AGE
ip-172-20-0-92.us-west-2.compute.internal   kubernetes.io/hostname=ip-172-20-0-92.us-west-2.compute.internal   Ready     56s
ip-172-20-0-93.us-west-2.compute.internal   kubernetes.io/hostname=ip-172-20-0-93.us-west-2.compute.internal   Ready     35s
Validate output:
NAME                 STATUS    MESSAGE              ERROR
controller-manager   Healthy   ok                   nil
scheduler            Healthy   ok                   nil
etcd-0               Healthy   {"health": "true"}   nil
etcd-1               Healthy   {"health": "true"}   nil
Cluster validation succeeded
Done, listing cluster services:

Kubernetes master is running at https://52.34.244.195
Elasticsearch is running at https://52.34.244.195/api/v1/proxy/namespaces/kube-system/services/elasticsearch-logging
Heapster is running at https://52.34.244.195/api/v1/proxy/namespaces/kube-system/services/heapster
Kibana is running at https://52.34.244.195/api/v1/proxy/namespaces/kube-system/services/kibana-logging
KubeDNS is running at https://52.34.244.195/api/v1/proxy/namespaces/kube-system/services/kube-dns
KubeUI is running at https://52.34.244.195/api/v1/proxy/namespaces/kube-system/services/kube-ui
Grafana is running at https://52.34.244.195/api/v1/proxy/namespaces/kube-system/services/monitoring-grafana
InfluxDB is running at https://52.34.244.195/api/v1/proxy/namespaces/kube-system/services/monitoring-influxdb

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

Miles to go 3.0 …

Arun Gupta is a technology enthusiast, avid runner, author of a best-selling book, globe trotter, a community guy, Java Champion, JavaOne Rockstar, JUG Leader, Minecraft Modder, NetBeans Dream Teamer, Devoxx4Kids-er, and a Couchbaser.

Tag Archives: kubernetes

Kubernetes Cluster on Azure and Expose Couchbase Service

Install and Configure Azure CLI

Start Kubernetes Cluster

Run Docker Container in Kubernetes Cluster on Azure

Expose Pod on Kubernetes as Service

Shutdown Kubernetes Cluster

Kubernetes Namespaces, Resource Quota, and Limits for QoS in Cluster

Default Kubernetes Namespace

Create a Resource in New Kubernetes Namespace

Set Kubernetes Namespace For an Existing Resource

Delete a Kubernetes Resource in Namespace

Resource Quota and Limit using Kubernetes Namespace

Specifying Limits During Pod Creation

Kubernetes Cluster on Google Cloud and Expose Couchbase Service

Download and Configure Google Cloud SDK

Setup Kubernetes Cluster on Google Cloud

Run Docker Container in Kubernetes Cluster on Google Cloud

Expose Pod on Kubernetes as Service

Shutdown Kubernetes Cluster

Kubernetes Cluster on Amazon and Expose Couchbase Service

Setup Kubernetes Cluster on Amazon Web Services