Thanks for your feedback and interest. 1. We'll improve the help text to be more specific about what we'd expect for that field. 2. The reason we didn't imple

Thanks for your feedback and interest. 1. We'll improve the help text to be more specific about what we'd expect for that field. 2. The reason we didn't implement OAuth is that we want user to be able to use the same email address in multiple accounts, so the account + email identifies the user not just the email address. 3. We are planning to use cross account IAM role instead of asking access key/ secret key. Will this address your concerns? 4. We are not just provision k8s cluster in your AWS account, k8s nodes will be running in your AWS account and we'll host the master components like etcd, api servers, controller managers and schedulers for you. Those components will be running in our AWS account, the more node you connect to the master, the more resource we need. So we charge based on the number of nodes in the cluster. This is similar to the GKE (not GCE) offering where you only run k8s nodes in your account not the masters.