Skip to content

Conversation

@alicefr
Copy link
Contributor

@alicefr alicefr commented Oct 28, 2025

No description provided.

@alicefr
Copy link
Contributor Author

alicefr commented Oct 28, 2025

/cc @Jakob-Naucke @travier

Copy link
Contributor

@Jakob-Naucke Jakob-Naucke Oct 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the passing of the Ignition config ("Configuration Schema" in the doc) is missing here. Unless it isn't passed, in which case I find the wording in the doc a little misleading. Maybe also an illustration of subsequent boots (below a separator)?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need to complicate the picture with that? I mean, ignition and the AK registration run only on first boot


## Ignition Configuration

The AK registration is configured through Ignition's attestation section. This configuration is provided during the firstboot merge process from the registration service.
Copy link
Contributor

@Jakob-Naucke Jakob-Naucke Oct 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The registration service provides a config in which it states its location and certificate, both of which Ignition would already have needed to know to (securely) connect to it in the first place? e: offline, we concluded that the registration service does not provide this configuration

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure I get the comment, ignition needs to have an endpoint where to put the AK. This endpoint will be served by the operator and then it will configure trustee with the AK

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This configuration is provided during the firstboot merge process from the registration service.

reads as if the registration service provides the configuration schema (the JSON that is listed below), which it won't afaict

Signed-off-by: Alice Frosi <afrosi@redhat.com>
@alicefr alicefr force-pushed the design-ak-registration branch from 9466fcb to 34fb1e1 Compare October 30, 2025 10:10
- AK is created with TPM-resident private key
- Public key is extracted and saved to `/var/tpm/ak.pub`
3. **Network Requirement**: If registration URL is configured, Ignition ensures network connectivity
4. **Registration Request**: Ignition POSTs the public AK to the registration URL
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the implementation you made that a PUT which might make more sense anyhow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants