1.4

SSH keys are now stored as secrets. will be created when you do kops create cluster. You no longer need to specify a --ssh-public-key when you do an update, but if you do it will be imported.
For AWS, only a single SSH key can be used; you can delete extra keys with kops delete secret

kops create cluster now creates the spec, but will not normally create the actual cloud resources. You can specify --yes to force immediate creation if you want to. create will now fail on an existing cluster.
kops update cluster will now apply changes from the spec to the cloud - it will create or update your cluster. It also defaults to dryrun mode, so you should pass (normally after checking the preview).
Most commands accept positional arguments for the cluster name (you can specify kops update cluster <name>, instead of kops update cluster --name <name>)