kube-aws | line tool to declaratively manage Kubernetes clusters | AWS library

I'm currently running on AWS and use kube-aws/kube-spot-termination-notice-handler to intercept an AWS spot termination notice and gracefully evict the pods.

I'm reading this GKE documentation page and I see:

Preemptible instances terminate after 30 seconds upon receiving a preemption notice.

Going into the Compute Engine documentation, I see that a ACPI G2 Soft Off is sent 30 seconds before the termination happens but this issue suggests that the kubelet itself doesn't handle it.

So, how does GKE handle preemption? Will the node do a drain/cordon operation or does it just do a hard shutdown?

Is it possible to install ansible galaxy using brew on mac os? I tried:

I followed this guide https://coreos.com/kubernetes/docs/latest/kubernetes-on-aws-launch.html to create a kubernetes cluster on AWS with kube-aws.

I am using kube-aws to v0.9.4-rc2

After successfully do kube-aws up --s3-uri s3://.., I tried to get the nodes with kubectl get nodes, and that's when I get this error:

I'm using kube-aws to run a Kubernetes cluster on AWS, and everything works as expected.

Now, I realize that cron jobs aren't turned on in the version I'm using (v1.7.10_coreos.0), while the documentation for Kubernetes only states the following:

For previous versions of cluster (< 1.8) you need to explicitly enable batch/v2alpha1 API by passing --runtime-config=batch/v2alpha1=true to the API server (see Turn on or off an API version for your cluster for more).

And the documentation directed to in that text only states this (it's the actual, full documentation):

Specific API versions can be turned on or off by passing --runtime-config=api/ flag while bringing up the API server. For example: to turn off v1 API, pass --runtime-config=api/v1=false. runtime-config also supports 2 special keys: api/all and api/legacy to control all and legacy APIs respectively. For example, for turning off all API versions except v1, pass --runtime-config=api/all=false,api/v1=true. For the purposes of these flags, legacy APIs are those APIs which have been explicitly deprecated (e.g. v1beta3).

I have been unsuccessful in finding information about how to change the configuration of a running cluster, and I, of course, don't want to try to re-run the command on api-server.

Note that kube-aws still use hyperkube, and not kubeadm. Also, the /etc/kubernetes/manifests-directory only contains the ssl-directory.

The setting I want to apply is this: --runtime-config=batch/v2alpha1=true

What is the proper way, preferably using kubectl, to apply this setting and have the apiservers restarted?

Thanks.

I'm going to create Kubernetes cluster on AWS infrastructure. I have two options in kops or kube-aws. which is the best one to use for creating and managing k8s cluster in AWS? What are the pros and cons of those tools?

I have one master and two worker nodes in different AZ.

Thank you

I'm wondering how people are deploying a production-caliber Kubernetes cluster in AWS and, more importantly, how they chose their approach.

The k8s documentation points towards kops for Debian, Ubuntu, CentOS, and RHEL or kube-aws for CoreOS/Container Linux. Among these choices it's not clear how to pick one over the others. CoreOS seems like the most compelling option since it's designed for container workloads.

But wait, there's more.

bootkube seems to be next iteration of the CoreOS deployment technology and is on the roadmap for inclusion within kube-aws. Should I wait until kube-aws uses bootkube?

Heptio recently announced a Quickstart architecture for deploying k8s in AWS. This is the newest approach and so probably the least mature approach but it does seem to have gained traction from within AWS.

Lastly kubeadm is a thing and I'm not really sure where it fits into all of this.

There are probably more approaches that I'm missing too.

Given the number of options with overlapping intent it's very difficult to choose a path forward. I'm not interested in a proof-of-concept. I want to be able to deploy a secure, highly-available cluster for production use and be able to upgrade the cluster (host OS, etcd, and k8s system components) over time.

What did you choose and how did you decide?

I have a k8 cluster deployed in AWS using kube-aws. When I deploy a service, a new ELB is added for exposing the service to internet. Can I use ingress-controller to replace ELB or is there any other way to expose services other than ELB?