Afterburn SSH public keys fetching is failing on Akamai

[tormath1]

Bug

⚠️ This is not an Afterburn bug it's more a design choice that impacts Afterburn assumption.

If you start an instance using Afterburn on Akamai with --authorized_users foo the SSH keys associated to the foo user profile won't be available on the /v1/ssh-keys metadata endpoint so Afterburn will fail to inject the keys.

Which means, if you want to get your SSH keys on the deployed instance, it's mandatory to pass them through Ignition.

/v1/ssh-keys metadata endpoint actually returns the key available in the user-data (Ignition or cloud-init), so if you deploy your instance with SSH keys in Ignition, Afterburn won't fail but it's pointless regarding the purpose of Ignition / Afterburn.

This issue is more here for reference purposes and help users facing the same issue and we can also discuss about removing SSH keys support from Afterburn implementation.

Operating System Version

Flatcar beta-4054.1.0

Afterburn Version

Afterburn v5.6.0

Environment

What hardware/cloud provider/hypervisor is being used to run Afterburn? Akamai

Expected Behavior

Get the metadata service to return the ssh public keys associated to the foo user

Actual Behavior

The metadata service returns keys only available in user-data

Reproduction Steps

1. Start an instance with SSH keys in user-data (cloud-init or Ignition) -> Afterburn will be able to fetch SSH keys
2. Start an instance without SSH keys in user-data -> Afterburn won't be able to fetch SSH keys

Other Information

• This does not impact the Afterburn metadata fetching, this is working perfectly.
• https://www.linode.com/community/questions/24938/v1ssh-keys-is-empty-when-deploying-a-private-image initial ticket