Do not require an SSH key to be set

[elliot]

It would be great to have a flag to disable setting an SSH key when creating AWS Launch Configurations.

Our use case is for a PCI-DSS environment. We are using pre-hardened AMI's that disabled creating default admin user accounts, but having a common SSH key associated with each instance raises questions for auditors as to who has access.

[jwickens]

this caught me out for a while while following the getting started guide for launching the basic cluster in aws.

[pieterlange]

I believe its an AWS (API) requirement to assign a private key to each instance.

/edit: false. nevermind :)

[chrislovecnm]

We allow re-using a key now. Please let me know if that helps

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[chrislovecnm]

/lifecycle frozen
/remove-lifecycle rotten

[rickardrosen]

I've been working on a PR for this as we want to able to output TF code without an SSH key.

[elliot]

Possible fix in #7096

[rifelpet]

This has been implemented in Kops 1.18.0
/close

[k8s-ci-robot]

@rifelpet: Closing this issue.

In response to this:

This has been implemented in Kops 1.18.0
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.