cluster/test-deploy/aws/openshift: Move sshKey to the admin block

[wking]

Catching up with openshift/installer@37f623c5 (openshift/installer#127).

[smarterclayton]

/lgtm

[openshift-ci-robot]

@wking: Updated the prow-job-cluster-launch-installer-e2e configmap using the following files:

• key cluster-launch-installer-e2e.yaml using file ci-operator/templates/cluster-launch-installer-e2e.yaml

Details

In response to this:

Catching up with openshift/installer@37f623c5 (openshift/installer#127).

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.

[wking]

Maybe this broke the YAML format? From here:

Invoking installer ...
time="2018-08-17T17:45:47Z" level=fatal msg="failed to get configuration from file \"inputs.yaml\": inputs.yaml is not a valid config file: yaml: line 75: found unexpected ':'" 

but there is no uploaded inputs.yaml to look at.

[wking]

The template around that line looks fine:

$ grep -n ^ cluster/test-deploy/aws/openshift.yaml | grep -4 '^75:'
71:    # Example: `["subnet-111111", "subnet-222222", "subnet-333333"]`
72:    # workerSubnetIDs:
73:
74:  # (optional) Extra AWS tags to be applied to created resources.
75:  #
76:  # Example: `{ "key" = "value", "foo" = "bar" }`
77:  extraTags: {"expirationDate" = "${EXPIRATION_DATE}"}
78:
79:  # (optional) Name of IAM role to use to access AWS in order to deploy the Tectonic Cluster.

[wking]

Ah, maybe this is an issue with #1103, but we're only seeing it now because we only just pushed the recent template into production? I'd uncommented extraTags there.

[wking]

Ah, maybe this is an issue with #1103...

Yup. I've filed #1209 with a fix.