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

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

./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

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

Amazon Console shows:

Three instances are created as shown – one for master node and two for worker nodes.

Username and password for the Kubernetes master are stored in /Users/arungupta/.kube/config. Look for a section like:

- name: aws_kubernetes
  user:
    client-certificate-data: DATA
    client-key-data: DATA
    password: 3FkxcAURLCWBXc9H
    username: admin

- name: aws_kubernetes

user:

client-certificate-data: DATA

client-key-data: DATA

password: 3FkxcAURLCWBXc9H

username: admin

Run Docker container in Kubernetes Cluster on Amazon

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
ip-172-20-0-92.us-west-2.compute.internal   kubernetes.io/hostname=ip-172-20-0-92.us-west-2.compute.internal   Ready     18m
ip-172-20-0-93.us-west-2.compute.internal   kubernetes.io/hostname=ip-172-20-0-93.us-west-2.compute.internal   Ready     18m

./kubernetes/cluster/kubectl.sh get no

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 18m

ip-172-20-0-93.us-west-2.compute.internal kubernetes.io/hostname=ip-172-20-0-93.us-west-2.compute.internal Ready 18m

It shows two worker nodes.

Create a new 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

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          12m

./kubernetes/cluster/kubectl.sh get rc

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

couchbase couchbase arungupta/couchbase run=couchbase 1 12m

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-kil4y   1/1       Running   0          12m

./kubernetes/cluster/kubectl.sh get po

NAME READY STATUS RESTARTS AGE

couchbase-kil4y 1/1 Running 0 12m

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-kil4y
Name:                           couchbase-kil4y
Namespace:                      default
Image(s):                       arungupta/couchbase
Node:                           ip-172-20-0-93.us-west-2.compute.internal/172.20.0.93
Start Time:                     Wed, 02 Mar 2016 10:25:47 -0800
Labels:                         run=couchbase
Status:                         Running
Reason:                         
Message:                        
IP:                             10.244.1.4
Replication Controllers:        couchbase (1/1 replicas created)
Containers:
  couchbase:
    Container ID:       docker://1c33e4f28978a5169a5d166add7c763de59839ed1f12865f4643456efdc0c60e
    Image:              arungupta/couchbase
    Image ID:           docker://080e2e96b3fc22964f3dec079713cdf314e15942d6eb135395134d629e965062
    QoS Tier:
      cpu:      Burstable
    Requests:
      cpu:              100m
    State:              Running
      Started:          Wed, 02 Mar 2016 10:26:18 -0800
    Ready:              True
    Restart Count:      0
    Environment Variables:
Conditions:
  Type          Status
  Ready         True 
Volumes:
  default-token-xuxn5:
    Type:       Secret (a secret that should populate this volume)
    SecretName: default-token-xuxn5
Events:
  FirstSeen     LastSeen        Count   From                                                    SubobjectPath           Reason          Message
  ─────────     ────────        ─────   ────                                                    ─────────────           ──────          ───────
  13m           13m             1       {scheduler }                                                                    Scheduled       Successfully assigned couchbase-kil4y to ip-172-20-0-93.us-west-2.compute.internal
  13m           13m             1       {kubelet ip-172-20-0-93.us-west-2.compute.internal}     implicitly required container POD       Pulled          Container image "gcr.io/google_containers/pause:0.8.0" already present on machine
  13m           13m             1       {kubelet ip-172-20-0-93.us-west-2.compute.internal}     implicitly required container POD       Created         Created with docker id 3830f504a7b6
  13m           13m             1       {kubelet ip-172-20-0-93.us-west-2.compute.internal}     implicitly required container POD       Started         Started with docker id 3830f504a7b6
  13m           13m             1       {kubelet ip-172-20-0-93.us-west-2.compute.internal}     spec.containers{couchbase}              Pulling         Pulling image "arungupta/couchbase"
  12m           12m             1       {kubelet ip-172-20-0-93.us-west-2.compute.internal}     spec.containers{couchbase}              Pulled          Successfully pulled image "arungupta/couchbase"
  12m           12m             1       {kubelet ip-172-20-0-93.us-west-2.compute.internal}     spec.containers{couchbase}              Created         Created with docker id 1c33e4f28978
  12m           12m             1       {kubelet ip-172-20-0-93.us-west-2.compute.internal}     spec.containers{couchbase}              Started         Started with docker id 1c33e4f28978

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

Name: couchbase-kil4y

Namespace: default

Image(s): arungupta/couchbase

Node: ip-172-20-0-93.us-west-2.compute.internal/172.20.0.93

Start Time: Wed, 02 Mar 2016 10:25:47 -0800

Labels: run=couchbase

Status: Running

Reason:

Message:

IP: 10.244.1.4

Replication Controllers: couchbase (1/1 replicas created)

Containers:

couchbase:

Container ID: docker://1c33e4f28978a5169a5d166add7c763de59839ed1f12865f4643456efdc0c60e

Image: arungupta/couchbase

Image ID: docker://080e2e96b3fc22964f3dec079713cdf314e15942d6eb135395134d629e965062

QoS Tier:

cpu: Burstable

Requests:

cpu: 100m

State: Running

Started: Wed, 02 Mar 2016 10:26:18 -0800

Ready: True

Restart Count: 0

Environment Variables:

Conditions:

Type Status

Ready True

Volumes:

default-token-xuxn5:

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

SecretName: default-token-xuxn5

Events:

FirstSeen LastSeen Count From SubobjectPath Reason Message

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

13m 13m 1 {scheduler } Scheduled Successfully assigned couchbase-kil4y to ip-172-20-0-93.us-west-2.compute.internal

13m 13m 1 {kubelet ip-172-20-0-93.us-west-2.compute.internal} implicitly required container POD Pulled Container image "gcr.io/google_containers/pause:0.8.0" already present on machine

13m 13m 1 {kubelet ip-172-20-0-93.us-west-2.compute.internal} implicitly required container POD Created Created with docker id 3830f504a7b6

13m 13m 1 {kubelet ip-172-20-0-93.us-west-2.compute.internal} implicitly required container POD Started Started with docker id 3830f504a7b6

13m 13m 1 {kubelet ip-172-20-0-93.us-west-2.compute.internal} spec.containers{couchbase} Pulling Pulling image "arungupta/couchbase"

12m 12m 1 {kubelet ip-172-20-0-93.us-west-2.compute.internal} spec.containers{couchbase} Pulled Successfully pulled image "arungupta/couchbase"

12m 12m 1 {kubelet ip-172-20-0-93.us-west-2.compute.internal} spec.containers{couchbase} Created Created with docker id 1c33e4f28978

12m 12m 1 {kubelet ip-172-20-0-93.us-west-2.compute.internal} spec.containers{couchbase} Started Started with docker id 1c33e4f28978

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 the Service:

./kubernetes/cluster/kubectl.sh describe svc couchbase
Name:                   couchbase
Namespace:              default
Labels:                 run=couchbase
Selector:               run=couchbase
Type:                   LoadBalancer
IP:                     10.0.158.93
LoadBalancer Ingress:   a44d3f016e0a411e5888f0206c9933da-1869988881.us-west-2.elb.amazonaws.com
Port:                   <unnamed> 8091/TCP
NodePort:               <unnamed> 32415/TCP
Endpoints:              10.244.1.4:8091
Session Affinity:       None
Events:
  FirstSeen     LastSeen        Count   From                    SubobjectPath   Reason                  Message
  ─────────     ────────        ─────   ────                    ─────────────   ──────                  ───────
  7s            7s              1       {service-controller }                   CreatingLoadBalancer    Creating load balancer
  5s            5s              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.158.93

LoadBalancer Ingress: a44d3f016e0a411e5888f0206c9933da-1869988881.us-west-2.elb.amazonaws.com

Port: <unnamed> 8091/TCP

NodePort: <unnamed> 32415/TCP

Endpoints: 10.244.1.4:8091

Session Affinity: None

Events:

FirstSeen LastSeen Count From SubobjectPath Reason Message

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

7s 7s 1 {service-controller } CreatingLoadBalancer Creating load balancer

5s 5s 1 {service-controller } CreatedLoadBalancer Created load balancer

The Loadbalancer attribute Ingress gives you the 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:

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: aws
Deleting ELBs in: vpc-7b46ac1f
Waiting for ELBs to be deleted
All ELBs deleted
Deleting auto-scaling group: kubernetes-minion-group
Deleting auto-scaling launch configuration: kubernetes-minion-group
Deleting instances in VPC: vpc-7b46ac1f
Waiting for instances to be deleted
Instances not yet deleted: i-45077282 i-44077283 i-b71a6f70
Sleeping for 3 seconds...
Instances not yet deleted: i-45077282 i-44077283 i-b71a6f70
Sleeping for 3 seconds...
Instances not yet deleted: i-45077282 i-44077283 i-b71a6f70
Sleeping for 3 seconds...
Instances not yet deleted: i-45077282 i-44077283 i-b71a6f70
Sleeping for 3 seconds...
Instances not yet deleted: i-45077282 i-44077283 i-b71a6f70
Sleeping for 3 seconds...
Instances not yet deleted: i-45077282 i-44077283 i-b71a6f70
Sleeping for 3 seconds...
Instances not yet deleted: i-45077282 i-44077283 i-b71a6f70
Sleeping for 3 seconds...
Instances not yet deleted: i-45077282 i-44077283 i-b71a6f70
Sleeping for 3 seconds...
Instances not yet deleted: i-45077282 i-44077283 i-b71a6f70
Sleeping for 3 seconds...
Instances not yet deleted: i-45077282 i-44077283 i-b71a6f70
Sleeping for 3 seconds...
Instances not yet deleted: i-45077282 i-44077283 i-b71a6f70
Sleeping for 3 seconds...
Instances not yet deleted: i-45077282 i-44077283 i-b71a6f70
Sleeping for 3 seconds...
Instances not yet deleted: i-44077283 i-b71a6f70
Sleeping for 3 seconds...
All instances deleted
Deleting VPC: vpc-7b46ac1f
Cleaning up security group: sg-308b3357
Cleaning up security group: sg-3b8b335c
Cleaning up security group: sg-e3813984
Deleting security group: sg-308b3357
Deleting security group: sg-3b8b335c
Deleting security group: sg-e3813984
Done

./kubernetes/cluster/kube-down.sh

Bringing down cluster using provider: aws

Deleting ELBs in: vpc-7b46ac1f

Waiting for ELBs to be deleted

All ELBs deleted

Deleting auto-scaling group: kubernetes-minion-group

Deleting auto-scaling launch configuration: kubernetes-minion-group

Deleting instances in VPC: vpc-7b46ac1f

Waiting for instances to be deleted

Instances not yet deleted: i-45077282 i-44077283 i-b71a6f70

Sleeping for 3 seconds...

Instances not yet deleted: i-45077282 i-44077283 i-b71a6f70

Sleeping for 3 seconds...

Instances not yet deleted: i-45077282 i-44077283 i-b71a6f70

Sleeping for 3 seconds...

Instances not yet deleted: i-45077282 i-44077283 i-b71a6f70

Sleeping for 3 seconds...

Instances not yet deleted: i-45077282 i-44077283 i-b71a6f70

Sleeping for 3 seconds...

Instances not yet deleted: i-45077282 i-44077283 i-b71a6f70

Sleeping for 3 seconds...

Instances not yet deleted: i-45077282 i-44077283 i-b71a6f70

Sleeping for 3 seconds...

Instances not yet deleted: i-45077282 i-44077283 i-b71a6f70

Sleeping for 3 seconds...

Instances not yet deleted: i-45077282 i-44077283 i-b71a6f70

Sleeping for 3 seconds...

Instances not yet deleted: i-45077282 i-44077283 i-b71a6f70

Sleeping for 3 seconds...

Instances not yet deleted: i-45077282 i-44077283 i-b71a6f70

Sleeping for 3 seconds...

Instances not yet deleted: i-45077282 i-44077283 i-b71a6f70

Sleeping for 3 seconds...

Instances not yet deleted: i-44077283 i-b71a6f70

Sleeping for 3 seconds...

All instances deleted

Deleting VPC: vpc-7b46ac1f

Cleaning up security group: sg-308b3357

Cleaning up security group: sg-3b8b335c

Cleaning up security group: sg-e3813984

Deleting security group: sg-308b3357

Deleting security group: sg-3b8b335c

Deleting security group: sg-e3813984

Done

For a complete clean up, you still need to explicitly delete the S3 bucket where Kubernetes binaries are stored.

Enjoy!

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

Couchbase on Kubernetes

February 26, 2016containers, couchbasecouchbase, docker, kubernetesarungupta

This blog is possible because of this tweet!

Had a great #Couchbase #Kubernetes hacking session with @saturnism, learned a lot, look forward to some nice blogs.

— Arun Gupta (@arungupta) February 27, 2016

Kubernetes is an open source orchestration system by Google for Docker containers. It manages containerized applications across multiple hosts and provides basic mechanisms for deployment, maintenance, and scaling of applications.

It allows the user to provide declarative primitives for the desired state, for example “need 5 Couchbase servers”. Kubernetes self-healing mechanisms, such as auto-restarting, re-scheduling, and replicating containers then ensure that this state is met. The user just define the state and Kubernetes ensures that the state is met at all times on the cluster.

Key Concepts of Kubernetes explains the key concepts of Kubernetes.

This multi-part blog series will show how to run Couchbase on Kubernetes in multiple ways. The first part starts with a simple setup using Vagrant.

Getting Started with Kubernetes

There are multiple ways to run Kubernetes but I found the simples (not necessarily predictable 😉 way is to run using Vagrant.

Download the latest Kubernetes release, 1.1.8 as of this writing, and expand the archive.

Start the Kubernetes cluster as:

cd kubernetes

export KUBERNETES_PROVIDER=vagrant
./cluster/kube-up.sh

cd kubernetes

export KUBERNETES_PROVIDER=vagrant

./cluster/kube-up.sh

This shows the output as:

kubernetes-1.1.8 > ./kubernetes/cluster/kube-up.sh 
... Starting cluster using provider: vagrant
... calling verify-prereqs
... calling kube-up
Bringing machine 'master' up with 'virtualbox' provider...
Bringing machine 'minion-1' up with 'virtualbox' provider...
==> master: Importing base box 'kube-fedora21'...

. . .

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://10.245.1.2
Heapster is running at https://10.245.1.2/api/v1/proxy/namespaces/kube-system/services/heapster
KubeDNS is running at https://10.245.1.2/api/v1/proxy/namespaces/kube-system/services/kube-dns
KubeUI is running at https://10.245.1.2/api/v1/proxy/namespaces/kube-system/services/kube-ui
Grafana is running at https://10.245.1.2/api/v1/proxy/namespaces/kube-system/services/monitoring-grafana
InfluxDB is running at https://10.245.1.2/api/v1/proxy/namespaces/kube-system/services/monitoring-influxdb

kubernetes-1.1.8 > ./kubernetes/cluster/kube-up.sh

... Starting cluster using provider: vagrant

... calling verify-prereqs

... calling kube-up

Bringing machine 'master' up with 'virtualbox' provider...

Bringing machine 'minion-1' up with 'virtualbox' provider...

==> master: Importing base box 'kube-fedora21'...

. . .

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://10.245.1.2

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

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

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

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

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

Run Couchbase on Kubernetes Cluster

The easiest way to start running a Docker container in Kubernetes is using the kubectl run command.

The command usage is:

kubectl run NAME --image=image [--env="key=value"] [--port=port] [--replicas=replicas] [--dry-run=bool] [--overrides=inline-json] [flags]

kubectl run NAME --image=image [--env="key=value"] [--port=port] [--replicas=replicas] [--dry-run=bool] [--overrides=inline-json] [flags]

The command runs a particular image, possibly replicated. The image replication is handled by creating a Replication Controller to manage the created container(s).

Complete list of options to run this command can be seen using:

./cluster/kubectl.sh run --help

./cluster/kubectl.sh run --help

Couchbase Docker Container explains the different Docker container for Couchbase. For this blog, we’ll use arungupta/couchbase image as that is pre-configured.

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

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

This shows the output:

replicationcontroller "couchbase" created

replicationcontroller "couchbase" created

The output confirms that a Replication Controller is created. Lets verify it:

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

./kubernetes/cluster/kubectl.sh get rc

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

couchbase couchbase arungupta/couchbase run=couchbase 1 17s

Now, check the pods:

./kubernetes/cluster/kubectl.sh get po
NAME              READY     STATUS    RESTARTS   AGE
couchbase-tzdhl   0/1       Pending   0          36s

./kubernetes/cluster/kubectl.sh get po

NAME READY STATUS RESTARTS AGE

couchbase-tzdhl 0/1 Pending 0 36s

Lets check the status of the pod:

./kubernetes/cluster/kubectl.sh describe pod couchbase-tzdhl
Name:                           couchbase-tzdhl
Namespace:                      default
Image(s):                       arungupta/couchbase
Node:                           10.245.1.4/10.245.1.4
Start Time:                     Fri, 26 Feb 2016 18:05:10 -0800
Labels:                         run=couchbase
Status:                         Running
Reason:                         
Message:                        
IP:                             10.246.67.2
Replication Controllers:        couchbase (1/1 replicas created)
Containers:
  couchbase:
    Container ID:       docker://56dddb66bf60a590e588b972d5cae997ec96149066a9fb8075548c982eb14961
    Image:              arungupta/couchbase
    Image ID:           docker://080e2e96b3fc22964f3dec079713cdf314e15942d6eb135395134d629e965062
    QoS Tier:
      cpu:      Burstable
    Requests:
      cpu:              100m
    State:              Running
      Started:          Fri, 26 Feb 2016 18:05:56 -0800
    Ready:              True
    Restart Count:      0
    Environment Variables:
Conditions:
  Type          Status
  Ready         True 
Volumes:
  default-token-clfeb:
    Type:       Secret (a secret that should populate this volume)
    SecretName: default-token-clfeb
Events:
  FirstSeen     LastSeen        Count   From                    SubobjectPath                           Reason          Message
  ─────────     ────────        ─────   ────                    ─────────────                           ──────          ───────
  1m            1m              1       {scheduler }                                                    Scheduled       Successfully assigned couchbase-tzdhl to 10.245.1.4
  1m            1m              1       {kubelet 10.245.1.4}    implicitly required container POD       Pulling         Pulling image "gcr.io/google_containers/pause:0.8.0"
  59s           59s             1       {kubelet 10.245.1.4}    implicitly required container POD       Created         Created with docker id 2dac5f81f4c2
  59s           59s             1       {kubelet 10.245.1.4}    spec.containers{couchbase}              Pulling         Pulling image "arungupta/couchbase"
  59s           59s             1       {kubelet 10.245.1.4}    implicitly required container POD       Started         Started with docker id 2dac5f81f4c2
  59s           59s             1       {kubelet 10.245.1.4}    implicitly required container POD       Pulled          Successfully pulled image "gcr.io/google_containers/pause:0.8.0"
  19s           19s             1       {kubelet 10.245.1.4}    spec.containers{couchbase}              Pulled          Successfully pulled image "arungupta/couchbase"
  18s           18s             1       {kubelet 10.245.1.4}    spec.containers{couchbase}              Created         Created with docker id 56dddb66bf60
  18s           18s             1       {kubelet 10.245.1.4}    spec.containers{couchbase}              Started         Started with docker id 56dddb66bf60

./kubernetes/cluster/kubectl.sh describe pod couchbase-tzdhl

Name: couchbase-tzdhl

Namespace: default

Image(s): arungupta/couchbase

Node: 10.245.1.4/10.245.1.4

Start Time: Fri, 26 Feb 2016 18:05:10 -0800

Labels: run=couchbase

Status: Running

Reason:

Message:

IP: 10.246.67.2

Replication Controllers: couchbase (1/1 replicas created)

Containers:

couchbase:

Container ID: docker://56dddb66bf60a590e588b972d5cae997ec96149066a9fb8075548c982eb14961

Image: arungupta/couchbase

Image ID: docker://080e2e96b3fc22964f3dec079713cdf314e15942d6eb135395134d629e965062

QoS Tier:

cpu: Burstable

Requests:

cpu: 100m

State: Running

Started: Fri, 26 Feb 2016 18:05:56 -0800

Ready: True

Restart Count: 0

Environment Variables:

Conditions:

Type Status

Ready True

Volumes:

default-token-clfeb:

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

SecretName: default-token-clfeb

Events:

FirstSeen LastSeen Count From SubobjectPath Reason Message

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

1m 1m 1 {scheduler } Scheduled Successfully assigned couchbase-tzdhl to 10.245.1.4

1m 1m 1 {kubelet 10.245.1.4} implicitly required container POD Pulling Pulling image "gcr.io/google_containers/pause:0.8.0"

59s 59s 1 {kubelet 10.245.1.4} implicitly required container POD Created Created with docker id 2dac5f81f4c2

59s 59s 1 {kubelet 10.245.1.4} spec.containers{couchbase} Pulling Pulling image "arungupta/couchbase"

59s 59s 1 {kubelet 10.245.1.4} implicitly required container POD Started Started with docker id 2dac5f81f4c2

59s 59s 1 {kubelet 10.245.1.4} implicitly required container POD Pulled Successfully pulled image "gcr.io/google_containers/pause:0.8.0"

19s 19s 1 {kubelet 10.245.1.4} spec.containers{couchbase} Pulled Successfully pulled image "arungupta/couchbase"

18s 18s 1 {kubelet 10.245.1.4} spec.containers{couchbase} Created Created with docker id 56dddb66bf60

18s 18s 1 {kubelet 10.245.1.4} spec.containers{couchbase} Started Started with docker id 56dddb66bf60

Fifth line of the output says the node’s IP is 10.245.1.4. This would be used to access the Web Console later.

The last line in this output shows that the pod is now ready. Checking the status of the pod again shows:

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

./kubernetes/cluster/kubectl.sh get po

NAME READY STATUS RESTARTS AGE

couchbase-tzdhl 1/1 Running 0 2m

Couchbase Web Console on Kubernetes Cluster

Now that your Couchbase container is running in Kubernetes cluster, you may like to view the Web Console.

Each pod is assigned a unique IP address, but this address is only accessible within the cluster. It can exposed using the kubectl expose command.

This command takes a Replication Controller, Service or Pod and expose it as new Kubernetes Service. This can be done by giving the command:

./cluster/kubectl.sh expose rc couchbase --target-port=8091 --port=8091 --external-ip=10.245.1.4
service "couchbase" exposed

./cluster/kubectl.sh expose rc couchbase --target-port=8091 --port=8091 --external-ip=10.245.1.4

service "couchbase" exposed

In this command:

--target-port is the name or number for the port on the container that the service should direct traffic to
--port is the port that the service should serve on
--external-ip is the external IP address to set for the service. Note, this IP address was obtained with kubectl describe pod command earlier.

Now, you can access the Couchbase Web Console at http://10.245.1.4:8091 and looks like:

Enter the password credentials as Administrator/password. These credentials are specified during Docker image creation at github.com/arun-gupta/docker-images/blob/master/couchbase/configure-cluster.sh#L9.

Voila!

Discuss with us at StackOverflow or Couchbase Forums. You can also follow us at @couchbasedev and @couchbase.

Source: http://blog.couchbase.com/2016/couchbase-on-kubernetes

Couchbase Cloud Recipes – Pick your favorite!

January 1, 2016couchbaseamazon, azure, bigstep, couchbase, digitalocean, docker, jelastic, joyent, kubernetes, openshift, vagrantarungupta

Couchbase 4.x Quick Installation provide instructions to install Couchbase on your local machine.

Would you like to run Couchbase 4.x in cloud? There are plenty of recipes available!

Looking for detailed instructions on Couchbase Cloud Recipes?

Digital Ocean
Jelastic
OpenShift
Docker
BigStep
Vagrant
Kubernetes
Joyent Triton
Amazon Web Services
Microsoft Azure
CoreOS and Kubernetes

Read more about it in Couchbase Cloud Deployments. Are there any other cloud/hosting solution where you you would like to see Couchbase running? Did I miss one where Couchbase already runs?

How is your experience of running Couchbase in the cloud?

Couchbase partners provide a complete list of partners.

As always, talk to us using StackOverflow or Forums.

Couchbase on OpenShift 3

December 20, 2015containers, couchbase, redhatcouchbase, docker, kubernetes, openshiftarungupta

OpenShift is Red Hat’s open source PaaS platform. OpenShift 3 provides a holistic experience of running your applications using Docker and Kubernetes. In a classic Red Hat way, all the work is done in the open source at OpenShift Origin. This also drives the next major release of OpenShift Online and OpenShift Enterprise.

OpenShift 3 using Docker and Kubernetes for container orchestration makes it really simple to bring any products that have a Docker image to run with minimal effort. This blog explains how to get started with Couchbase on OpenShift 3.

Getting Started with OpenShift 3

Download the latest Vagrant box (1.1 as of this writing) and Vagrantfile from: openshift.org/vm/. Copy them in the same directory.Vagrantfile is configured for 2GB memory and can be updated if you need to run more containers. OpenShift Master, Node, Docker Registry, and other components run inside the VM.This blog was written using Vagrant 1.7.4 and VirtualBox 5.0.10r104061.

Add the Vagrant Box:

vagrant box add --name openshift3 openshift-bootstrap-1.1.box 
==> box: Box file was not detected as metadata. Adding it directly...
==> box: Adding box 'openshift3' (v0) for provider: 
    box: Unpacking necessary files from: file:///Users/arungupta/tools/openshiftv3/1.1/openshift-bootstrap-1.1.box
==> box: Successfully added box 'openshift3' (v0) for 'virtualbox'!

vagrant box add --name openshift3 openshift-bootstrap-1.1.box

==> box: Box file was not detected as metadata. Adding it directly...

==> box: Adding box 'openshift3' (v0) for provider:

box: Unpacking necessary files from: file:///Users/arungupta/tools/openshiftv3/1.1/openshift-bootstrap-1.1.box

==> box: Successfully added box 'openshift3' (v0) for 'virtualbox'!

Start the Virtual Machine:

vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Setting the name of the VM: openshift3
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 80 => 1080 (adapter 1)
    default: 443 => 1443 (adapter 1)
    default: 5000 => 5000 (adapter 1)
    default: 8080 => 8080 (adapter 1)
    default: 8443 => 8443 (adapter 1)
    default: 22 => 2222 (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Connection timeout. Retrying...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
    default: The guest additions on this VM do not match the installed version of
    default: VirtualBox! In most cases this is fine, but in rare cases it can
    default: prevent things such as shared folders from working properly. If you see
    default: shared folder errors, please make sure the guest additions within the
    default: virtual machine match the version of VirtualBox you have installed on
    default: your host and reload your VM.
    default: 
    default: Guest Additions Version: 4.3.20
    default: VirtualBox Version: 5.0

vagrant up

Bringing machine 'default' up with 'virtualbox' provider...

==> default: Setting the name of the VM: openshift3

==> default: Clearing any previously set network interfaces...

==> default: Preparing network interfaces based on configuration...

default: Adapter 1: nat

==> default: Forwarding ports...

default: 80 => 1080 (adapter 1)

default: 443 => 1443 (adapter 1)

default: 5000 => 5000 (adapter 1)

default: 8080 => 8080 (adapter 1)

default: 8443 => 8443 (adapter 1)

default: 22 => 2222 (adapter 1)

==> default: Running 'pre-boot' VM customizations...

==> default: Booting VM...

==> default: Waiting for machine to boot. This may take a few minutes...

default: SSH address: 127.0.0.1:2222

default: SSH username: vagrant

default: SSH auth method: private key

default: Warning: Connection timeout. Retrying...

==> default: Machine booted and ready!

==> default: Checking for guest additions in VM...

default: The guest additions on this VM do not match the installed version of

default: VirtualBox! In most cases this is fine, but in rare cases it can

default: prevent things such as shared folders from working properly. If you see

default: shared folder errors, please make sure the guest additions within the

default: virtual machine match the version of VirtualBox you have installed on

default: your host and reload your VM.

default:

default: Guest Additions Version: 4.3.20

default: VirtualBox Version: 5.0

Download and Configure OpenShift 3 Client

Download Mac 64-bit client tools (gem install rhc is for v2 only) from openshift.org/vm/ and extract them a in directory. The listing looks like:

tar xzvf ~/Downloads/openshift-origin-v1.1-ac7a99a-darwin-amd64.tar.gz 
x ./
x ./oadm
x ./kube-scheduler
x ./kubelet
x ./kube-apiserver
x ./openshift
x ./kube-controller-manager
x ./kube-proxy
x ./oc
x ./kubectl

tar xzvf ~/Downloads/openshift-origin-v1.1-ac7a99a-darwin-amd64.tar.gz

x ./

x ./oadm

x ./kube-scheduler

x ./kubelet

x ./kube-apiserver

x ./openshift

x ./kube-controller-manager

x ./kube-proxy

x ./oc

x ./kubectl

Verify the client version:

./oc version
oc v1.1
kubernetes v1.1.0-origin-1107-g4c8e6f4

./oc version

oc v1.1

kubernetes v1.1.0-origin-1107-g4c8e6f4

Remove ~/.kube/configor rename to something else.

./oc login
Server [https://localhost:8443]: 
The server uses a certificate signed by an unknown authority.
You can bypass the certificate check, but any data you send to the server could be intercepted by others.
Use insecure connections? (y/n): y

Authentication required for https://localhost:8443 (openshift)
Username: admin
Password: 
Login successful.

You have access to the following projects and can switch between them with 'oc project <projectname>':

  * default (current)
  * openshift
  * turbo

Using project "default".
Welcome! See 'oc help' to get started.

./oc login

Server [https://localhost:8443]:

The server uses a certificate signed by an unknown authority.

You can bypass the certificate check, but any data you send to the server could be intercepted by others.

Use insecure connections? (y/n): y

Authentication required for https://localhost:8443 (openshift)

Username: admin

Password:

You have access to the following projects and can switch between them with 'oc project <projectname>':

* default (current)

* openshift

* turbo

Using project "default".

Welcome! See 'oc help' to get started.

Create Couchbase Application in OpenShift 3

Create a new Couchbase instance:

./oc new-app arungupta/couchbase
--> Found Docker image 9131c5a (2 days old) from Docker Hub for "arungupta/couchbase"
    * An image stream will be created as "couchbase:latest" that will track this image
    * This image will be deployed in deployment config "couchbase"
    * Ports 11207/tcp, 11210/tcp, 11211/tcp, 18091/tcp, 18092/tcp, 8091/tcp, 8092/tcp, 8093/tcp will be load balanced by service "couchbase"
--> Creating resources with label app=couchbase ...
    ImageStream "couchbase" created
    DeploymentConfig "couchbase" created
    Service "couchbase" created
--> Success
    Run 'oc status' to view your app.

./oc new-app arungupta/couchbase

--> Found Docker image 9131c5a (2 days old) from Docker Hub for "arungupta/couchbase"

* An image stream will be created as "couchbase:latest" that will track this image

* This image will be deployed in deployment config "couchbase"

* Ports 11207/tcp, 11210/tcp, 11211/tcp, 18091/tcp, 18092/tcp, 8091/tcp, 8092/tcp, 8093/tcp will be load balanced by service "couchbase"

--> Creating resources with label app=couchbase ...

ImageStream "couchbase" created

DeploymentConfig "couchbase" created

Service "couchbase" created

--> Success

Run 'oc status' to view your app.

arungupta/couchbase is used as it uses Couchbase REST API to preconfigure the Couchbase server with:

Memory and index quota
Query, Data, and Index service
Username and password credentials
Install travel-sample bucket

This sample bucket will be used later for querying data.

Check the status of deployment:

./oc status
In project default on server https://localhost:8443

svc/couchbase - 172.30.84.134 ports 8091, 8092, 8093, 11207, 11210, 11211, 18091, 18092
  dc/couchbase deploys imagestreamtag/couchbase:latest 
    #1 deployed about a minute ago - 1 pod

svc/docker-registry - 172.30.236.154:5000
  dc/docker-registry deploys docker.io/openshift/origin-docker-registry:v1.1 
    #1 deployed 4 weeks ago - 1 pod

svc/kubernetes - 172.30.0.1 ports 443, 53, 53

svc/router - 172.30.233.69:80
  dc/router deploys docker.io/openshift/origin-haproxy-router:v1.1 
    #1 deployed 4 weeks ago - 1 pod

Warnings:
  * container "registry" in pod/docker-registry-1-imxqp has restarted 5 times
  * container "openshift-registry-proxy-1" in pod/openshift-registry-proxy has restarted 3 times
  * container "router" in pod/router-1-5grim has restarted 5 times

To see more, use 'oc describe <resource>/<name>'.
You can use 'oc get all' to see a list of other objects.

./oc status

In project default on server https://localhost:8443

svc/couchbase - 172.30.84.134 ports 8091, 8092, 8093, 11207, 11210, 11211, 18091, 18092

dc/couchbase deploys imagestreamtag/couchbase:latest

#1 deployed about a minute ago - 1 pod

svc/docker-registry - 172.30.236.154:5000

dc/docker-registry deploys docker.io/openshift/origin-docker-registry:v1.1

#1 deployed 4 weeks ago - 1 pod

svc/kubernetes - 172.30.0.1 ports 443, 53, 53

svc/router - 172.30.233.69:80

dc/router deploys docker.io/openshift/origin-haproxy-router:v1.1

#1 deployed 4 weeks ago - 1 pod

Warnings:

* container "registry" in pod/docker-registry-1-imxqp has restarted 5 times

* container "openshift-registry-proxy-1" in pod/openshift-registry-proxy has restarted 3 times

* container "router" in pod/router-1-5grim has restarted 5 times

To see more, use 'oc describe <resource>/<name>'.

You can use 'oc get all' to see a list of other objects.

Find the list of Pods:

client > ./oc get po
NAME                       READY     STATUS    RESTARTS   AGE
couchbase-1-5zhju          1/1       Running   0          1d
docker-registry-1-imxqp    1/1       Running   5          32d
openshift-registry-proxy   1/1       Running   3          32d
router-1-5grim             1/1       Running   5          32d

client > ./oc get po

NAME READY STATUS RESTARTS AGE

couchbase-1-5zhju 1/1 Running 0 1d

docker-registry-1-imxqp 1/1 Running 5 32d

openshift-registry-proxy 1/1 Running 3 32d

router-1-5grim 1/1 Running 5 32d

Get more details about the Couchbase pod:

./oc describe po couchbase-1-5zhju
Name:                           couchbase-1-5zhju
Namespace:                      default
Image(s):                       arungupta/couchbase@sha256:9131c5a283d79e11b6556c94b0b0f8ceba7daf5ba5982bac850100099019959f
Node:                           localhost.localdomain/10.0.2.15
Start Time:                     Sat, 19 Dec 2015 08:19:31 -0800
Labels:                         app=couchbase,deployment=couchbase-1,deploymentconfig=couchbase
Status:                         Running
Reason:                         
Message:                        
IP:                             172.17.0.7
Replication Controllers:        couchbase-1 (1/1 replicas created)
Containers:
  couchbase:
    Container ID:       docker://bd51f655c2a54f92f4634b84f455ca91642a88b925be39126f07df43ce883a33
    Image:              arungupta/couchbase@sha256:9131c5a283d79e11b6556c94b0b0f8ceba7daf5ba5982bac850100099019959f
    Image ID:           docker://c9d204bb75427500ef94263f8f53e8b78f2e56efd37543e620aebb1bc1bd7de1
    QoS Tier:
      cpu:              BestEffort
      memory:           BestEffort
    State:              Running
      Started:          Sat, 19 Dec 2015 08:20:21 -0800
    Ready:              True
    Restart Count:      0
    Environment Variables:
Conditions:
  Type          Status
  Ready         True 
Volumes:
  couchbase-volume-1:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:     
  default-token-cycb6:
    Type:       Secret (a secret that should populate this volume)
    SecretName: default-token-cycb6
No events.

./oc describe po couchbase-1-5zhju

Name: couchbase-1-5zhju

Namespace: default

Image(s): arungupta/couchbase@sha256:9131c5a283d79e11b6556c94b0b0f8ceba7daf5ba5982bac850100099019959f

Node: localhost.localdomain/10.0.2.15

Start Time: Sat, 19 Dec 2015 08:19:31 -0800

Labels: app=couchbase,deployment=couchbase-1,deploymentconfig=couchbase

Status: Running

Reason:

Message:

IP: 172.17.0.7

Replication Controllers: couchbase-1 (1/1 replicas created)

Containers:

couchbase:

Container ID: docker://bd51f655c2a54f92f4634b84f455ca91642a88b925be39126f07df43ce883a33

Image: arungupta/couchbase@sha256:9131c5a283d79e11b6556c94b0b0f8ceba7daf5ba5982bac850100099019959f

Image ID: docker://c9d204bb75427500ef94263f8f53e8b78f2e56efd37543e620aebb1bc1bd7de1

QoS Tier:

cpu: BestEffort

memory: BestEffort

State: Running

Started: Sat, 19 Dec 2015 08:20:21 -0800

Ready: True

Restart Count: 0

Environment Variables:

Conditions:

Type Status

Ready True

Volumes:

couchbase-volume-1:

Type: EmptyDir (a temporary directory that shares a pod's lifetime)

Medium:

default-token-cycb6:

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

SecretName: default-token-cycb6

No events.

Query Couchbase Sample Bucket

Log into the Vagrant box:

vagrant ssh
Last login: Wed Nov 18 18:04:32 2015 from 10.0.2.2
[vagrant@localhost ~]$

vagrant ssh

Last login: Wed Nov 18 18:04:32 2015 from 10.0.2.2

[vagrant@localhost ~]$

Find a list of all the running containers:

[vagrant@localhost ~]$ docker ps
CONTAINER ID        IMAGE                                                                                                                  COMMAND                  CREATED             STATUS              PORTS                    NAMES
bd51f655c2a5        arungupta/couchbase@sha256:9131c5a283d79e11b6556c94b0b0f8ceba7daf5ba5982bac850100099019959f                            "/entrypoint.sh /opt/"   7 minutes ago       Up 7 minutes                                 k8s_couchbase.f96da262_couchbase-1-5zhju_default_48e953db-a66c-11e5-8a75-080027c5bfa9_31dbcfec
8e5ef3e54d4e        openshift/origin-pod:v1.1                                                                                              "/pod"                   8 minutes ago       Up 8 minutes                                 k8s_POD.d7dfee57_couchbase-1-5zhju_default_48e953db-a66c-11e5-8a75-080027c5bfa9_b1bcd72d
0f7807f389d9        openshift/mysql-55-centos7:latest                                                                                      "container-entrypoint"   15 minutes ago      Up 15 minutes                                k8s_ruby-helloworld-database.448eeefe_database-1-w51ix_turbo_91adac2f-8d66-11e5-bf15-080027c5bfa9_74ecdc59
077a078e00a3        172.30.236.154:5000/turbo/origin-ruby-sample@sha256:c4ed12ec9817fca1fb41a5eb0c66f2edccf2e7375128fd6d64f7180207262193   "container-entrypoint"   16 minutes ago      Up 16 minutes                                k8s_ruby-helloworld.88353f9f_frontend-2-1lm99_turbo_42a6dd40-8d67-11e5-bf15-080027c5bfa9_d5110e41
e2105f2f4ab6        openshift/origin-haproxy-router:v1.1                                                                                   "/usr/bin/openshift-r"   16 minutes ago      Up 16 minutes                                k8s_router.c3a638e8_router-1-5grim_default_cac8c2d2-8d63-11e5-b835-080027c5bfa9_9d49a633
b98052109d08        172.30.236.154:5000/turbo/origin-ruby-sample@sha256:c4ed12ec9817fca1fb41a5eb0c66f2edccf2e7375128fd6d64f7180207262193   "container-entrypoint"   16 minutes ago      Up 16 minutes                                k8s_ruby-helloworld.88353f9f_frontend-2-hdz43_turbo_46657993-8d67-11e5-bf15-080027c5bfa9_f6394539
646dcce91f59        openshift/origin-docker-registry:v1.1                                                                                  "/bin/sh -c 'REGISTRY"   16 minutes ago      Up 16 minutes                                k8s_registry.35eb136e_docker-registry-1-imxqp_default_cb3dde6e-8d63-11e5-b835-080027c5bfa9_71586c07
d02c8c07f690        openshift/origin-registry-proxy                                                                                        "sh -cx '/bin/tcppm -"   16 minutes ago      Up 16 minutes                                k8s_openshift-registry-proxy-1.a0457375_openshift-registry-proxy_default_767fcb12-8d64-11e5-bf15-080027c5bfa9_4c413a10
23267082944f        openshift/origin-pod:v1.1                                                                                              "/pod"                   17 minutes ago      Up 16 minutes                                k8s_POD.d982fd5f_database-1-w51ix_turbo_91adac2f-8d66-11e5-bf15-080027c5bfa9_8fc2969f
bd7f82a88cb1        openshift/origin-pod:v1.1                                                                                              "/pod"                   17 minutes ago      Up 16 minutes                                k8s_POD.e127fd63_frontend-2-1lm99_turbo_42a6dd40-8d67-11e5-bf15-080027c5bfa9_3f73ddf8
d2ca01d75a0c        openshift/origin-pod:v1.1                                                                                              "/pod"                   17 minutes ago      Up 16 minutes                                k8s_POD.4d0ddc3f_router-1-5grim_default_cac8c2d2-8d63-11e5-b835-080027c5bfa9_036343da
5e25f5ba5c4c        openshift/origin-pod:v1.1                                                                                              "/pod"                   17 minutes ago      Up 16 minutes                                k8s_POD.e127fd63_frontend-2-hdz43_turbo_46657993-8d67-11e5-bf15-080027c5bfa9_122e502e
7c4b2b9e6c39        openshift/origin-pod:v1.1                                                                                              "/pod"                   17 minutes ago      Up 16 minutes                                k8s_POD.cc3ffd58_docker-registry-1-imxqp_default_cb3dde6e-8d63-11e5-b835-080027c5bfa9_0ae24ed7
85c4cf8d0808        openshift/origin-pod:v1.1                                                                                              "/pod"                   17 minutes ago      Up 16 minutes       0.0.0.0:5000->5000/tcp   k8s_POD.c686fded_openshift-registry-proxy_default_767fcb12-8d64-11e5-bf15-080027c5bfa9_04225f94

[vagrant@localhost ~]$ docker ps

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

bd51f655c2a5 arungupta/couchbase@sha256:9131c5a283d79e11b6556c94b0b0f8ceba7daf5ba5982bac850100099019959f "/entrypoint.sh /opt/" 7 minutes ago Up 7 minutes k8s_couchbase.f96da262_couchbase-1-5zhju_default_48e953db-a66c-11e5-8a75-080027c5bfa9_31dbcfec

8e5ef3e54d4e openshift/origin-pod:v1.1 "/pod" 8 minutes ago Up 8 minutes k8s_POD.d7dfee57_couchbase-1-5zhju_default_48e953db-a66c-11e5-8a75-080027c5bfa9_b1bcd72d

0f7807f389d9 openshift/mysql-55-centos7:latest "container-entrypoint" 15 minutes ago Up 15 minutes k8s_ruby-helloworld-database.448eeefe_database-1-w51ix_turbo_91adac2f-8d66-11e5-bf15-080027c5bfa9_74ecdc59

077a078e00a3 172.30.236.154:5000/turbo/origin-ruby-sample@sha256:c4ed12ec9817fca1fb41a5eb0c66f2edccf2e7375128fd6d64f7180207262193 "container-entrypoint" 16 minutes ago Up 16 minutes k8s_ruby-helloworld.88353f9f_frontend-2-1lm99_turbo_42a6dd40-8d67-11e5-bf15-080027c5bfa9_d5110e41

e2105f2f4ab6 openshift/origin-haproxy-router:v1.1 "/usr/bin/openshift-r" 16 minutes ago Up 16 minutes k8s_router.c3a638e8_router-1-5grim_default_cac8c2d2-8d63-11e5-b835-080027c5bfa9_9d49a633

b98052109d08 172.30.236.154:5000/turbo/origin-ruby-sample@sha256:c4ed12ec9817fca1fb41a5eb0c66f2edccf2e7375128fd6d64f7180207262193 "container-entrypoint" 16 minutes ago Up 16 minutes k8s_ruby-helloworld.88353f9f_frontend-2-hdz43_turbo_46657993-8d67-11e5-bf15-080027c5bfa9_f6394539

646dcce91f59 openshift/origin-docker-registry:v1.1 "/bin/sh -c 'REGISTRY" 16 minutes ago Up 16 minutes k8s_registry.35eb136e_docker-registry-1-imxqp_default_cb3dde6e-8d63-11e5-b835-080027c5bfa9_71586c07

d02c8c07f690 openshift/origin-registry-proxy "sh -cx '/bin/tcppm -" 16 minutes ago Up 16 minutes k8s_openshift-registry-proxy-1.a0457375_openshift-registry-proxy_default_767fcb12-8d64-11e5-bf15-080027c5bfa9_4c413a10

23267082944f openshift/origin-pod:v1.1 "/pod" 17 minutes ago Up 16 minutes k8s_POD.d982fd5f_database-1-w51ix_turbo_91adac2f-8d66-11e5-bf15-080027c5bfa9_8fc2969f

bd7f82a88cb1 openshift/origin-pod:v1.1 "/pod" 17 minutes ago Up 16 minutes k8s_POD.e127fd63_frontend-2-1lm99_turbo_42a6dd40-8d67-11e5-bf15-080027c5bfa9_3f73ddf8

d2ca01d75a0c openshift/origin-pod:v1.1 "/pod" 17 minutes ago Up 16 minutes k8s_POD.4d0ddc3f_router-1-5grim_default_cac8c2d2-8d63-11e5-b835-080027c5bfa9_036343da

5e25f5ba5c4c openshift/origin-pod:v1.1 "/pod" 17 minutes ago Up 16 minutes k8s_POD.e127fd63_frontend-2-hdz43_turbo_46657993-8d67-11e5-bf15-080027c5bfa9_122e502e

7c4b2b9e6c39 openshift/origin-pod:v1.1 "/pod" 17 minutes ago Up 16 minutes k8s_POD.cc3ffd58_docker-registry-1-imxqp_default_cb3dde6e-8d63-11e5-b835-080027c5bfa9_0ae24ed7

85c4cf8d0808 openshift/origin-pod:v1.1 "/pod" 17 minutes ago Up 16 minutes 0.0.0.0:5000->5000/tcp k8s_POD.c686fded_openshift-registry-proxy_default_767fcb12-8d64-11e5-bf15-080027c5bfa9_04225f94

Search for Couchbase container:

[vagrant@localhost ~]$ docker ps | grep couchbase
CONTAINER ID        IMAGE                                                                                                                  COMMAND                  CREATED             STATUS              PORTS                    NAMES
bd51f655c2a5        arungupta/couchbase@sha256:9131c5a283d79e11b6556c94b0b0f8ceba7daf5ba5982bac850100099019959f                            "/entrypoint.sh /opt/"   7 minutes ago       Up 7 minutes                                 k8s_couchbase.f96da262_couchbase-1-5zhju_default_48e953db-a66c-11e5-8a75-080027c5bfa9_31dbcfec
8e5ef3e54d4e        openshift/origin-pod:v1.1                                                                                              "/pod"                   8 minutes ago       Up 8 minutes                                 k8s_POD.d7dfee57_couchbase-1-5zhju_default_48e953db-a66c-11e5-8a75-080027c5bfa9_b1bcd72d
0f7807f389d9        openshift/mysql-55-centos7:latest                                                                                      "container-entrypoint"   15 minutes ago      Up 15 minutes

[vagrant@localhost ~]$ docker ps | grep couchbase

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

8e5ef3e54d4e openshift/origin-pod:v1.1 "/pod" 8 minutes ago Up 8 minutes k8s_POD.d7dfee57_couchbase-1-5zhju_default_48e953db-a66c-11e5-8a75-080027c5bfa9_b1bcd72d

0f7807f389d9 openshift/mysql-55-centos7:latest "container-entrypoint" 15 minutes ago Up 15 minutes

Get the id for our container:

docker ps | grep arungupta/couchbase | awk '{ print $1}'
bd51f655c2a5

docker ps | grep arungupta/couchbase | awk '{ print $1}'

bd51f655c2a5

Get IP address of the Pod where Couchbase server is running:

[vagrant@localhost ~]$ docker inspect --format '{{ index .Config.Env 6 }}' `docker ps | grep arungupta/couchbase | awk '{ print $1}'`
COUCHBASE_SERVICE_HOST=172.30.84.134

[vagrant@localhost ~]$ docker inspect --format '{{ index .Config.Env 6 }}' `docker ps | grep arungupta/couchbase | awk '{ print $1}'`

COUCHBASE_SERVICE_HOST=172.30.84.134

Use the IP address shown above to start Couchbase Query CLI:

[vagrant@localhost ~]$ docker run -it arungupta/couchbase /opt/couchbase/bin/cbq -engine=http://172.30.84.134:8093
Unable to find image 'arungupta/couchbase:latest' locally
Trying to pull repository docker.io/arungupta/couchbase ... latest: Pulling from arungupta/couchbase
62baed0d0de5: Already exists 
39387babd60f: Already exists 
6a2bc8404be0: Already exists 
bad926a6fb50: Already exists 
1a86c4c907e0: Already exists 
32132a7c82e9: Already exists 
646c3d5ebb71: Already exists 
864cbabd77ad: Already exists 
8c327c6d4e43: Already exists 
8592c697ab61: Already exists 
7734f4a832d4: Already exists 
35edb38ebc17: Already exists 
99f3eb6fb46f: Already exists 
91e5fad693c2: Already exists 
0cb81f5cc79b: Already exists 
ec58df60a109: Already exists 
c9d204bb7542: Already exists 
Digest: sha256:9131c5a283d79e11b6556c94b0b0f8ceba7daf5ba5982bac850100099019959f
Status: Downloaded newer image for docker.io/arungupta/couchbase:latest

Couchbase query shell connected to http://172.30.84.134:8093/ . Type Ctrl-D to exit.
cbq>

[vagrant@localhost ~]$ docker run -it arungupta/couchbase /opt/couchbase/bin/cbq -engine=http://172.30.84.134:8093

Unable to find image 'arungupta/couchbase:latest' locally

Trying to pull repository docker.io/arungupta/couchbase ... latest: Pulling from arungupta/couchbase

62baed0d0de5: Already exists

39387babd60f: Already exists

6a2bc8404be0: Already exists

bad926a6fb50: Already exists

1a86c4c907e0: Already exists

32132a7c82e9: Already exists

646c3d5ebb71: Already exists

864cbabd77ad: Already exists

8c327c6d4e43: Already exists

8592c697ab61: Already exists

7734f4a832d4: Already exists

35edb38ebc17: Already exists

99f3eb6fb46f: Already exists

91e5fad693c2: Already exists

0cb81f5cc79b: Already exists

ec58df60a109: Already exists

c9d204bb7542: Already exists

Digest: sha256:9131c5a283d79e11b6556c94b0b0f8ceba7daf5ba5982bac850100099019959f

Status: Downloaded newer image for docker.io/arungupta/couchbase:latest

Couchbase query shell connected to http://172.30.84.134:8093/ . Type Ctrl-D to exit.

cbq>

Query the sample bucket:

cbq> select * from `travel-sample` limit 1;
{
    "requestID": "a7bd414a-c571-4b22-8c81-30512b87730d",
    "signature": {
        "*": "*"
    },
    "results": [
        {
            "travel-sample": {
                "callsign": "MILE-AIR",
                "country": "United States",
                "iata": "Q5",
                "icao": "MLA",
                "id": 10,
                "name": "40-Mile Air",
                "type": "airline"
            }
        }
    ],
    "status": "success",
    "metrics": {
        "elapsedTime": "123.799956ms",
        "executionTime": "116.882044ms",
        "resultCount": 1,
        "resultSize": 300
    }
}

cbq> select * from `travel-sample` limit 1;

{

"requestID": "a7bd414a-c571-4b22-8c81-30512b87730d",

"signature": {

"*": "*"

"results": [

{

"travel-sample": {

"callsign": "MILE-AIR",

"country": "United States",

"iata": "Q5",

"icao": "MLA",

"id": 10,

"name": "40-Mile Air",

"type": "airline"

}

"status": "success",

"metrics": {

"elapsedTime": "123.799956ms",

"executionTime": "116.882044ms",

"resultCount": 1,

"resultSize": 300

}

Enjoy!

This blog shows the very basics of getting started with Couchbase on OpenShift 3. Future blogs will show:

How to deploy an application to OpenShift and use this Couchbase
How to make this application accessible outside OpenShift
How to scale Couchbase in OpenShift
Possibly some other interesting items that come along

Do you have a suggestion on what you’d like to see?

Docker, Kubernetes, and Microservices Replay from Devoxx 2015

November 12, 2015conferences, containers, microservicesdevoxx, docker, kubernetes, microservicesarungupta

Devoxx 2015 BE Arun

Java gives us Write Once Run Anywhere (WORA) because of the common abstraction provided by Java Virtual Machine. The binary byte code produced by Java is understood by the JVM running on multiple operating systems. This allows Java code to run on any operating system. But deploying such applications typically requires to tune the JVM, setup application server, install appropriate database drivers, other similar configuration. Docker nicely complements WORA by defining a way to package Java applications, and include all the configuration in a an easy to describe format. This can be called as Package Once Deploy Anywhere, or PODA.

Do you want to learn more about how Docker helps with PODA?
How do you create multi-container applications using Docker Compose?
How do you deploy this multi-container application on multiple hosts running in a Docker Swarm cluster?
What new features Docker introduced in 1.9 release – particularly multi-host networking and persistent storage?
How do you deploy Docker containers using Kubernetes?
How does Kubernetes help with scaling applications?
How does Docker Swarm compare with Kubernetes?

I had the privilege of delivering a 3-hour university on Docker and Kubernetes followed by a 3-hour hands-on lab. The replay of the university session is now available:

Slides for the university are available at: github.com/javaee-samples/docker-java/tree/master/slides

The contents from the hands-on lab are available at bit.ly/dockerlab.

In addition, I also gave a 3-hour university on Refactor your Java EE Applications using Microservices and Containers. This session explained:

Basic characteristics of Microservices
Showed a simple shopping cart monolithic application, and how it was refactored to multiple microservices (github.com/arun-gupta/microservices)
Talked about transactions, event sourcing and CQRS
How KumuluzEE was used to create standalone JARs
Explained how such microservices can be deployed using Docker

Slides from this session are available at: github.com/arun-gupta/microservices/tree/master/slides

Replay is available at:

The response on twitter was quite positive:

Almost packed room 20 mins before #Docker #Kubernetes workshop at #Devoxx pic.twitter.com/LVuK1cLuHR

— Arun Gupta (@arungupta) November 9, 2015

Top 3 talks so far, with lots of votes, Venkat Subramaniam. Talk about a super star speaker! #Devoxx

— Frédéric Donckels (@forgotten_pass) November 11, 2015

Enjoyed the 2 university days #Devoxx so far, specialy @venkat_s and @arungupta great talks

— Marc…Aurèle…ius (@marcaurele) November 10, 2015

@arungupta talks about microservices on #Devoxx – best talk so far👍👍👍

— Henrik Thorsted (@elbartdk) November 10, 2015

Full quote @arungupta: #Kubernetes can't exist w/o #Docker just like #Spring cannot w/o (parts of) #JavaEE. #Devoxx https://t.co/2LjBo2cZVI

— Vladimir Pavlov (@vladopavlov) November 9, 2015

#docker hands on lab very popular #devoxx @arungupta – checkout the material at https://t.co/u0dDI7AYUR pic.twitter.com/dEsBsYESI1

— Stijn Van den Enden (@stieno) November 9, 2015

Very good overview #docker #kubernetes at #devoxx @arungupta https://t.co/hNSbj9LDrJ

— Sascha (@sam6_de) November 9, 2015

sweet intro into Kubernetes by @arungupta and very useful session in general! #Devoxx #DevoxxBE pic.twitter.com/X8GR4PYZMz

— Vladimir Tsukur (@flushdia) November 9, 2015

@arungupta always the best!! pic.twitter.com/RMO4TWGpGy

— fiorenzo pizza (@fiorenzino) November 9, 2015

And in case you are interested, watch a quick interview with Voxxed team:

Enjoy!

Kubernetes Application – Package Multiple Resources Together

August 18, 2015containers, javaee, techtipcontainers, docker, javaee, kubernetes, mysql, wildflyarungupta

Deploying an application in Kubernetes require to create multiple resources such as Pods, Services, Replication Controllers, and others. Typically each resource is define in a configuration file and created using kubectl script. But if multiple resources need to be created then you need to invoke kubectl multiple times. So if you need to create the following resources:

MySQL Pod
MySQL Service
WildFly Replication Controller

Then the commands would look like:

kubectl.sh create -f ~/workspaces/kubernetes-java-sample/app-mysql-pod.yaml
kubectl.sh create -f ~/workspaces/kubernetes-java-sample/app-mysql-service.yaml
kubectl.sh create -f ~/workspaces/kubernetes-java-sample/app-wildfly-rc.yaml

kubectl.sh create -f ~/workspaces/kubernetes-java-sample/app-mysql-pod.yaml

kubectl.sh create -f ~/workspaces/kubernetes-java-sample/app-mysql-service.yaml

kubectl.sh create -f ~/workspaces/kubernetes-java-sample/app-wildfly-rc.yaml

Or for convenience, wrap these invocations in a shell script. But that is not very intuitive! There is a better, and more natural and intuitive way.

Kubernetes allow multiple resources to be specified in a single configuration file. This allows to create a “Kubernetes Application” that can consists of multiple resources easily.

Previous section showed how to deploy the Java EE application using multiple configuration files. This application can be delpoyed using a single configuration file as well.

An application, as discussed above, consisting of MySQL Pod, MySQL Service, and WildFly Replication Controller can be created using the following configuration file:

apiVersion: v1
kind: Pod
metadata:
  name: mysql-pod
  labels:
    name: mysql-pod
    context: docker-k8s-lab
spec:
  containers:
    -
      name: mysql
      image: mysql:latest
      env:
        -
          name: "MYSQL_USER"
          value: "mysql"
        -
          name: "MYSQL_PASSWORD"
          value: "mysql"
        -
          name: "MYSQL_DATABASE"
          value: "sample"
        -
          name: "MYSQL_ROOT_PASSWORD"
          value: "supersecret"
      ports:
        -
          containerPort: 3306
----
apiVersion: v1
kind: Service
metadata:
  name: mysql-service
  labels:
    name: mysql-pod
    context: docker-k8s-lab
spec:
  ports:
    # the port that this service should serve on
    - port: 3306
  # label keys and values that must match in order to receive traffic for this service
  selector:
    name: mysql-pod
    context: docker-k8s-lab
----
apiVersion: v1
kind: ReplicationController
metadata:
  name: wildfly-rc
  labels:
    name: wildfly
    context: docker-k8s-lab
spec:
  replicas: 1
  template:
    metadata:
      labels:
        name: wildfly
    spec:
      containers:
      - name: wildfly-rc-pod
        image: arungupta/wildfly-mysql-javaee7:k8s
        ports:
        - containerPort: 8080

apiVersion: v1

kind: Pod

metadata:

labels:

context: docker-k8s-lab

spec:

containers:

image: mysql:latest

env:

value: "mysql"

value: "mysql"

value: "sample"

value: "supersecret"

ports:

containerPort: 3306

----

apiVersion: v1

kind: Service

metadata:

labels:

context: docker-k8s-lab

spec:

ports:

# the port that this service should serve on

- port: 3306

# label keys and values that must match in order to receive traffic for this service

selector:

context: docker-k8s-lab

----

apiVersion: v1

kind: ReplicationController

metadata:

labels:

context: docker-k8s-lab

spec:

replicas: 1

template:

metadata:

labels:

spec:

containers:

- name: wildfly-rc-pod

image: arungupta/wildfly-mysql-javaee7:k8s

ports:

- containerPort: 8080

Notice that each section, one each for MySQL Pod, MySQL Service, and WildFly Replication Controller, is separated by ----.

Such an application can be created as:

kubectl.sh create -f ~/workspaces/kubernetes-java-sample/app.yaml
pods/mysql-pod
services/mysql-service
replicationcontrollers/wildfly-rc

kubectl.sh create -f ~/workspaces/kubernetes-java-sample/app.yaml

pods/mysql-pod

services/mysql-service

replicationcontrollers/wildfly-rc

Complete details about how to setup Kubernetes and run this application are available at github.com/arun-gupta/kubernetes-java-sample/#kubernetes-application.

More details about creating a Kubernetes application with multiple resources can be found in #12104.

You can learn about how to create Kubernetes resources for a Java application, or otherwise, at github.com/arun-gupta/kubernetes-java-sample/.

Docker and Kubernetes Workshops in Fall 2015

August 14, 2015conferences, containers, java, microservices, redhatdocker, kubernetes, microservicesarungupta

Docker and Kubernetes workshops is going to 4 continents and 9 countries this Fall!

Lets talk about:

Get started with Docker and Kubernetes for packaging your applications
Microservices using Docker and Kubernetes
Clustering architectures
Migrating existing applications to Docker and Kubernetes
Tooling
Debugging tips

I’ll share some of what I know and will learn a lot more from you!

Here is the complete circuit so far:

Sep 9 -10
Sep 15
Sep 17
Sep 29	Red Hat Forums, Argentina
Oct 2
Oct 24 – 29
Nov 5	(tentative)
Nov 7
Nov 9 – 13
Nov 16 – 18
Nov 18 – 22

Where will I see you?

Would you like to run with me at any of these events? 5k, 10k, 10mile, half marathon, marathon … you pick the distance and we run together!

Kubernetes Design Patterns

July 21, 2015containers, microservices, redhatdocker, javaee, kubernetes, wildflyarungupta

14,000 commits and 400 contributors (including one tiny commit from me!) is what build Kubernetes 1.0. It is now available!

Download here
API Docs
Kubectl command tool
Getting Started Guide
Kubernetes Introduction Slides

This blog discusses some of the Kubernetes design patterns. All source code for the design patterns discussed below are available at kubernetes-java-sample.

Key Concepts of Kubernetes

At a very high level, there are three key concepts:

Pods are the smallest deployable units that can be created, scheduled, and managed. Its a logical collection of containers that belong to an application.
Master is the central control point that provides a unified view of the cluster. There is a single master node that control multiple minions.
Node is a worker node that run tasks as delegated by the master. Minions can run one or more pods. It provides an application-specific “virtual host” in a containerized environment.

Some other concepts to be aware of:

Replication Controller is a resource at Master that ensures that requested number of pods are running on nodes at all times.
Service is an object on master that provides load balancing across a replicated group of pods.
Label is an arbitrary key/value pair in a distributed watchable storage that the Replication Controller uses for service discovery.

Start Kubernetes Cluster

Easiest way to start a Kubernetes cluster on a Mac OS is using Vagrant:

export KUBERNETES_PROVIDER=vagrant
curl -sS https://get.k8s.io | bash

export KUBERNETES_PROVIDER=vagrant

curl -sS https://get.k8s.io | bash

Alternatively, Kubernetes can be downloaded from github.com/GoogleCloudPlatform/kubernetes/releases/download/v1.0.0/kubernetes.tar.gz, and cluster can be started as:

cd kubernetes
export KUBERNETES_PROVIDER=vagrant
cluster/kube-up.sh

cd kubernetes

export KUBERNETES_PROVIDER=vagrant

cluster/kube-up.sh

Kubernetes Cluster Vagrant

A Pod with One Container

This section will explain how to start a Pod with one Container. WildFly base Docker image will be used as the Container.

Pod, Replication Controller, Service, etc are all resources in Kubernetes. They can be created using the kubectl by using a configuration file.

The configuration file in this case:

apiVersion: v1
kind: Pod
metadata:
  name: wildfly-pod
  labels: 
    name: wildfly
spec: 
  containers: 
    - image: jboss/wildfly
      name: wildfly-pod
      ports: 
        - containerPort: 8080

apiVersion: v1

kind: Pod

metadata:

labels:

spec:

containers:

- image: jboss/wildfly

ports:

- containerPort: 8080

Complete details on how to create a Pod are explained at github.com/arun-gupta/kubernetes-java-sample#a-pod-with-one-container

Java EE Application Deployed in a Pod with One Container

This section will show how to deploy a Java EE application in a Pod with one Container. WildFly, with an in-memory H2 database, will be used as the container.

Configuration file is:

apiVersion: v1
kind: ReplicationController
metadata:
  name: javaee7-hol
  labels:
    name: javaee7-hol
spec:
  replicas: 1
  selector:
    name: javaee7-hol
  template:
    metadata:
      labels:
        name: javaee7-hol
    spec:
      containers:
      - name: master
        image: arungupta/javaee7-hol
        ports:
        - containerPort: 8080
          hostPort: 8080

apiVersion: v1

kind: ReplicationController

metadata:

labels:

spec:

replicas: 1

selector:

template:

metadata:

labels:

spec:

containers:

- name: master

image: arungupta/javaee7-hol

ports:

- containerPort: 8080

hostPort: 8080

Complete details at github.com/arun-gupta/kubernetes-java-sample#java-ee-application-deployed-in-a-pod-with-one-container-wildfly–h2-in-memory-database.

A Replication Controller with Two Replicas of a Pod

This section will explain how to start a Replication Controller with two replicas of a Pod. Each Pod will have one WildFly container.

Configuration file is:

apiVersion: v1
kind: ReplicationController
metadata:
  name: wildfly-rc
  labels:
    name: wildfly
    context: docker-k8s-lab
spec:
  replicas: 1
  template:
    metadata:
      labels:
        name: wildfly
    spec:
      containers:
      - name: wildfly-rc-pod
        image: arungupta/wildfly-mysql-javaee7:k8s
        ports:
        - containerPort: 8080

apiVersion: v1

kind: ReplicationController

metadata:

labels:

context: docker-k8s-lab

spec:

replicas: 1

template:

metadata:

labels:

spec:

containers:

- name: wildfly-rc-pod

image: arungupta/wildfly-mysql-javaee7:k8s

ports:

- containerPort: 8080

Complete details at github.com/arun-gupta/kubernetes-java-sample#a-replication-controller-with-two-replicas-of-a-pod-wildfly

Rescheduling Pods

Replication Controller ensures that specified number of pod “replicas” are running at any one time. If there are too many, the replication controller kills some pods. If there are too few, it starts more.

Complete details at github.com/arun-gupta/kubernetes-java-sample#rescheduling-pods.

Scaling Pods

Replication Controller allows dynamic scaling up and down of Pods.

Complete details at github.com/arun-gupta/kubernetes-java-sample#scaling-pods.

Kubernetes Service

Pods are ephemeral. IP address assigned to a Pod cannot be relied upon. Kubernetes, Replication Controller in particular, create and destroy Pods dynamically. A consumer Pod cannot rely upon the IP address of a producer Pod.

Kubernetes Service is an abstraction which defines a set of logical Pods. The set of Pods targeted by a Service are determined by labels associated with the Pods.

This section will show how to run a WildFly and MySQL containers in separate Pods. WildFly Pod will talk to the MySQL Pod using a Service.

Complete details at github.com/arun-gupta/kubernetes-java-sample#kubernetes-service.

Here are couple of blogs that will help you get started:

The complete set of Kubernetes blog entries provide more details.

Enjoy!

Scaling Kubernetes Cluster

July 15, 2015containers, redhatclustering, kubernetes, wildflyarungupta

Automatic Restarting of Pods inside Replication Controller of Kubernetes Cluster shows how Kubernetes reschedule pods in the cluster if one or more of existing Pods disappear for some reason. This is a common usage pattern and one of the key features of Kubernetes.

Another common usage pattern of Replication Controller is scaling:

The replication controller makes it easy to scale the number of replicas up or down, either manually or by an auto-scaling control agent, by simply updating the replicas field.

Replication Controller#Scaling

This blog will show how a Kubernetes cluster can be easily scaled up and down.

All the code used in this blog is available at kubernetes-java-sample.

Start Replication Controller and Verify

Start a Replication Controller as:

./cluster/kubectl.sh create -f ~/workspaces/kubernetes-java-sample/wildfly-rc.yaml 
replicationcontrollers/wildfly-rc

./cluster/kubectl.sh create -f ~/workspaces/kubernetes-java-sample/wildfly-rc.yaml

replicationcontrollers/wildfly-rc

Get status of the Pods:

./cluster/kubectl.sh get -w po
NAME      READY     STATUS    RESTARTS   AGE
NAME               READY     STATUS    RESTARTS   AGE
wildfly-rc-bgtkg   0/1       Pending   0          1s
wildfly-rc-l8fqv   0/1       Pending   0         1s
wildfly-rc-bgtkg   0/1       Pending   0         1s
wildfly-rc-l8fqv   0/1       Pending   0         1s
wildfly-rc-bgtkg   0/1       Pending   0         1s
wildfly-rc-l8fqv   0/1       Pending   0         1s
wildfly-rc-bgtkg   0/1       Running   0         1m
wildfly-rc-l8fqv   0/1       Running   0         1m
wildfly-rc-bgtkg   1/1       Running   0         1m
wildfly-rc-l8fqv   1/1       Running   0         1m

./cluster/kubectl.sh get -w po

NAME READY STATUS RESTARTS AGE

wildfly-rc-bgtkg 0/1 Pending 0 1s

wildfly-rc-l8fqv 0/1 Pending 0 1s

wildfly-rc-bgtkg 0/1 Pending 0 1s

wildfly-rc-l8fqv 0/1 Pending 0 1s

wildfly-rc-bgtkg 0/1 Pending 0 1s

wildfly-rc-l8fqv 0/1 Pending 0 1s

wildfly-rc-bgtkg 0/1 Running 0 1m

wildfly-rc-l8fqv 0/1 Running 0 1m

wildfly-rc-bgtkg 1/1 Running 0 1m

wildfly-rc-l8fqv 1/1 Running 0 1m

Make sure to wait for the status to change to Running.

Note down name of the Pods as wildfly-rc-bgtkg” and wildfly-rc-bgtkg”.

Get status of the Replication Controller:

./cluster/kubectl.sh get rc
CONTROLLER   CONTAINER(S)     IMAGE(S)        SELECTOR       REPLICAS
wildfly-rc   wildfly-rc-pod   jboss/wildfly   name=wildfly   2

./cluster/kubectl.sh get rc

CONTROLLER CONTAINER(S) IMAGE(S) SELECTOR REPLICAS

wildfly-rc wildfly-rc-pod jboss/wildfly name=wildfly 2

If multiple Replication Controllers are running then you can query for this specific one using the label:

./cluster/kubectl.sh get rc -l name=wildfly
CONTROLLER   CONTAINER(S)     IMAGE(S)        SELECTOR       REPLICAS
wildfly-rc   wildfly-rc-pod   jboss/wildfly   name=wildfly   2

./cluster/kubectl.sh get rc -l name=wildfly

CONTROLLER CONTAINER(S) IMAGE(S) SELECTOR REPLICAS

wildfly-rc wildfly-rc-pod jboss/wildfly name=wildfly 2

Scaling Kubernetes Cluster Up

Replication Controller allows dynamic scaling up and down of Pods.

Scale up the number of Pods:

./cluster/kubectl.sh scale --replicas=3 rc wildfly-rc
scaled

./cluster/kubectl.sh scale --replicas=3 rc wildfly-rc

scaled

Status of the Pods can be seen in another shell:

./cluster/kubectl.sh get -w po
NAME               READY     STATUS    RESTARTS   AGE
wildfly-rc-k6pk2   1/1       Running   0          47s
wildfly-rc-wez29   1/1       Running   0          47s
NAME               READY     STATUS    RESTARTS   AGE
wildfly-rc-aqaqn   0/1       Pending   0          0s
wildfly-rc-aqaqn   0/1       Pending   0         0s
wildfly-rc-aqaqn   0/1       Pending   0         0s
wildfly-rc-aqaqn   0/1       Running   0         2s
wildfly-rc-aqaqn   1/1       Running   0         11s

./cluster/kubectl.sh get -w po

NAME READY STATUS RESTARTS AGE

wildfly-rc-k6pk2 1/1 Running 0 47s

wildfly-rc-wez29 1/1 Running 0 47s

NAME READY STATUS RESTARTS AGE

wildfly-rc-aqaqn 0/1 Pending 0 0s

wildfly-rc-aqaqn 0/1 Running 0 2s

wildfly-rc-aqaqn 1/1 Running 0 11s

Notice a new Pod with the name wildfly-rc-aqaqn is created.

Scale Kubernetes Cluster Down

Scale down the number of Pods:

./cluster/kubectl.sh scale --replicas=1 rc wildfly-rc
scaled

./cluster/kubectl.sh scale --replicas=1 rc wildfly-rc

scaled

Status of the Pods using -w is not correctly updated (#11338). But status of the Pods can be seen correctly as:

./cluster/kubectl.sh get po
NAME               READY     STATUS    RESTARTS   AGE
wildfly-rc-k6pk2   1/1       Running   0          9m

./cluster/kubectl.sh get po

NAME READY STATUS RESTARTS AGE

wildfly-rc-k6pk2 1/1 Running 0 9m

Notice only one Pod is now running.

Kubernetes dynamically scales the Pods up and down using the scale --replicas command.

All code used in this blog is available at kubernetes-java-sample.

Enjoy!

Automatic Restarting of Pods inside Replication Controller of Kubernetes Cluster

July 14, 2015containers, redhat, techtipclustering, docker, kubernetesarungupta

A key feature of Kubernetes is its ability to maintain the “desired state” using declared primitives. Replication Controllers is a key concept that helps achieve this state.

A replication controller ensures that a specified number of pod “replicas” are running at any one time. If there are too many, it will kill some. If there are too few, it will start more.

Replication Controller

Lets take a look on how to spin up a Replication Controller with two replicas of a Pod. Then we’ll kill one pod and see how Kubernetes will start another Pod automatically.

Start Kubernetes Cluster

Easiest way to start a Kubernetes cluster on a Mac OS is using Vagrant:

export KUBERNETES_PROVIDER=vagrant
curl -sS https://get.k8s.io | bash

export KUBERNETES_PROVIDER=vagrant

curl -sS https://get.k8s.io | bash

Alternatively, Kubernetes can be downloaded from github.com/GoogleCloudPlatform/kubernetes/releases/download/v1.0.0/kubernetes.tar.gz, and cluster can be started as:

cd kubernetes
export KUBERNETES_PROVIDER=vagrant
cluster/kube-up.sh

cd kubernetes

export KUBERNETES_PROVIDER=vagrant

cluster/kube-up.sh

Start and Verify Replication Controller and Pods

All configuration files required by Kubernetes to start Replication Controller are in kubernetes-java-sample project. Clone the workspace:

git clone https://github.com/arun-gupta/kubernetes-java-sample.git

git clone https://github.com/arun-gupta/kubernetes-java-sample.git

Start a Replication Controller that has two replicas of a pod, each with a WildFly container:

./cluster/kubectl.sh create -f ~/workspaces/kubernetes-java-sample/wildfly-rc.yaml
replicationcontrollers/wildfly-rc

./cluster/kubectl.sh create -f ~/workspaces/kubernetes-java-sample/wildfly-rc.yaml

replicationcontrollers/wildfly-rc

The configuration file used is shown:

apiVersion: v1
kind: ReplicationController
metadata:
  name: wildfly-rc
  labels:
    name: wildfly
spec:
  replicas: 2
  template:
    metadata:
      labels:
        name: wildfly
    spec:
      containers:
      - name: wildfly-rc-pod
        image: jboss/wildfly
        ports:
        - containerPort: 8080

apiVersion: v1

kind: ReplicationController

metadata:

labels:

spec:

replicas: 2

template:

metadata:

labels:

spec:

containers:

- name: wildfly-rc-pod

image: jboss/wildfly

ports:

- containerPort: 8080

Default WildFly Docker image is used here.

Get status of the Pods:

./cluster/kubectl.sh get -w po
NAME               READY     STATUS    RESTARTS   AGE
wildfly-rc-15xg5   0/1       Pending   0          2s
wildfly-rc-d5fbs   0/1       Pending   0          2s
NAME               READY     STATUS    RESTARTS   AGE
wildfly-rc-15xg5   0/1       Pending   0          5s
wildfly-rc-d5fbs   0/1       Pending   0         5s
wildfly-rc-d5fbs   0/1       Running   0         8s
wildfly-rc-15xg5   0/1       Running   0         8s
wildfly-rc-d5fbs   1/1       Running   0         15s
wildfly-rc-15xg5   1/1       Running   0         15s

./cluster/kubectl.sh get -w po

NAME READY STATUS RESTARTS AGE

wildfly-rc-15xg5 0/1 Pending 0 2s

wildfly-rc-d5fbs 0/1 Pending 0 2s

NAME READY STATUS RESTARTS AGE

wildfly-rc-15xg5 0/1 Pending 0 5s

wildfly-rc-d5fbs 0/1 Pending 0 5s

wildfly-rc-d5fbs 0/1 Running 0 8s

wildfly-rc-15xg5 0/1 Running 0 8s

wildfly-rc-d5fbs 1/1 Running 0 15s

wildfly-rc-15xg5 1/1 Running 0 15s

Notice -w refreshes the status whenever there is a change. The status changes from Pending to Running and then Ready to receive requests.

Get status of the Replication Controller:

./cluster/kubectl.sh get rc
CONTROLLER   CONTAINER(S)     IMAGE(S)        SELECTOR       REPLICAS
wildfly-rc   wildfly-rc-pod   jboss/wildfly   name=wildfly   2

./cluster/kubectl.sh get rc

CONTROLLER CONTAINER(S) IMAGE(S) SELECTOR REPLICAS

wildfly-rc wildfly-rc-pod jboss/wildfly name=wildfly 2

If multiple Replication Controllers are running then you can query for this specific one using the label:

./cluster/kubectl.sh get rc -l name=wildfly
CONTROLLER   CONTAINER(S)     IMAGE(S)        SELECTOR       REPLICAS
wildfly-rc   wildfly-rc-pod   jboss/wildfly   name=wildfly   2

./cluster/kubectl.sh get rc -l name=wildfly

CONTROLLER CONTAINER(S) IMAGE(S) SELECTOR REPLICAS

wildfly-rc wildfly-rc-pod jboss/wildfly name=wildfly 2

Get name of the running Pods:

./cluster/kubectl.sh get po
NAME               READY     STATUS    RESTARTS   AGE
wildfly-rc-15xg5   1/1       Running   0          36m
wildfly-rc-d5fbs   1/1       Running   0          36m

./cluster/kubectl.sh get po

NAME READY STATUS RESTARTS AGE

wildfly-rc-15xg5 1/1 Running 0 36m

wildfly-rc-d5fbs 1/1 Running 0 36m

Find IP address of each Pod (using the name):

./cluster/kubectl.sh get -o template po wildfly-rc-15xg5 --template={{.status.podIP}}
10.246.1.18

./cluster/kubectl.sh get -o template po wildfly-rc-15xg5 --template={{.status.podIP}}

10.246.1.18

And of the other Pod as well:

./cluster/kubectl.sh get -o template po wildfly-rc-d5fbs --template={{.status.podIP}}
10.246.1.19

./cluster/kubectl.sh get -o template po wildfly-rc-d5fbs --template={{.status.podIP}}

10.246.1.19

Pod’s IP address is accessible only inside the cluster. Login to the minion to access WildFly’s main page hosted by the containers:

kubernetes> vagrant ssh minion-1
Last login: Tue Jul 14 21:35:12 2015 from 10.0.2.2
[vagrant@kubernetes-minion-1 ~]$ curl http://10.246.1.18:8080
<!--
  ~ JBoss, Home of Professional Open Source.

. . .

</div>
</body>
</html>
[vagrant@kubernetes-minion-1 ~]$ curl http://10.246.1.19:8080
<!--
  ~ JBoss, Home of Professional Open Source.
  ~ Copyright (c) 2014, Red Hat, Inc., and individual contributors

. . .

</div>
</body>
</html>

kubernetes> vagrant ssh minion-1

Last login: Tue Jul 14 21:35:12 2015 from 10.0.2.2

[vagrant@kubernetes-minion-1 ~]$ curl http://10.246.1.18:8080

<!--

~ JBoss, Home of Professional Open Source.

. . .

</div>

</body>

</html>

[vagrant@kubernetes-minion-1 ~]$ curl http://10.246.1.19:8080

<!--

~ JBoss, Home of Professional Open Source.

. . .

</div>

</body>

</html>

Automatic Restart of Pods

Lets delete a Pod and see how a new Pod is automatically created.

kubernetes> ./cluster/kubectl.sh delete po wildfly-rc-15xg5
pods/wildfly-rc-15xg5
kubernetes> ./cluster/kubectl.sh get -w po
NAME               READY     STATUS    RESTARTS   AGE
wildfly-rc-0xoms   0/1       Pending   0          2s
wildfly-rc-d5fbs   1/1       Running   0          48m
NAME               READY     STATUS    RESTARTS   AGE
wildfly-rc-0xoms   0/1       Pending   0          11s
wildfly-rc-0xoms   0/1       Running   0         13s
wildfly-rc-0xoms   1/1       Running   0         21s

kubernetes> ./cluster/kubectl.sh delete po wildfly-rc-15xg5

pods/wildfly-rc-15xg5

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

NAME READY STATUS RESTARTS AGE

wildfly-rc-0xoms 0/1 Pending 0 2s

wildfly-rc-d5fbs 1/1 Running 0 48m

NAME READY STATUS RESTARTS AGE

wildfly-rc-0xoms 0/1 Pending 0 11s

wildfly-rc-0xoms 0/1 Running 0 13s

wildfly-rc-0xoms 1/1 Running 0 21s

Notice how the Pod with name wildfly-rc-15xg5 was deleted and a new Pod with the name wildfly-rc-0xoms was created.

Finally, delete the Replication Controller:

kubectl.sh create -f ~/workspaces/kubernetes-java-sample/wildfly-rc.yaml

kubectl.sh create -f ~/workspaces/kubernetes-java-sample/wildfly-rc.yaml

The latest configuration files and detailed instructions are at kubernetes-java-sample.

In real world, you’ll typically wrap this Replication Controller in a Service and front-end with a Load Balancer. But that’s a topic for another blog!

Enjoy!

OpenShift v3: Getting Started with Java EE 7 using WildFly and MySQL (Tech Tip #73)

February 13, 2015containers, javaee, techtip, wildflydevops, docker, javaee7, kubernetes, openshift, wildflyarungupta

OpenShift is Red Hat’s open source PaaS platform. OpenShift v3 (due to be released this year) will provide a holistic experience on running your microservices using Docker and Kubernetes. In a classic Red Hat way, all the work is done in the open source at OpenShift Origin. This will also drive the next major release of OpenShift Online and OpenShift Enterprise.

OpenShift v3 uses a new platform stack that is using plenty of community projects where Red Hat contributes such as Fedora, Centos, Docker, Project Atomic, Kubernetes, and OpenStack. OpenShift v3 Platform Combines Docker, Kubernetes, Atomic and More explain this platform stack in detail.

This tech tip will explain how to get started with OpenShift v3, lets get started!

Getting Started with OpenShift v3

Pre-built binaries for OpenShift v3 can be downloaded from Origin at GitHub. However the simplest way to get started is to run OpenShift Origin as a Docker container.

OpenShift Application Lifecycle provide complete details on what it takes to run a sample application from scratch. This blog will use those steps and adapt them to run using boot2docker VM on Mac. And in the process we’ll also deploy a Java EE 7 application on WildFly which will be accessing database on a separate MySQL container.

Here is our deployment diagram:

WildFly and MySQL are running on separate pods.
Each of them is wrapped in a Replication Controller to enable simplified scaling.
Each Replication Controller is published as a Service.
WildFly talks to the MySQL service, as opposed to directly to the pod. This is important as Pods, and IP addresses assigned to them, are ephemeral.

Lets get started!

Configure Docker Daemon

Configure the docker daemon on your host to trust the docker registry service you’ll be starting. This registry will be used to push images for build/test/deploy cycle.

Log into boot2docker VM as:

boot2docker ssh

boot2docker ssh

Edit the file

sudo vi /var/lib/boot2docker/profile

sudo vi /var/lib/boot2docker/profile

This will be an empty file.

Add the following name/value pair:

EXTRA_ARGS="--insecure-registry 172.30.17.0/24"

EXTRA_ARGS="--insecure-registry 172.30.17.0/24"

Save the file, and quit the editor.

This will instruct the docker daemon to trust any docker registry on the 172.30.17.0/24 subnet.

Check out OpenShift v3 and Java EE 7 Sample

Download and Install Go and setup GOPATH and PATH environment variable. Check out OpenShift origin directory:

openshift> git clone https://github.com/openshift/origin.git
Cloning into 'origin'...
remote: Counting objects: 21451, done.
remote: Compressing objects: 100% (76/76), done.
remote: Total 21451 (delta 26), reused 15 (delta 1)
Receiving objects: 100% (21451/21451), 35.11 MiB | 1.24 MiB/s, done.
Resolving deltas: 100% (11392/11392), done.
Checking connectivity... done.

openshift> git clone https://github.com/openshift/origin.git

Cloning into 'origin'...

remote: Counting objects: 21451, done.

remote: Compressing objects: 100% (76/76), done.

remote: Total 21451 (delta 26), reused 15 (delta 1)

Receiving objects: 100% (21451/21451), 35.11 MiB | 1.24 MiB/s, done.

Resolving deltas: 100% (11392/11392), done.

Checking connectivity... done.

Note the directory where its checked out. In this case, its ~/workspaces/openshift.

Build the workspace:

make release
origin> make release
rm -rf _output Godeps/_workspace/pkg
hack/build-release.sh
Unable to find image 'openshift/origin-release' locally
Pulling repository openshift/origin-release
c59f040a4054: Download complete 
511136ea3c5a: Download complete 
5b12ef8fd570: Download complete 
dade6cb4530a: Download complete 
bd195712b86c: Download complete 
4aae29c1c846: Download complete 
d8738da3ed4c: Download complete 
7f7491063665: Download complete 
b5cfa9eebdb5: Download complete 
2f6297477756: Download complete 
dc98bd93df2f: Download complete 
1be2a7550a3d: Download complete 
42fd088f8c55: Download complete 
b6f6ad4012df: Download complete 
Status: Downloaded newer image for openshift/origin-release:latest

make release

origin> make release

rm -rf _output Godeps/_workspace/pkg

hack/build-release.sh

Unable to find image 'openshift/origin-release' locally

Pulling repository openshift/origin-release

c59f040a4054: Download complete

511136ea3c5a: Download complete

5b12ef8fd570: Download complete

dade6cb4530a: Download complete

bd195712b86c: Download complete

4aae29c1c846: Download complete

d8738da3ed4c: Download complete

7f7491063665: Download complete

b5cfa9eebdb5: Download complete

2f6297477756: Download complete

dc98bd93df2f: Download complete

1be2a7550a3d: Download complete

42fd088f8c55: Download complete

b6f6ad4012df: Download complete

Status: Downloaded newer image for openshift/origin-release:latest

Check out javaee7-hol workspace that has been converted to a Kubernetes application:

origin> git clone https://github.com/bparees/javaee7-hol
Cloning into 'javaee7-hol'...
remote: Counting objects: 1159, done.
remote: Compressing objects: 100% (49/49), done.
remote: Total 1159 (delta 35), reused 37 (delta 21)
Receiving objects: 100% (1159/1159), 20.35 MiB | 1.78 MiB/s, done.
Resolving deltas: 100% (605/605), done.
Checking connectivity... done.

origin> git clone https://github.com/bparees/javaee7-hol

Cloning into 'javaee7-hol'...

remote: Counting objects: 1159, done.

remote: Compressing objects: 100% (49/49), done.

remote: Total 1159 (delta 35), reused 37 (delta 21)

Receiving objects: 100% (1159/1159), 20.35 MiB | 1.78 MiB/s, done.

Resolving deltas: 100% (605/605), done.

Checking connectivity... done.

This is also done in ~/workspaces/openshift directory.

Start OpenShift v3 Container

Start OpenShift Origin as Docker container:

~> docker run -d --name "openshift-origin" --net=host --privileged \
  -v /var/run/docker.sock:/var/run/docker.sock  \
  -v /Users/arungupta/workspaces/openshift:/workspaces/openshift \
  -v /usr/local/bin/docker:/usr/bin/docker \
  openshift/origin start --public-master=$(boot2docker ip)

The VM's Host only interface IP address is: 

0ae85091e7ad7e85697575369f008273a6673d112b49860f5557a61d9e82d908

~> docker run -d --name "openshift-origin" --net=host --privileged \

-v /var/run/docker.sock:/var/run/docker.sock \

-v /Users/arungupta/workspaces/openshift:/workspaces/openshift \

-v /usr/local/bin/docker:/usr/bin/docker \

openshift/origin start --public-master=$(boot2docker ip)

The VM's Host only interface IP address is:

0ae85091e7ad7e85697575369f008273a6673d112b49860f5557a61d9e82d908

Note ~/workspaces/openshift directory is mounted as /workspaces/openshift volume in the container. Some additional volumes are mounted as well.

Check that the container is running:

~> docker ps
CONTAINER ID        IMAGE                    COMMAND                CREATED             STATUS              PORTS               NAMES
0ae85091e7ad        openshift/origin:beta1   "/usr/bin/openshift    2 minutes ago       Up 2 minutes                            openshift-origin

~> docker ps

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

0ae85091e7ad openshift/origin:beta1 "/usr/bin/openshift 2 minutes ago Up 2 minutes openshift-origin

Log into the container as:

openshift> docker exec -it `docker ps | grep origin:beta1 | awk '{ print $1 }'` bash
[root@boot2docker openshift]#

openshift> docker exec -it `docker ps | grep origin:beta1 | awk '{ print $1 }'` bash

[root@boot2docker openshift]#

Install Docker registry in the container by giving the following command:

export CERT_DIR=/var/lib/openshift/openshift.local.certificates/openshift-client && \
export KUBECONFIG=/var/lib/openshift/openshift.local.certificates/admin/.kubeconfig && \
cd /workspaces/openshift/origin && hack/install-registry.sh

export CERT_DIR=/var/lib/openshift/openshift.local.certificates/openshift-client && \

export KUBECONFIG=/var/lib/openshift/openshift.local.certificates/admin/.kubeconfig && \

cd /workspaces/openshift/origin && hack/install-registry.sh

Confirm that the registry is running by getting the list of pods:

[root@boot2docker origin]# osc get pods
POD                       IP                  CONTAINER(S)         IMAGE(S)                    HOST                    LABELS                                                                                                             STATUS
docker-registry-1-gfkbz   172.17.0.14         registry-container   openshift/docker-registry   boot2docker/127.0.0.1   deployment=docker-registry-1,deploymentconfig=docker-registry,name=registrypod,template=docker-registry-template   Running

[root@boot2docker origin]# osc get pods

POD IP CONTAINER(S) IMAGE(S) HOST LABELS STATUS

docker-registry-1-gfkbz 172.17.0.14 registry-container openshift/docker-registry boot2docker/127.0.0.1 deployment=docker-registry-1,deploymentconfig=docker-registry,name=registrypod,template=docker-registry-template Running

osc is OpenShift Client CLI and allows to create and manage OpenShift projects. Some of the kubectl commands can also be using this script.

Confirm the registry service is running. Note the actual IP address may vary:

[root@boot2docker origin]# osc get services
NAME                LABELS                                    SELECTOR            IP                  PORT
docker-registry     template=docker-registry-template         name=registrypod    172.30.17.142       5001
kubernetes          component=apiserver,provider=kubernetes   <none>              172.30.17.2         443
kubernetes-ro       component=apiserver,provider=kubernetes   <none>              172.30.17.1         80

[root@boot2docker origin]# osc get services

NAME LABELS SELECTOR IP PORT

docker-registry template=docker-registry-template name=registrypod 172.30.17.142 5001

kubernetes component=apiserver,provider=kubernetes <none> 172.30.17.2 443

kubernetes-ro component=apiserver,provider=kubernetes <none> 172.30.17.1 80

Confirm that the registry service is accessible:

curl `osc get services docker-registry -o template --template="{{ .portalIP}}:{{ .port }}"`

curl `osc get services docker-registry -o template --template="{{ .portalIP}}:{{ .port }}"`

And look for the output:

"docker-registry server (dev) (v0.9.0)"

"docker-registry server (dev) (v0.9.0)"

Access OpenShift v3 Web Console

OpenShift Origin server is now up and running. Find out the host’s IP address using boot2docker ip and open http://<IP addresss of boot2docker host>:8444 to view OpenShift Web Console in your browser.For example, the console is accessible at https://192.168.59.103:8444/ on this machine.

You will need to have the browser accept the certificate at https://<host>:8444 before the console can consult the OpenShift API. Of course this would not be necessary with a legitimate certificate.
OpenShift Origin login screen shows up. Enter the username/password as admin/admin:

and click on the “Log In” button. The default web console looks like:

Create OpenShift v3 Project

Use project.json from github.com/openshift/origin/blob/master/examples/sample-app/project.json in the OpenShift v3 container and create a test project as:

[root@boot2docker origin]# osc create -f /workspaces/openshift/origin/examples/sample-app/project.json 
test

[root@boot2docker origin]# osc create -f /workspaces/openshift/origin/examples/sample-app/project.json

test

Refreshing the web console now shows:

Clicking on “OpenShift 3 Sample” shows an empty project description:

Request creation of the application template:

[root@boot2docker openshift]# cd javaee7-hol/
[root@boot2docker javaee7-hol]# osc process -n test -f application-template-jeebuild.json | osc create -n test -f -
frontend
origin-jee-sample
wildfly-8-centos
jee-sample-build
frontend
mysql
database

[root@boot2docker openshift]# cd javaee7-hol/

[root@boot2docker javaee7-hol]# osc process -n test -f application-template-jeebuild.json | osc create -n test -f -

frontend

origin-jee-sample

wildfly-8-centos

jee-sample-build

frontend

mysql

database

Web Console automatically refreshes and shows:

The list of services running can be seen as:

Build the Project

Trigger an initial build of your project:

[root@boot2docker javaee7-hol]# osc start-build -n test jee-sample-build
cee73fbc-b32d-11e4-a0f2-5282784576db

[root@boot2docker javaee7-hol]# osc start-build -n test jee-sample-build

cee73fbc-b32d-11e4-a0f2-5282784576db

Monitor the builds and wait for the status to go to “complete” (this can take a few minutes):

[root@boot2docker javaee7-hol]#  osc get -n test builds
NAME                                   TYPE                STATUS              POD
cee73fbc-b32d-11e4-a0f2-5282784576db   STI                 Running             build-cee73fbc-b32d-11e4-a0f2-5282784576db

[root@boot2docker javaee7-hol]# osc get -n test builds

NAME TYPE STATUS POD

cee73fbc-b32d-11e4-a0f2-5282784576db STI Running build-cee73fbc-b32d-11e4-a0f2-5282784576db

You can add the –watch flag to wait for updates until the build completes:

[root@boot2docker javaee7-hol]#  osc get -n test builds --watch
NAME                                   TYPE                STATUS              POD
cee73fbc-b32d-11e4-a0f2-5282784576db   STI                 Running             build-cee73fbc-b32d-11e4-a0f2-5282784576db
NAME                                   TYPE                STATUS              POD
cee73fbc-b32d-11e4-a0f2-5282784576db   STI                 Complete            build-cee73fbc-b32d-11e4-a0f2-5282784576db

[root@boot2docker javaee7-hol]# osc get -n test builds --watch

NAME TYPE STATUS POD

cee73fbc-b32d-11e4-a0f2-5282784576db STI Running build-cee73fbc-b32d-11e4-a0f2-5282784576db

NAME TYPE STATUS POD

cee73fbc-b32d-11e4-a0f2-5282784576db STI Complete build-cee73fbc-b32d-11e4-a0f2-5282784576db

Wait for the STATUS column to show Complete. It will take a few minutes as all the components (WIldFly, MySQL, Java EE 7 application) are provisioned. Effectively, their new Docker images are created and pushed to the local registry that was started earlier.

Hit Ctrl+C to stop watching builds after the status changes to Complete.

Complete log of the build can be seen as:

[root@boot2docker javaee7-hol]# osc build-logs -n test cee73fbc-b32d-11e4-a0f2-5282784576db
2015-02-13T03:10:07.065718606Z Cloning into '/tmp/sti552730161/upload/src'...
2015-02-13T03:11:03.184576532Z I0213 03:11:03.184326       1 build.go:160] Successfully built 172.30.17.142:5001/test/origin-jee-sample
2015-02-13T03:11:07.261489310Z The push refers to a repository [172.30.17.142:5001/test/origin-jee-sample] (len: 1)
2015-02-13T03:11:07.261489310Z Sending image list
2015-02-13T03:11:07.275256699Z Pushing repository 172.30.17.142:5001/test/origin-jee-sample (1 tags)
2015-02-13T03:11:07.307836081Z Pushing
Buffering to disk07.314345045Z Buffering to disk 1.024 kB
2015-02-13T03:11:07.315452728Z Buffering to disk
Pushing-13T03:11:07.323973430Z Pushing [=========================>                         ]    512 B/1.024 kB 0

. . .

Pushing-13T03:13:05.932725921Z Pushing [================================================>  ]  6.56 MB/6.704 MB 0
Pushing-13T03:13:05.942989165Z Pushing [=================================================> ] 6.635 MB/6.704 MB 0
Pushing-13T03:13:05.943025109Z Pushing [=================================================> ] 6.702 MB/6.704 MB 0
Pushing-13T03:13:05.947665528Z Pushing [==================================================>] 6.704 MB/6.704 MB
2015-02-13T03:13:05.953476634Z Image successfully pushed
2015-02-13T03:13:05.953476634Z Pushing tag for rev [b0a7868377c1] on {http://172.30.17.142:5001/v1/repositories/test/origin-jee-sample/tags/latest}

[root@boot2docker javaee7-hol]# osc build-logs -n test cee73fbc-b32d-11e4-a0f2-5282784576db

2015-02-13T03:10:07.065718606Z Cloning into '/tmp/sti552730161/upload/src'...

2015-02-13T03:11:03.184576532Z I0213 03:11:03.184326 1 build.go:160] Successfully built 172.30.17.142:5001/test/origin-jee-sample

2015-02-13T03:11:07.261489310Z The push refers to a repository [172.30.17.142:5001/test/origin-jee-sample] (len: 1)

2015-02-13T03:11:07.261489310Z Sending image list

2015-02-13T03:11:07.275256699Z Pushing repository 172.30.17.142:5001/test/origin-jee-sample (1 tags)

2015-02-13T03:11:07.307836081Z Pushing

Buffering to disk07.314345045Z Buffering to disk 1.024 kB

2015-02-13T03:11:07.315452728Z Buffering to disk

Pushing-13T03:11:07.323973430Z Pushing [=========================> ] 512 B/1.024 kB 0

. . .

Pushing-13T03:13:05.932725921Z Pushing [================================================> ] 6.56 MB/6.704 MB 0

Pushing-13T03:13:05.942989165Z Pushing [=================================================> ] 6.635 MB/6.704 MB 0

Pushing-13T03:13:05.943025109Z Pushing [=================================================> ] 6.702 MB/6.704 MB 0

Pushing-13T03:13:05.947665528Z Pushing [==================================================>] 6.704 MB/6.704 MB

2015-02-13T03:13:05.953476634Z Image successfully pushed

2015-02-13T03:13:05.953476634Z Pushing tag for rev [b0a7868377c1] on {http://172.30.17.142:5001/v1/repositories/test/origin-jee-sample/tags/latest}

Check for the application pods to start:

[root@boot2docker javaee7-hol]# osc get -n test pods    
POD                                          IP                  CONTAINER(S)        IMAGE(S)                                                                                                     HOST                    LABELS                                                                              STATUS
build-cee73fbc-b32d-11e4-a0f2-5282784576db   172.17.0.17         sti-build           openshift/origin-sti-builder:v0.3                                                                            boot2docker/127.0.0.1   <none>                                                                              Succeeded
database-1-axe6d                             172.17.0.16         jee-database        mysql                                                                                                        boot2docker/127.0.0.1   deployment=database-1,deploymentconfig=database,name=database,template=jee-sample   Running
frontend-1-pkcia                             172.17.0.20         jee-sample          172.30.17.142:5001/test/origin-jee-sample:b0a7868377c10a50b40019be70e22d040b9a2bb2d87fa3932b700494e50a4de6   boot2docker/127.0.0.1   deployment=frontend-1,deploymentconfig=frontend,name=frontend,template=jee-sample   Running

[root@boot2docker javaee7-hol]# osc get -n test pods

POD IP CONTAINER(S) IMAGE(S) HOST LABELS STATUS

build-cee73fbc-b32d-11e4-a0f2-5282784576db 172.17.0.17 sti-build openshift/origin-sti-builder:v0.3 boot2docker/127.0.0.1 <none> Succeeded

database-1-axe6d 172.17.0.16 jee-database mysql boot2docker/127.0.0.1 deployment=database-1,deploymentconfig=database,name=database,template=jee-sample Running

frontend-1-pkcia 172.17.0.20 jee-sample 172.30.17.142:5001/test/origin-jee-sample:b0a7868377c10a50b40019be70e22d040b9a2bb2d87fa3932b700494e50a4de6 boot2docker/127.0.0.1 deployment=frontend-1,deploymentconfig=frontend,name=frontend,template=jee-sample Running

Note, that the “frontend” and “database” pods are now running.

Determine IP of the “frontend” service:

[root@boot2docker javaee7-hol]# osc get -n test services
NAME                LABELS                SELECTOR            IP                  PORT
frontend            template=jee-sample   name=frontend       172.30.17.115       8080
mysql               template=jee-sample   name=database       172.30.17.75        3306

[root@boot2docker javaee7-hol]# osc get -n test services

NAME LABELS SELECTOR IP PORT

frontend template=jee-sample name=frontend 172.30.17.115 8080

mysql template=jee-sample name=database 172.30.17.75 3306

Access the application at http://<IP address of “frontend”>:8080/movieplex7-1.0-SNAPSHOT should work. Note the IP address may (most likely will) vary. In this case, it would be http://172.30.17.115:8080/moviexplex7-1.0-SNAPSHOT.The app would not be accessible yet, as some further debugging is required to configure firewall on Mac when OpenShift v3 is used as Docker container. Until we figure that out, you can do docker ps in your boot2docker VM to see the list of all the containers:

origin> docker ps
CONTAINER ID        IMAGE                                                                                                       COMMAND                CREATED             STATUS              PORTS               NAMES
c776cabb72f8        172.30.17.17:5001/test/origin-jee-sample:91d1b5a5ed58e1642aafbd652eba0b7eae3a0ac08c17729d205ae88204f64449   "/tmp/scripts/run"     2 hours ago         Up 2 hours                              k8s_jee-sample.7af25557_frontend-2-9ciae.test.api_12a0d77e-b3b5-11e4-81f6-5282784576db_53f91f55                      
e7f87112c473        openshift/origin-pod:beta1                                                                                  "/pod"                 2 hours ago         Up 2 hours                              k8s_POD.9cbfdefa_frontend-2-9ciae.test.api_12a0d77e-b3b5-11e4-81f6-5282784576db_64263b61                             
7e7579db5f82        openshift/origin-pod:beta1                                                                                  "/pod"                 2 hours ago         Up 2 hours                              k8s_POD.123cbdd6_build-e075047d-b3b4-11e4-81f6-5282784576db.test.api_e07bcdb2-b3b4-11e4-81f6-5282784576db_376c0e63   
74082d7791ec        openshift/origin-pod:beta1                                                                                  "/pod"                 2 hours ago         Up 2 hours                              k8s_POD.123cbdd6_build-76364bb6-b3b2-11e4-81f6-5282784576db.test.api_7639e3a5-b3b2-11e4-81f6-5282784576db_f653c7fd   
3e42dacb0da7        mysql:latest                                                                                                "/entrypoint.sh mysq   3 hours ago         Up 3 hours                              k8s_jee-database.f12628ae_database-1-bqg8v.test.api_56093bac-b3b2-11e4-81f6-5282784576db_193dddf7                    
cb551c8cf7bf        openshift/origin-pod:beta1                                                                                  "/pod"                 3 hours ago         Up 3 hours                              k8s_POD.95f2def6_database-1-bqg8v.test.api_56093bac-b3b2-11e4-81f6-5282784576db_295fc320                             
e8719152df42        openshift/docker-registry:latest                                                                            "\"sh -c 'echo \"$OP   3 hours ago         Up 3 hours                              k8s_registry-container.4e338487_docker-registry-1-bt49s.default.api_177a691c-b3b0-11e4-81f6-5282784576db_a6f4f83b    
d3ecc5841c3b        openshift/origin-pod:beta1                                                                                  "/pod"                 3 hours ago         Up 3 hours                              k8s_POD.8a29deef_docker-registry-1-bt49s.default.api_177a691c-b3b0-11e4-81f6-5282784576db_ba53d62b                   
a506222fae91        openshift/origin:beta1                                                                                      "/usr/bin/openshift    3 hours ago         Up 3 hours                              openshift-origin

origin> docker ps

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

c776cabb72f8 172.30.17.17:5001/test/origin-jee-sample:91d1b5a5ed58e1642aafbd652eba0b7eae3a0ac08c17729d205ae88204f64449 "/tmp/scripts/run" 2 hours ago Up 2 hours k8s_jee-sample.7af25557_frontend-2-9ciae.test.api_12a0d77e-b3b5-11e4-81f6-5282784576db_53f91f55

e7f87112c473 openshift/origin-pod:beta1 "/pod" 2 hours ago Up 2 hours k8s_POD.9cbfdefa_frontend-2-9ciae.test.api_12a0d77e-b3b5-11e4-81f6-5282784576db_64263b61

7e7579db5f82 openshift/origin-pod:beta1 "/pod" 2 hours ago Up 2 hours k8s_POD.123cbdd6_build-e075047d-b3b4-11e4-81f6-5282784576db.test.api_e07bcdb2-b3b4-11e4-81f6-5282784576db_376c0e63

74082d7791ec openshift/origin-pod:beta1 "/pod" 2 hours ago Up 2 hours k8s_POD.123cbdd6_build-76364bb6-b3b2-11e4-81f6-5282784576db.test.api_7639e3a5-b3b2-11e4-81f6-5282784576db_f653c7fd

3e42dacb0da7 mysql:latest "/entrypoint.sh mysq 3 hours ago Up 3 hours k8s_jee-database.f12628ae_database-1-bqg8v.test.api_56093bac-b3b2-11e4-81f6-5282784576db_193dddf7

cb551c8cf7bf openshift/origin-pod:beta1 "/pod" 3 hours ago Up 3 hours k8s_POD.95f2def6_database-1-bqg8v.test.api_56093bac-b3b2-11e4-81f6-5282784576db_295fc320

e8719152df42 openshift/docker-registry:latest "\"sh -c 'echo \"$OP 3 hours ago Up 3 hours k8s_registry-container.4e338487_docker-registry-1-bt49s.default.api_177a691c-b3b0-11e4-81f6-5282784576db_a6f4f83b

d3ecc5841c3b openshift/origin-pod:beta1 "/pod" 3 hours ago Up 3 hours k8s_POD.8a29deef_docker-registry-1-bt49s.default.api_177a691c-b3b0-11e4-81f6-5282784576db_ba53d62b

a506222fae91 openshift/origin:beta1 "/usr/bin/openshift 3 hours ago Up 3 hours openshift-origin

And then login to the container associated with frontend as:

docker exec -it `docker ps | grep origin-jee-sample | awk '{ print $1 }'` bash

docker exec -it `docker ps | grep origin-jee-sample | awk '{ print $1 }'` bash

This will log in to the Docker container where you can check that the application is deployed successfully by giving the following command:

bash-4.2$ curl http://localhost:8080/movieplex7-1.0-SNAPSHOT/

bash-4.2$ curl http://localhost:8080/movieplex7-1.0-SNAPSHOT/

This will print the index.html page from the application which has license at the top and rest of the page after that.

Now once the firewall issue is resolved, this page will then be accessible on host Mac as well.

Lets summarize:

Cloned the OpenShift Origin and Java EE 7 sample repo
Started OpenShift v3 as Docker container
Loaded the OpenShift v3 Web Console
Create an OpenShift v3 project
Loaded Java EE 7 application template
Triggered a build, which deployed the application

Here are some troubleshooting tips if you get stuck.

Enjoy!

MySQL as Kubernetes Service, Access from WildFly Pod (Tech Tip #72)

February 10, 2015containers, javaee, techtipdocker, javaee, kubernetes, mysql, wildflyarungupta

Java EE 7 and WildFly on Kubernetes using Vagrant (Tech Tip #71) explained how to run a trivial Java EE 7 application on WildFly hosted using Kubernetes and Docker. The Java EE 7 application was the hands-on lab that have been delivered around the world. It uses an in-memory database that is bundled with WildFly and allows to understand the key building blocks of Kubernetes. This is good to get you started with initial development efforts but quickly becomes a bottleneck as the database is lost when the application server goes down. This tech tip will show how to run another trivial Java EE 7 application and use MySQL as the database server. It will use Kubernetes Services to explain how MySQL and WildFly can be easily decoupled.

Lets get started!

Make sure to have a working Kubernetes setup as explained in Kubernetes using Vagrant.

The complete source code used in this blog is available at github.com/arun-gupta/kubernetes-java-sample.

Start MySQL Kubernetes pod

First step is to start the MySQL pod. This can be started by using the MySQL Kubernetes configuration file:

kubernetes> ./cluster/kubectl.sh create -f ../kubernetes-java-sample/mysql.json
KUBE_MASTER_IP: 10.245.1.2
Running: ./cluster/../cluster/vagrant/../../_output/dockerized/bin/darwin/amd64/kubectl --auth-path=/Users/arungupta/.kubernetes_vagrant_auth create -f ../kubernetes-java-sample/mysql.json
mysql

kubernetes> ./cluster/kubectl.sh create -f ../kubernetes-java-sample/mysql.json

KUBE_MASTER_IP: 10.245.1.2

Running: ./cluster/../cluster/vagrant/../../_output/dockerized/bin/darwin/amd64/kubectl --auth-path=/Users/arungupta/.kubernetes_vagrant_auth create -f ../kubernetes-java-sample/mysql.json

mysql

The configuration file used is at github.com/arun-gupta/kubernetes-java-sample/blob/master/mysql.json.

Check the status of MySQL pod:

kubernetes> ./cluster/kubectl.sh get pods
KUBE_MASTER_IP: 10.245.1.2
Running: ./cluster/../cluster/vagrant/../../_output/dockerized/bin/darwin/amd64/kubectl --auth-path=/Users/arungupta/.kubernetes_vagrant_auth get pods
POD                 IP                  CONTAINER(S)        IMAGE(S)            HOST                    LABELS              STATUS
mysql               10.246.1.3          mysql               mysql:latest        10.245.1.3/10.245.1.3   name=mysql          Pending

kubernetes> ./cluster/kubectl.sh get pods

KUBE_MASTER_IP: 10.245.1.2

Running: ./cluster/../cluster/vagrant/../../_output/dockerized/bin/darwin/amd64/kubectl --auth-path=/Users/arungupta/.kubernetes_vagrant_auth get pods

POD IP CONTAINER(S) IMAGE(S) HOST LABELS STATUS

mysql 10.246.1.3 mysql mysql:latest 10.245.1.3/10.245.1.3 name=mysql Pending

Wait till the status changes to “Running”. It will look like:

KUBE_MASTER_IP: 10.245.1.2
Running: ./cluster/../cluster/vagrant/../../_output/dockerized/bin/darwin/amd64/kubectl --auth-path=/Users/arungupta/.kubernetes_vagrant_auth get pods
POD                 IP                  CONTAINER(S)        IMAGE(S)            HOST                    LABELS              STATUS
mysql               10.246.1.3          mysql               mysql:latest        10.245.1.3/10.245.1.3   name=mysql          Running

KUBE_MASTER_IP: 10.245.1.2

Running: ./cluster/../cluster/vagrant/../../_output/dockerized/bin/darwin/amd64/kubectl --auth-path=/Users/arungupta/.kubernetes_vagrant_auth get pods

POD IP CONTAINER(S) IMAGE(S) HOST LABELS STATUS

mysql 10.246.1.3 mysql mysql:latest 10.245.1.3/10.245.1.3 name=mysql Running

It takes a few minutes for MySQL server to be in that state, so grab a coffee or a quick fast one miler!

Start MySQL Kubernetes service

Pods, and the IP addresses assigned to them, are ephemeral. If a pod dies then Kubernetes will recreate that pod because of its self-healing features, but it might recreate it on a different host. Even if it is on the same host, a different IP address could be assigned to it. And so any application cannot rely upon the IP address of the pod.

Kubernetes services is an abstraction which defines a logical set of pods. A service is typically back-ended by one or more physical pods (associated using labels), and it has a permanent IP address that can be used by other pods/applications. For example, WildFly pod can not directly connect to a MySQL pod but can connect to MySQL service. In essence, Kubernetes service offers clients an IP and port pair which, when accessed, redirects to the appropriate backends.

Lets start MySQL service.

kubernetes> ./cluster/kubectl.sh create -f ../kubernetes-java-sample/mysql-service.json
KUBE_MASTER_IP: 10.245.1.2
Running: ./cluster/../cluster/vagrant/../../_output/dockerized/bin/darwin/amd64/kubectl --auth-path=/Users/arungupta/.kubernetes_vagrant_auth create -f ../kubernetes-java-sample/mysql-service.json
mysql

kubernetes> ./cluster/kubectl.sh create -f ../kubernetes-java-sample/mysql-service.json

KUBE_MASTER_IP: 10.245.1.2

Running: ./cluster/../cluster/vagrant/../../_output/dockerized/bin/darwin/amd64/kubectl --auth-path=/Users/arungupta/.kubernetes_vagrant_auth create -f ../kubernetes-java-sample/mysql-service.json

mysql

The configuration file used is at github.com/arun-gupta/kubernetes-java-sample/blob/master/mysql-service.json. In this case, only a single MySQL instance is started. But multiple MySQL instances can be easily started and WildFly Pod will continue to refer to all of them using MySQL Service.

Check the status/IP of the MySQL service:

kubernetes> ./cluster/kubectl.sh get services
KUBE_MASTER_IP: 10.245.1.2
Running: ./cluster/../cluster/vagrant/../../_output/dockerized/bin/darwin/amd64/kubectl --auth-path=/Users/arungupta/.kubernetes_vagrant_auth get services
NAME                LABELS                                    SELECTOR            IP                  PORT
kubernetes          component=apiserver,provider=kubernetes   <none>              10.247.0.2          443
kubernetes-ro       component=apiserver,provider=kubernetes   <none>              10.247.0.1          80
mysql               name=mysql                                name=mysql          10.247.202.104      3306
skydns              k8s-app=skydns                            k8s-app=skydns      10.247.0.10         53

kubernetes> ./cluster/kubectl.sh get services

KUBE_MASTER_IP: 10.245.1.2

Running: ./cluster/../cluster/vagrant/../../_output/dockerized/bin/darwin/amd64/kubectl --auth-path=/Users/arungupta/.kubernetes_vagrant_auth get services

NAME LABELS SELECTOR IP PORT

kubernetes component=apiserver,provider=kubernetes <none> 10.247.0.2 443

kubernetes-ro component=apiserver,provider=kubernetes <none> 10.247.0.1 80

mysql name=mysql name=mysql 10.247.202.104 3306

skydns k8s-app=skydns k8s-app=skydns 10.247.0.10 53

Start WildFly Kubernetes Pod

WildFly Pod must be started after MySQL service has started. This is because the environment variables used for creating JDBC resource in WildFly are only available after the service is up and running. Specifically, the JDBC resource is created as:

data-source add --name=mysqlDS --driver-name=mysql --jndi-name=java:jboss/datasources/ExampleMySQLDS --connection-url=jdbc:mysql://$MYSQL_SERVICE_HOST:$MYSQL_SERVICE_PORT/sample?useUnicode=true&amp;characterEncoding=UTF-8 --user-name=mysql --password=mysql --use-ccm=false --max-pool-size=25 --blocking-timeout-wait-millis=5000 --enabled=true

data-source add --name=mysqlDS --driver-name=mysql --jndi-name=java:jboss/datasources/ExampleMySQLDS --connection-url=jdbc:mysql://$MYSQL_SERVICE_HOST:$MYSQL_SERVICE_PORT/sample?useUnicode=true&characterEncoding=UTF-8 --user-name=mysql --password=mysql --use-ccm=false --max-pool-size=25 --blocking-timeout-wait-millis=5000 --enabled=true

$MYSQL_SERVICE_HOST and $MYSQL_SERVICE_PORT environment variables are populated by Kubernetes as explained here.

This is shown at github.com/arun-gupta/docker-images/blob/master/wildfly-mysql-javaee7/customization/execute.sh#L44.

Start WildFly pod:

kubernetes> ./cluster/kubectl.sh create -f ../kubernetes-java-sample/wildfly.json
KUBE_MASTER_IP: 10.245.1.2
Running: ./cluster/../cluster/vagrant/../../_output/dockerized/bin/darwin/amd64/kubectl --auth-path=/Users/arungupta/.kubernetes_vagrant_auth create -f ../kubernetes-java-sample/wildfly.json
wildfly

kubernetes> ./cluster/kubectl.sh create -f ../kubernetes-java-sample/wildfly.json

KUBE_MASTER_IP: 10.245.1.2

Running: ./cluster/../cluster/vagrant/../../_output/dockerized/bin/darwin/amd64/kubectl --auth-path=/Users/arungupta/.kubernetes_vagrant_auth create -f ../kubernetes-java-sample/wildfly.json

wildfly

The configuration file used is at github.com/arun-gupta/kubernetes-java-sample/blob/master/wildfly.json.

Check the status of pods:

KUBE_MASTER_IP: 10.245.1.2
Running: ./cluster/../cluster/vagrant/../../_output/dockerized/bin/darwin/amd64/kubectl --auth-path=/Users/arungupta/.kubernetes_vagrant_auth get pods
POD                 IP                  CONTAINER(S)        IMAGE(S)                                 HOST                    LABELS              STATUS
mysql               10.246.1.3          mysql               mysql:latest                             10.245.1.3/10.245.1.3   name=mysql          Running
wildfly             10.246.1.4          wildfly             arungupta/wildfly-mysql-javaee7:knetes   10.245.1.3/10.245.1.3   name=wildfly        Pending

KUBE_MASTER_IP: 10.245.1.2

Running: ./cluster/../cluster/vagrant/../../_output/dockerized/bin/darwin/amd64/kubectl --auth-path=/Users/arungupta/.kubernetes_vagrant_auth get pods

POD IP CONTAINER(S) IMAGE(S) HOST LABELS STATUS

mysql 10.246.1.3 mysql mysql:latest 10.245.1.3/10.245.1.3 name=mysql Running

wildfly 10.246.1.4 wildfly arungupta/wildfly-mysql-javaee7:knetes 10.245.1.3/10.245.1.3 name=wildfly Pending

Wait until WildFly pod’s status is changed to Running. This could be a few minutes, so may be time to grab another quick miler!

Once the container is up and running, you can check /opt/jboss/wildfly/standalone/configuration/standalone.xml in the WildFly container and verify that the connection URL indeed contains the correct IP address. Here is how it looks on my machine:

[jboss@wildfly ~]$ grep 3306 /opt/jboss/wildfly/standalone/configuration/standalone.xml 
                    <connection-url>jdbc:mysql://10.247.202.104:3306/sample?useUnicode=true&amp;amp;characterEncoding=UTF-8</connection-url>

[jboss@wildfly ~]$ grep 3306 /opt/jboss/wildfly/standalone/configuration/standalone.xml

<connection-url>jdbc:mysql://10.247.202.104:3306/sample?useUnicode=true&amp;characterEncoding=UTF-8</connection-url>

The updated status (after the container is running) would look like as shown:

kubernetes> ./cluster/kubectl.sh get pods
KUBE_MASTER_IP: 10.245.1.2
Running: ./cluster/../cluster/vagrant/../../_output/dockerized/bin/darwin/amd64/kubectl --auth-path=/Users/arungupta/.kubernetes_vagrant_auth get pods
POD                 IP                  CONTAINER(S)        IMAGE(S)                                 HOST                    LABELS              STATUS
mysql               10.246.1.3          mysql               mysql:latest                             10.245.1.3/10.245.1.3   name=mysql          Running
wildfly             10.246.1.4          wildfly             arungupta/wildfly-mysql-javaee7:knetes   10.245.1.3/10.245.1.3   name=wildfly        Running

kubernetes> ./cluster/kubectl.sh get pods

KUBE_MASTER_IP: 10.245.1.2

Running: ./cluster/../cluster/vagrant/../../_output/dockerized/bin/darwin/amd64/kubectl --auth-path=/Users/arungupta/.kubernetes_vagrant_auth get pods

POD IP CONTAINER(S) IMAGE(S) HOST LABELS STATUS

mysql 10.246.1.3 mysql mysql:latest 10.245.1.3/10.245.1.3 name=mysql Running

wildfly 10.246.1.4 wildfly arungupta/wildfly-mysql-javaee7:knetes 10.245.1.3/10.245.1.3 name=wildfly Running

Access the Java EE 7 Application

Note down the HOST IP address of the WildFly container and access the application as:

curl http://10.245.1.3:8080/employees/resources/employees

curl http://10.245.1.3:8080/employees/resources/employees

to see the output as:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><collection><employee><id>1</id><name>Penny</name></employee><employee><id>2</id><name>Sheldon</name></employee><employee><id>3</id><name>Amy</name></employee><employee><id>4</id><name>Leonard</name></employee><employee><id>5</id><name>Bernadette</name></employee><employee><id>6</id><name>Raj</name></employee><employee><id>7</id><name>Howard</name></employee><employee><id>8</id><name>Priya</name></employee></collection>

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><collection><employee><id>1</id><name>Penny</name></employee><employee><id>2</id><name>Sheldon</name></employee><employee><id>3</id><name>Amy</name></employee><employee><id>4</id><name>Leonard</name></employee><employee><id>5</id><name>Bernadette</name></employee><employee><id>6</id><name>Raj</name></employee><employee><id>7</id><name>Howard</name></employee><employee><id>8</id><name>Priya</name></employee></collection>

Or viewed in the browser as:

Debugging Kubernetes and Docker

kubernetes> vagrant ssh minion-1
Last login: Tue Feb 10 23:20:13 2015 from 10.0.2.2

kubernetes> vagrant ssh minion-1

Last login: Tue Feb 10 23:20:13 2015 from 10.0.2.2

[vagrant@kubernetes-minion-1 ~]$ su -
Password: 
[root@kubernetes-minion-1 ~]#

[vagrant@kubernetes-minion-1 ~]$ su -

Password:

[root@kubernetes-minion-1 ~]#

Default root password for VM images created by Vagrant is “vagrant”.

List of Docker containers running on this VM can be seen as:

[root@kubernetes-minion-1 ~]# docker ps
CONTAINER ID        IMAGE                                    COMMAND                CREATED             STATUS              PORTS                                            NAMES
7fc1fca102bf        arungupta/wildfly-mysql-javaee7:knetes   "/opt/jboss/wildfly/   28 minutes ago      Up 28 minutes                                                        k8s_wildfly.6c5f240e_wildfly.default.api_1230e74a-b178-11e4-8464-0800279696e1_509268aa                                  
4aa49c0ebb70        kubernetes/pause:go                      "/pause"               43 minutes ago      Up 43 minutes       0.0.0.0:8080->8080/tcp, 0.0.0.0:9090->9090/tcp   k8s_POD.bca60d1a_wildfly.default.api_1230e74a-b178-11e4-8464-0800279696e1_0bff6efa                                      
c36e99cd4557        mysql:latest                             "/entrypoint.sh mysq   47 minutes ago      Up 47 minutes                                                        k8s_mysql.278e3c40_mysql.default.api_f3d07101-b175-11e4-8464-0800279696e1_ddbcaf62                                      
ed4611b5c276        google/cadvisor:0.8.0                    "/usr/bin/cadvisor"    56 minutes ago      Up 56 minutes                                                        k8s_cadvisor.8d424740_cadvisor-agent.file-6bb810db-kubernetes-minion-1.file_80331227d28e618b4cef459507a31796_36d83f7d   
50a3428612f0        kubernetes/pause:go                      "/pause"               58 minutes ago      Up 58 minutes       0.0.0.0:3306->3306/tcp                           k8s_POD.c783ea16_mysql.default.api_f3d07101-b175-11e4-8464-0800279696e1_e46a8424                                        
11a95eeda794        kubernetes/pause:go                      "/pause"               59 minutes ago      Up 59 minutes       0.0.0.0:4194->8080/tcp                           k8s_POD.252debe0_cadvisor-agent.file-6bb810db-kubernetes-minion-1.file_80331227d28e618b4cef459507a31796_734d54eb

[root@kubernetes-minion-1 ~]# docker ps

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

7fc1fca102bf arungupta/wildfly-mysql-javaee7:knetes "/opt/jboss/wildfly/ 28 minutes ago Up 28 minutes k8s_wildfly.6c5f240e_wildfly.default.api_1230e74a-b178-11e4-8464-0800279696e1_509268aa

4aa49c0ebb70 kubernetes/pause:go "/pause" 43 minutes ago Up 43 minutes 0.0.0.0:8080->8080/tcp, 0.0.0.0:9090->9090/tcp k8s_POD.bca60d1a_wildfly.default.api_1230e74a-b178-11e4-8464-0800279696e1_0bff6efa

c36e99cd4557 mysql:latest "/entrypoint.sh mysq 47 minutes ago Up 47 minutes k8s_mysql.278e3c40_mysql.default.api_f3d07101-b175-11e4-8464-0800279696e1_ddbcaf62

ed4611b5c276 google/cadvisor:0.8.0 "/usr/bin/cadvisor" 56 minutes ago Up 56 minutes k8s_cadvisor.8d424740_cadvisor-agent.file-6bb810db-kubernetes-minion-1.file_80331227d28e618b4cef459507a31796_36d83f7d

50a3428612f0 kubernetes/pause:go "/pause" 58 minutes ago Up 58 minutes 0.0.0.0:3306->3306/tcp k8s_POD.c783ea16_mysql.default.api_f3d07101-b175-11e4-8464-0800279696e1_e46a8424

11a95eeda794 kubernetes/pause:go "/pause" 59 minutes ago Up 59 minutes 0.0.0.0:4194->8080/tcp k8s_POD.252debe0_cadvisor-agent.file-6bb810db-kubernetes-minion-1.file_80331227d28e618b4cef459507a31796_734d54eb

Last 10 lines of the WildFly log (after application has been accessed a few times) can be seen as:

23:12:25,004 INFO  [stdout] (ServerService Thread Pool -- 50) Hibernate: INSERT INTO EMPLOYEE_SCHEMA(ID, NAME) VALUES (8, 'Priya')
23:12:27,928 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-5) Deploying javax.ws.rs.core.Application: class org.javaee7.samples.employees.MyApplication
23:12:27,987 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-5) JBAS017534: Registered web context: /employees
23:12:28,073 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 28) JBAS018559: Deployed "employees.war" (runtime-name : "employees.war")
23:12:28,203 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
23:12:28,203 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
23:12:28,204 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.2.0.Final "Tweek" started in 26772ms - Started 280 of 334 services (92 services are lazy, passive or on-demand)
23:23:16,091 INFO  [stdout] (default task-16) Hibernate: select employee0_.id as id1_0_, employee0_.name as name2_0_ from EMPLOYEE_SCHEMA employee0_
23:24:07,322 INFO  [stdout] (default task-17) Hibernate: select employee0_.id as id1_0_, employee0_.name as name2_0_ from EMPLOYEE_SCHEMA employee0_
23:35:07,030 INFO  [stdout] (default task-18) Hibernate: select employee0_.id as id1_0_, employee0_.name as name2_0_ from EMPLOYEE_SCHEMA employee0_

23:12:25,004 INFO [stdout] (ServerService Thread Pool -- 50) Hibernate: INSERT INTO EMPLOYEE_SCHEMA(ID, NAME) VALUES (8, 'Priya')

23:12:27,928 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-5) Deploying javax.ws.rs.core.Application: class org.javaee7.samples.employees.MyApplication

23:12:27,987 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) JBAS017534: Registered web context: /employees

23:12:28,073 INFO [org.jboss.as.server] (ServerService Thread Pool -- 28) JBAS018559: Deployed "employees.war" (runtime-name : "employees.war")

23:12:28,203 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management

23:12:28,203 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990

23:12:28,204 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.2.0.Final "Tweek" started in 26772ms - Started 280 of 334 services (92 services are lazy, passive or on-demand)

23:23:16,091 INFO [stdout] (default task-16) Hibernate: select employee0_.id as id1_0_, employee0_.name as name2_0_ from EMPLOYEE_SCHEMA employee0_

23:24:07,322 INFO [stdout] (default task-17) Hibernate: select employee0_.id as id1_0_, employee0_.name as name2_0_ from EMPLOYEE_SCHEMA employee0_

23:35:07,030 INFO [stdout] (default task-18) Hibernate: select employee0_.id as id1_0_, employee0_.name as name2_0_ from EMPLOYEE_SCHEMA employee0_

Similarly, MySQL log is seen as:

2015-02-10 22:52:55 1 [Note] Server hostname (bind-address): '*'; port: 3306
2015-02-10 22:52:55 1 [Note] IPv6 is available.
2015-02-10 22:52:55 1 [Note]   - '::' resolves to '::';
2015-02-10 22:52:55 1 [Note] Server socket created on IP: '::'.
2015-02-10 22:52:56 1 [Note] Event Scheduler: Loaded 0 events
2015-02-10 22:52:56 1 [Note] Execution of init_file '/tmp/mysql-first-time.sql' started.
2015-02-10 22:52:56 1 [Note] Execution of init_file '/tmp/mysql-first-time.sql' ended.
2015-02-10 22:52:56 1 [Note] mysqld: ready for connections.
Version: '5.6.23'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server (GPL)
2015-02-10 23:12:21 1 [Warning] IP address '10.246.1.1' could not be resolved: Name or service not known

2015-02-10 22:52:55 1 [Note] Server hostname (bind-address): '*'; port: 3306

2015-02-10 22:52:55 1 [Note] IPv6 is available.

2015-02-10 22:52:55 1 [Note] - '::' resolves to '::';

2015-02-10 22:52:55 1 [Note] Server socket created on IP: '::'.

2015-02-10 22:52:56 1 [Note] Event Scheduler: Loaded 0 events

2015-02-10 22:52:56 1 [Note] Execution of init_file '/tmp/mysql-first-time.sql' started.

2015-02-10 22:52:56 1 [Note] Execution of init_file '/tmp/mysql-first-time.sql' ended.

2015-02-10 22:52:56 1 [Note] mysqld: ready for connections.

Version: '5.6.23' socket: '/var/run/mysqld/mysqld.sock' port: 3306 MySQL Community Server (GPL)

2015-02-10 23:12:21 1 [Warning] IP address '10.246.1.1' could not be resolved: Name or service not known

Enjoy!