You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of each platform implementing their own mechanism for supplying
SSH keys, use the same method everywhere. Now, instead of using AWS's
metadata service, we inject the keys directly via Ignition.
Note: The stub Ignition configs contain the SSH keys. Eventually, the
keys will need to be moved into MCO, so that they can be rotated.
Copy file name to clipboardExpand all lines: examples/tectonic.aws.yaml
+1-3Lines changed: 1 addition & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,7 @@
1
1
admin:
2
2
email: "a@b.c"
3
3
password: "verysecure"
4
+
sshKey: "ssh-ed25519 AAAA..."
4
5
aws:
5
6
# (optional) Unique name under which the Amazon S3 bucket will be created. Bucket name must start with a lower case name and is limited to 63 characters.
6
7
# The Tectonic Installer uses the bucket to store tectonic assets and kubeconfig.
@@ -130,9 +131,6 @@ aws:
130
131
# The target AWS region for the cluster.
131
132
region: eu-west-1
132
133
133
-
# Name of an SSH key located within the AWS region. Example: coreos-user.
134
-
sshKey:
135
-
136
134
# Block of IP addresses used by the VPC.
137
135
# This should not overlap with any other networks, such as a private datacenter connected via Direct Connect.
0 commit comments