Kubernetes 1.5.0 was released just about a month ago! Key theme for the release are:
- StatefulSets (ex-PetSets)
- StatefulSets are beta now (fixes and stabilization)
- Improved Federation Support
- New command:
kubefed - DaemonSets
- Deployments
- ConfigMaps
- New command:
- Simplified Cluster Deployment
- Improvements to
kubeadm - HA Setup for Master
- Improvements to
- Node Robustness and Extensibility
- Windows Server Container support
- CRI for pluggable container runtimes
kubeletAPI supports authentication and authorization
Read CHANGELOG for complete details. Up until 1.5.0, starting up a Kubernetes cluster on Amazon Web Services was pretty straight forward.
|
1 |
NUM_NODES=2 NODE_SIZE=m3.medium KUBERNETES_PROVIDER=aws ./clúster/kube–up.sh |
But with 1.5.0 and 1.5.1, the command fails with the error:
|
1 2 3 4 5 |
... Starting clúster en nosotros–west–2a usando proveedor aws ... calling verify–prereqs ... calling kube–up Starting clúster usando os distro: jessie !!! Cannot find Kubernetes–server–linux–amd64.tar.gz |
What happened? Basically, Kubernetes binaries was getting bigger than 1GB. The binary was broken into a basic install bundle and client and server binaries. The updated installation process requires to download the basic install bundle of of 4.57 MB (yes, MB instead of GB). It includes cluster scripts like kubectl, kube-up.sh y kube-down.sh, examples, docs and other scripts. This then downloads client and server binaries. Server binary is the base image that is used to start EC2 instances. But instead of automating the download of binaries, somebody decided to add a README in the server directory.
This was a big user experience change, and no links in the README bundled with the release or the release blog. Ouch!
Anyway, this was filed as #38728 and fixed promptly. But it missed the 1.5.1 release and now finally showed up in the 1.5.2 release today.
So, how do you run a Kubernetes 1.5.2 cluster on AWS? It is more seamlessly integrated now but you need to hit Enter key a couple of times to accept the default value:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 |
NUM_NODES=2 NODE_SIZE=m3.medium KUBERNETES_PROVIDER=aws ./clúster/kube–up.sh ... Starting clúster en nosotros–west–2a usando proveedor aws ... calling verify–prereqs ... calling verify–kube–binaries !!! kubectl appears a be broken o missing !!! Cannot find Kubernetes–server–linux–amd64.tar.gz Required binaries appear a be missing. Do you wish a download them? [Y/n] Kubernetes release: v1.5.2 Servidor: linux/amd64 (a anular, establecer KUBERNETES_SERVER_ARCH) Client: darwin/amd64 (autodetected) Will download Kubernetes–server–linux–amd64.tar.gz desde https://storage.googleapis.com/kubernetes-release/release/v1.5.2 Will download y extract Kubernetes–client–darwin–amd64.tar.gz desde https://storage.googleapis.com/kubernetes-release/release/v1.5.2 Is este ok? [Y]/n Warning: Keep–alive functionality somewhat crippled due a missing support en Warning: your operating system! % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 299M 100 299M 0 0 2132k 0 0:02:23 0:02:23 —:—:— 2439k md5sum(Kubernetes–server–linux–amd64.tar.gz)=7947bd430c4ffc358a6784e51c1d2b0f sha1sum(Kubernetes–server–linux–amd64.tar.gz)=4dbdcfa623412dac6be8fd5a4209a1f1423e8d30 Warning: Keep–alive functionality somewhat crippled due a missing support en Warning: your operating system! % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 22.0M 100 22.0M 0 0 1810k 0 0:00:12 0:00:12 —:—:— 2296k md5sum(Kubernetes–client–darwin–amd64.tar.gz)=f55a8f9c300042e9b16e327ad2788521 sha1sum(Kubernetes–client–darwin–amd64.tar.gz)=c29ab99e22146ba0a3da5c25de62ed13108b8ba9 Extracting /Users/arungupta/Herramientas/Kubernetes/Kubernetes–1.5.2/Kubernetes/client/Kubernetes–client–darwin–amd64.tar.gz into /Users/arungupta/Herramientas/Kubernetes/Kubernetes–1.5.2/Kubernetes/platforms/darwin/amd64 Add ‘/Users/arungupta/tools/kubernetes/kubernetes-1.5.2/kubernetes/client/bin’ a your PATH a use newly–installed binaries. ... calling kube–up Starting clúster usando os distro: jessie Uploading a Amazon S3 ... |
After the usual Kubernetes cluster is created, the output is shown as:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 |
0 minions started; waiting 0 minions started; waiting 2 minions started; ready Waiting para clúster initialization. Este will continually check a see si el API para Kubernetes is reachable. Este might loop forever si allí was some uncaught error during start up. .........................................................................................................................................................................Kubernetes clúster created. Sanity checking clúster... Attempt 1 a check Docker en nodo @ 35.166.195.134 ...no working yet Attempt 2 a check Docker en nodo @ 35.166.195.134 ...working Attempt 1 a check Docker en nodo @ 35.166.188.211 ...no working yet Attempt 2 a check Docker en nodo @ 35.166.188.211 ...working Kubernetes clúster is running. El maestro is running at: https://35.165.234.219 El usuario nombre y contraseña a use is located en /Users/arungupta/.kube/configuración. ... calling validate–clúster No resources found. Waiting para 2 ready nodos. 0 ready nodos, 0 registered. Retrying. Waiting para 2 ready nodos. 0 ready nodos, 2 registered. Retrying. Waiting para 2 ready nodos. 0 ready nodos, 2 registered. Retrying. Found 2 nodo(s). NAME ESTADO AGE ip–172–20–0–206.us–west–2.compute.internal Ready 45s ip–172–20–0–246.us–west–2.compute.internal Ready 42s Validate output: NAME ESTADO MESSAGE ERROR controller–gerente Healthy ok scheduler Healthy ok etcd–0 Healthy {“health”: “true”} etcd–1 Healthy {“health”: “true”} Clúster validation succeeded Done, listing clúster services: Kubernetes maestro is running at https://35.165.234.219 Elasticsearch is running at https://35.165.234.219/api/v1/proxy/namespaces/kube-system/services/elasticsearch-logging Heapster is running at https://35.165.234.219/api/v1/proxy/namespaces/kube-system/services/heapster Kibana is running at https://35.165.234.219/api/v1/proxy/namespaces/kube-system/services/kibana-logging KubeDNS is running at https://35.165.234.219/api/v1/proxy/namespaces/kube-system/services/kube-dns Kubernetes–dashboard is running at https://35.165.234.219/api/v1/proxy/namespaces/kube-system/services/kubernetes-dashboard Grafana is running at https://35.165.234.219/api/v1/proxy/namespaces/kube-system/services/monitoring-grafana InfluxDB is running at https://35.165.234.219/api/v1/proxy/namespaces/kube-system/services/monitoring-influxdb A further depurar y diagnose clúster problems, use ‘kubectl cluster-info dump’. |
Even though your Kubernetes cluster on AWS starts up fine, but kube-up.sh script is going to be deprecated soon. The recommended way is to use Kubernetes Cluster on Amazon using Kops. Now that your Kubernetes cluster is up, what do you do next?
- Follow the detailed steps for Kubernetes for Java Developers workshop.
- Run a Couchbase cluster in Kubernetes
- Aprende más sobre Couchbase cluster in Containers
Deja un comentario
Lo siento, debes estar conectado para publicar un comentario.