Skip to content

Conversation

@alicefr
Copy link
Contributor

@alicefr alicefr commented Jan 5, 2026

The new service allows to add attestation key as trusted keys in trustee

@alicefr alicefr marked this pull request as draft January 5, 2026 15:24
@alicefr
Copy link
Contributor Author

alicefr commented Jan 5, 2026

@Jakob-Naucke I still need to add unit tests and run the test suite, but running the VM from the example, it works. If you have time and what to start to have a look at the code

Copy link
Contributor

@Jakob-Naucke Jakob-Naucke left a comment

Choose a reason for hiding this comment

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

first set of random comments

@openshift-ci
Copy link

openshift-ci bot commented Jan 7, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: alicefr

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

The attestationkey represents a request for a registration of a trusted
attestation key. The key is added to the trusted key, only if there is a
machine which corresponds to the IP declared in the AK.

Signed-off-by: Alice Frosi <afrosi@redhat.com>
The attestation key registration offers an API to register an
attestation key. It creates a corresponding CR and the AttestationKey
will be approved and added to the trusted key, if there is a matching
machine.

Once an attestation key is approved, the corresponding secret is created
and added to trustee deployment. In the same way, if a machine owning an
attestation key is removed, also the AK and its secrets are removed from
the trustee deployment.

Signed-off-by: Alice Frosi <afrosi@redhat.com>
Signed-off-by: Alice Frosi <afrosi@redhat.com>
Signed-off-by: Alice Frosi <afrosi@redhat.com>
Signed-off-by: Alice Frosi <afrosi@redhat.com>
If you already have the image cached locally, you can simply load them
in the kind cluster, which is much faster then downloaded each cluster
creation.

Signed-off-by: Alice Frosi <afrosi@redhat.com>
It requires a kubevirt container disk with the latest changes, the
igniiton version needs to be set to the 3.0.0-experimental and include
the attestation key registration endpoint.

Signed-off-by: Alice Frosi <afrosi@redhat.com>
The latest configuration mandate to have the admin.type set.

Signed-off-by: Alice Frosi <afrosi@redhat.com>
They contains the latest trustee and attester which are compatible.

Signed-off-by: Alice Frosi <afrosi@redhat.com>
We have update the approved image and the reference values have changed.

Signed-off-by: Alice Frosi <afrosi@redhat.com>
@alicefr alicefr marked this pull request as ready for review January 9, 2026 13:16
@openshift-ci
Copy link

openshift-ci bot commented Jan 9, 2026

@alicefr: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/infra-provision-verify 158de0c link true /test infra-provision-verify
ci/prow/operator-lifecycle-verify 158de0c link true /test operator-lifecycle-verify

Full PR test history. Your PR dashboard.

Details

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-sigs/prow repository. I understand the commands that are listed here.

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.

3 participants